Skip to content
Squatch MCP
Sign in

X3 Compliance

io.github.x3allamerican/x3-compliance-mcp

by io.github.x3allamerican· v1.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: Medium2 findings

Severity: MediumStatus: OpenSQ-TOOL-CREDENTIAL-ARGUMENT

Asks the AI model to supply credentials as 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.

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: Low4 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-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-EXFIL-SHAPED-PARAM

Free-text parameter commonly used to collect conversation data

A free-text parameter has a name commonly abused to collect conversation, prompt or environment data.

First seen · Last seen

Suggested fix: Constrain the parameter (enum, maxLength) or rename it to reflect its purpose; never ask the model to fill it with conversation content.

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.

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