Home / MCP registry index / io.github.baianomarceloeduardo-jpg/automaton-token-safety-mcp
Automaton Token Safety
io.github.baianomarceloeduardo-jpg/automaton-token-safety-mcp in the official MCP registry.
Endpoint https://api.automaton-sovereign.workers.dev/mcp. Source: github.com/baianomarceloeduardo-jpg/automaton-x402.
The registry describes it as: Base L2 token safety for AI agents: honeypot scans, swap simulation, approval and liquidity risk.
We read its 20 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
x402_conformance_check simulate_base_transaction token_scan tx_simulate approval_risk liquidity_risk sentinel_latest security_scan attest verify_attestation attestation_pubkey read_ledger oracle_base merkle_prove merkle_verify sentiment_analysis hash_sha256 uuid pricing health
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-baianomarceloeduardo-jpg-automaton-token-safety-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.