Skip to content
Squatch MCP

AgentBridge — Discover A2A Services from MCP

dev.ngrok-free.sympathy-myself-jogger/agentbridge

by dev.ngrok-free.sympathy-myself-jogger· v0.9.1-rc.29Source: Official MCP Registry

Findings

Detected by Squatch rules from the server's metadata and protocol behavior. Latest completed scan: .

Severity: High2 findings

Severity: HighStatus: OpenSQ-ENDPOINT-EPHEMERAL-TUNNEL

Endpoint on an ephemeral tunnel domain

The endpoint is hosted on an ephemeral tunnel domain.

First seen · Last seen

Suggested fix: Host the endpoint on a stable domain the publisher controls.

Severity: HighStatus: OpenSQ-TOOL-EXFIL-DIRECTIVE

Asks the AI model to pass conversation data or secrets

Model-facing text instructs the AI model to place conversation content, prompts, tool history or secrets into tool arguments or external destinations.

First seen · Last seen

Suggested fix: Do not ask the model to include conversation, prompt or credential content in arguments.

Severity: Medium1 finding

Severity: MediumStatus: OpenSQ-SERVER-AUTH-NONE-WRITE

State-changing tools available without authentication

The remote server lists state-changing tools without requiring authentication.

First seen · Last seen

Suggested fix: Require MCP authorization for servers that expose state-changing tools.

Severity: Low3 findings

Severity: LowStatus: OpenSQ-REPO-MISSING

No source repository linked

No source repository is linked in the registry entry.

First seen · Last seen

Suggested fix: Add a repository to server.json.

Severity: LowStatus: OpenSQ-TOOL-DESTRUCTIVE-NO-ANNOTATION

Destructive tool without annotations

A tool that appears to delete data, change permissions or run code declares no tool annotations.

First seen · Last seen

Suggested fix: Declare readOnlyHint, destructiveHint, idempotentHint and openWorldHint so clients can request confirmation.

Severity: LowStatus: OpenSQ-CONFORMANCE-MODERN-FAILURE

Protocol conformance checks failed

The server failed one or more MCP protocol conformance checks.

First seen · Last seen

Suggested fix: Review the failed checks against the MCP specification.

What this scan does not cover

  • Squatch never calls a server's tools, so it cannot see what they actually do at run time.
  • It scans without credentials: tools behind authentication may not be visible.
  • It does not review source code, dependencies or the publisher's infrastructure.
  • A server can change behavior between scans; monitoring compares each scan with the last.
  • Classifications come from tool names, descriptions and schemas, which the publisher controls.

How Squatch scans servers