Protocol conformance checks failed
The server failed one or more MCP protocol conformance checks.
First seen · Last seen
Detected by Squatch rules from the server's metadata and protocol behavior. Latest completed scan: .
The server failed one or more MCP protocol conformance checks.
First seen · Last seen
Suggested fix: Review the failed checks against the MCP specification.
No source repository is linked in the registry entry.
First seen · Last seen
Suggested fix: Add a repository to server.json.
The tool's name and description do not state what it does.
First seen · Last seen
Suggested fix: Describe the action the tool performs, its target and its side effects.
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.
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.
The tool declares itself read-only, but its name or description indicates it changes, deletes or runs something. Clients that auto-approve read-only tools would run it without confirmation.
First seen · Last seen
Suggested fix: Set readOnlyHint to false and destructiveHint to reflect the tool's behavior.