Automaton Token Safety MCP Server

Automaton Token Safety is an MCP integration. Base L2 token safety for AI agents: honeypot scans, swap simulation, approval and liquidity risk.

Hosted connection

The registry lists a streamable-http connection at https://api.automaton-sovereign.workers.dev/mcp.

Packages and local setup

The published npm package is @celorodrigues/token-safety-mcp, version 2.0.2. Its declared MCP transport is stdio.

The package declares VALUE_API_BASE (required): Base URL of the Automaton Token Safety API the tools call.; AUTOMATON_ORIGIN_BASE: Origin URL for routes the edge defers with a use_origin answer (for example the free conformance checker). Optional; without it such a tool reports which variable to set.; AUTOMATON_MCP_PAYER_KEY: Private key of the wallet that pays for calls. The server only SIGNS an EIP-3009 authorisation; it never sends a transaction. Also required: ALLOW_OUTBOUND_SPEND=1, and this key is not loaded into the process without it. Never set this to the payee/treasury wallet: that is rejected.; ALLOW_OUTBOUND_SPEND: Set to 1 to permit this server to sign paid calls. Any other value (including absent) leaves every paid tool answering with the price only.; AUTOMATON_MCP_MAX_AMOUNT_UNITS: Per-call ceiling in USDC base units (6 decimals, so 10000 = 0.01 USDC). A requirement above it is refused before signing.; AUTOMATON_MCP_TOTAL_CAP_UNITS: Ceiling for the whole process lifetime, in USDC base units. Stops a runaway loop, not just a single expensive call.; MCP_HTTP_PORT: When set, serve Streamable HTTP on this port instead of stdio. Binds to 127.0.0.1 by default..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 2.0.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.