Skip to content
Squatch MCP

Findings

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

Severity: Medium2 findings

Severity: MediumStatus: OpenSQ-SCHEMA-NETWORK-REF

Schema references a remote URL

A tool schema contains a $ref that points to a network location. Clients must not fetch it automatically.

First seen · Last seen

Suggested fix: Inline referenced definitions under $defs.

Severity: MediumStatus: OpenSQ-SCHEMA-NETWORK-REF

Schema references a remote URL

A tool schema contains a $ref that points to a network location. Clients must not fetch it automatically.

First seen · Last seen

Suggested fix: Inline referenced definitions under $defs.

Severity: Low2 findings

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.

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.

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