Skip to content
Squatch MCP
Sign in

io.github.cyanheads/us-lobbying-mcp-server

io.github.cyanheads/us-lobbying-mcp-server

by io.github.cyanheads· v0.1.2Source: Official MCP Registry
Sign in to watchSign in to claim this server

Findings

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

Severity: High1 finding

Severity: HighStatus: OpenSQ-TOOL-TITLE-EFFECT-MISMATCH

Display title describes a lower-impact action than the name

The tool's display title describes a lower-impact action than its name (for example a read title on a delete tool).

First seen · Last seen

Suggested fix: Make the title describe the same action as the tool name.

Severity: Medium2 findings

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: MediumStatus: OpenSQ-TOOL-INJECTION-INSTRUCTIONS

Instructions addressed to the AI model

Model-facing text contains instructions addressed to the AI model rather than a description of the tool (for example to override prior instructions, to act before using tools, or to react to trigger phrases).

First seen · Last seen

Suggested fix: Describe what the tool does and its parameters. Do not include instructions to the model about other tools, the user or the conversation.

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