Tools

What tools does

The tools MCP server provides AI agents with access to Doormat Capital’s paid x402 safety tools. Its stated security functions are token scanning and HTTP security-header analysis. These capabilities place the server in the 🔒 Security category and are relevant when an agent needs to perform focused checks on token-related data or web response headers.

The available listing does not provide a README or detailed API reference. As a result, the exact input fields, output format, supported token types, header rules, pricing details, and error behavior cannot be confirmed from the supplied material. Developers should verify those details against the service before building production workflows.

Tools and capabilities

The tools MCP server is described as offering two main safety functions:

• Token scanning for inspecting tokens through Doormat Capital’s service.
• HTTP security-header checks for assessing HTTP response security headers.

These functions are presented as paid x402 tools for AI agents. The listing does not identify additional tools, integrations, programming-language SDKs, data sources, or reporting formats, so those should not be assumed.

A suitable use case is an agent workflow that needs a dedicated security check before processing token data or relying on an HTTP endpoint. The server may also fit an agent that needs to include header analysis as part of a broader request-review process. The available information does not establish whether checks are synchronous, whether results are cached, or whether the service accepts raw values, URLs, or structured requests.

Limitations and notes

The source material identifies the service endpoint and its two safety-tool areas but does not include installation instructions. It does not document the MCP transport, required environment variables, payment flow, credentials, supported clients, rate limits, regional availability, or license. No client-specific compatibility can therefore be confirmed.

The x402 designation indicates that the tools are paid, but the supplied description does not explain how payment is initiated or settled. Confirm the expected x402 configuration and any account requirements before deployment. Also verify what token material may be sent to the service and how responses should be handled, especially in workflows involving sensitive credentials.

Use the tools MCP server only for the checks documented by the provider. Do not infer that token scanning validates every token standard or that HTTP security-header analysis covers the full security posture of an application. The listing supports those two capabilities, but it does not claim to provide a complete application-security assessment.