Severity: HighStatus: OpenSQ-TOOL-SENSITIVE-PATH-REFERENCE
References credential or key locations
Model-facing text references credential, key or configuration file locations unrelated to the tool's stated purpose.
First seen · Last seen
SCRIPTMASTERLABS — PRO-LO
com.scriptmasterlabs/pro-lo
Findings
Detected by Squatch rules from the server's metadata and protocol behavior. Latest completed scan: .
Severity: High2 findings
Suggested fix: Remove references to credential files, key stores and client configuration files.
Severity: HighStatus: OpenSQ-TOOL-ANNOTATION-UNDERCLAIM
Annotations understate what the tool does
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.
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: Low7 findings
Severity: LowStatus: OpenSQ-TOOL-META-INSUFFICIENT
Description too thin to determine behavior
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.
Severity: LowStatus: OpenSQ-ENDPOINT-OUTSIDE-NAMESPACE
Endpoint host outside the namespace domain
The endpoint host is not inside the domain that the registry namespace was verified for.
First seen · Last seen
Suggested fix: Host the endpoint under the namespace domain, or verify the endpoint domain with Squatch.
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-TOOL-META-INSUFFICIENT
Description too thin to determine behavior
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.
Severity: LowStatus: OpenSQ-TOOL-ANNOTATION-UNDERCLAIM
Annotations understate what the tool does
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.
Severity: LowStatus: OpenSQ-TOOL-ANNOTATION-UNDERCLAIM
Annotations understate what the tool does
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.
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.
3 resolved or dismissed findings
Severity: LowStatus: ResolvedSQ-TOOL-META-INSUFFICIENT
Description too thin to determine behavior
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.
Status history
- ResolvedSquatch
Severity: LowStatus: ResolvedSQ-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.
Status history
- ResolvedSquatch
Severity: LowStatus: ResolvedSQ-TOOL-META-INSUFFICIENT
Description too thin to determine behavior
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.
Status history
- ResolvedSquatch
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.