Look-alike characters from mixed scripts
A name or word mixes Latin letters with look-alike letters from other scripts.
First seen · Last seen
dev.tanod/text
Detected by Squatch rules from the server's metadata and protocol behavior. Latest completed scan: .
A name or word mixes Latin letters with look-alike letters from other scripts.
First seen · Last seen
Suggested fix: Use a single script per identifier; tool and parameter names should be ASCII.
Model-facing text references credential, key or configuration file locations unrelated to the tool's stated purpose.
First seen · Last seen
Suggested fix: Remove references to credential files, key stores and client configuration files.
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.
A tool parameter asks the AI model to supply a password, token, key or similar credential, which the model can see and repeat.
First seen · Last seen
Suggested fix: Obtain credentials through server-side configuration or MCP authorization instead of tool arguments.
A tool parameter asks the AI model to supply a password, token, key or similar credential, which the model can see and repeat.
First seen · Last seen
Suggested fix: Obtain credentials through server-side configuration or MCP authorization instead of tool arguments.
Model-facing text gives the AI model instructions about tools that this server does not provide (tool shadowing).
First seen · Last seen
Suggested fix: Describe only this server's own 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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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.
No source repository is linked in the registry entry.
First seen · Last seen
Suggested fix: Add a repository to server.json.
Model-facing text gives the AI model instructions about tools that this server does not provide (tool shadowing).
First seen · Last seen
Suggested fix: Describe only this server's own tools.