Automaton Token Safety
REMOTE · API.AUTOMATON-SOVEREIGN.WORKERS.DEV · 2 COMPONENTS
Base L2 token safety for AI agents: honeypot scans, swap simulation, approval and liquidity risk.
Available components
Last scanned (3 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1733 tokens (~86/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +53
- HTTPS: unverified → fail ▼ security
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 2 Nov 26 −53
- Endpoint reachability: reachable → behind authorisation ▼ security
- HTTPS: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.automaton-sovereign.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=automaton-sovereign.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6ad2ead95d3780b46a70337cf4852943ea2 |
| SANs: *.automaton-sovereign.workers.dev, automaton-sovereign.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.automaton-sovereign.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.automaton-sovereign.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.automaton-sovereign.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
approval_risk ~136
PAID 0.01 USDC/call, or free trial (3/day/IP). Read-only audit of the ERC-20 approvals an owner granted for a token: spender, allowance, contract vs EOA, verified flag, drainable amount and a drain-risk verdict. On 402, pay the accepts[] terms then retry with the payment tx hash.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Address whose approvals are audited (0x...) |
| payment | string | – | – |
| spenders | array | – | Extra spenders to check beyond the log window |
| token | string | yes | ERC-20 token contract (0x...) |
No output schema declared.
No examples provided.
attest ~102
Create a SIGNED, hash-chained, append-only attestation (verifiable proof-of-existence) for a payload. PAID: 0.05 USDC/call, or free trial (3/day/IP). On 402, pay the accepts[] terms then retry with the payment tx hash.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Payload to attest (any string). |
| payment | string | – | Optional X-PAYMENT base tx hash of the USDC payment. |
No output schema declared.
No examples provided.
attestation_pubkey ~35
FREE. Get the ECDSA P-256 public key (PEM) and keyId used to sign ledger entries.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hash_sha256 ~42
PAID 0.001 USDC/call. SHA-256 hex of a string.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | – |
| payment | string | – | – |
No output schema declared.
No examples provided.
health ~15
FREE. Service liveness and version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
liquidity_risk ~130
PAID 0.01 USDC/call, or free trial (3/day/IP). One-block liquidity audit of a Base token: Uniswap V3 / Aerodrome pools, the USD needed to move the price 1/2/5/10%, holder concentration, LP burn evidence and explicit coverage gaps. On 402, pay the accepts[] terms then retry with the payment tx hash.
| Name | Type | Req | Description |
|---|---|---|---|
| pair | string | – | Analyze only this pool instead of all pools (0x...) |
| payment | string | – | – |
| token | string | yes | Token contract to audit (0x...) |
No output schema declared.
No examples provided.
merkle_prove ~66
PAID 0.001 USDC/call. Generate a cryptographic Merkle inclusion proof for a list of items and target element.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Array of items |
| payment | string | – | – |
| target | string | – | Target item or index |
No output schema declared.
No examples provided.
merkle_verify ~44
FREE. Verify a cryptographic Merkle inclusion proof against a root.
| Name | Type | Req | Description |
|---|---|---|---|
| item | string | yes | – |
| proof | array | yes | – |
| root | string | yes | – |
No output schema declared.
No examples provided.
oracle_base ~80
PAID 0.001 USDC/call. Get real-time Base L2 gas estimates and asset prices (ETH, USDC, cbBTC, AERO, VIRTUAL) with an ECDSA P-256 digital signature from the sovereign agent.
| Name | Type | Req | Description |
|---|---|---|---|
| payment | string | – | Optional X-PAYMENT base tx hash of the USDC payment. |
No output schema declared.
No examples provided.
pricing ~19
FREE. Full pricing terms, endpoints, and payment mechanics.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_ledger ~34
FREE. Read the attestation ledger (paginated).
| Name | Type | Req | Description |
|---|---|---|---|
| from | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
security_scan ~141
LEGACY NAME of token_scan — same route, same arguments, kept so clients written against this server keep working. PAID 0.001 USDC/call, or free trial (3/day/IP). Base token safety analysis: honeypot detection, mint traps, selfdestruct/delegatecall, proxy and tax risks from contract bytecode, with a risk score and signed verdict. On 402, pay the accepts[] terms then retry with the payment tx hash.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token or contract address on Base (0x...). |
| payment | string | – | Optional X-PAYMENT base tx hash of the USDC payment. |
No output schema declared.
No examples provided.
sentiment_analysis ~61
PAID 0.001 USDC/call. Web3 token risk, security checks, and sentiment scoring with signed verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol (e.g. ETH, AERO, VIRTUAL) |
| payment | string | – | – |
No output schema declared.
No examples provided.
sentinel_latest ~163
PAID 0.001 USDC/call, or free trial (3/day/IP). Newest liquidity pools created on Base (Uniswap v3/v4, Aerodrome) with a bytecode risk score per new token. Filters are optional. On 402, pay the accepts[] terms then retry with the payment tx hash.
| Name | Type | Req | Description |
|---|---|---|---|
| dex | string | – | Restrict to one venue |
| limit | integer | – | Max pools to return (default 50) |
| maxRisk | number | – | Only pools whose risk score is at most this |
| minRisk | number | – | Only pools whose risk score is at least this |
| payment | string | – | – |
| since | string | – | ISO-8601 timestamp; only pools detected after it |
No output schema declared.
No examples provided.
simulate_base_transaction ~175
FREE, runs locally against Base Mainnet RPC. Dry-run a transaction before sending it: eth_call + eth_estimateGas at the latest block. Predicts whether it will revert and decodes the reason (Error(string), Panic(uint256) codes, custom-error selector, or node rejection such as insufficient funds). Returns { ok, willRevert, revertReason, estimatedGas, returnData }.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | – | Calldata as 0x-hex (default 0x for a plain ETH transfer). |
| from | string | – | Optional sender address; needed for balance/allowance-dependent calls. |
| to | string | yes | Target contract or recipient address on Base (0x...). |
| value | string | – | ETH value in wei, decimal or 0x-hex (default 0). |
No output schema declared.
No examples provided.
token_scan ~131
PAID 0.001 USDC/call, or free trial (3/day/IP). Bytecode security scan of a Base token contract: honeypot opcodes, mint/blacklist/pause/tax capabilities, a risk score and a verdict. Read-only — no transaction is sent. On 402, pay the accepts[] terms then retry with the payment tx hash. (Exposed as `security_scan` on older clients.)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract on Base (0x...) |
| payment | string | – | Optional X-PAYMENT base tx hash of the USDC payment. |
No output schema declared.
No examples provided.
tx_simulate ~174
PAID 0.01 USDC/call, or free trial (3/day/IP). Read-only buy/sell simulation of a Base token through the Uniswap V2 WETH pool: returns reverts, the MEASURED transfer tax and a honeypot verdict. No transaction is sent. On 402, pay the accepts[] terms then retry with the payment tx hash. (Not the same tool as simulate_base_transaction, which dry-runs arbitrary calldata for free.)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | ETH for a buy, token units for a sell (positive decimal string) |
| payment | string | – | – |
| side | string | yes | Trade direction being simulated |
| token | string | yes | Token contract to trade (0x...) |
| wallet | string | yes | Address simulated as the trader (0x...) |
No output schema declared.
No examples provided.
uuid ~31
PAID 0.001 USDC/call. Generate a UUIDv4.
| Name | Type | Req | Description |
|---|---|---|---|
| payment | string | – | – |
No output schema declared.
No examples provided.
verify_attestation ~51
FREE. Verify a ledger entry by index or by data hash: recomputes hash, checks ECDSA signature and chain link.
| Name | Type | Req | Description |
|---|---|---|---|
| dataHash | string | – | – |
| index | integer | – | – |
No output schema declared.
No examples provided.
x402_conformance_check ~103
FREE, runs locally. Lint any x402 paid endpoint for protocol conformance: HTTP 402 challenge, x402Version, accepts[] (exact scheme), Base network and addresses, EIP-712 domain, and rejection of malformed, forged, expired, underpaid and wrong-recipient EIP-3009 payments. Returns verdict, grade and per-check results.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the x402-protected endpoint to check. |
No output schema declared.
No examples provided.
How do I install the Automaton Token Safety MCP server?
Automaton Token Safety is a hosted endpoint at https://api.automaton-sovereign.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.automaton-sovereign.workers.dev
claude mcp add --transport http baianomarceloeduardo-jpg-automaton-token-safety- 'https://api.automaton-sovereign.workers.dev/mcp'
What is the Automaton Token Safety MCP server?
Automaton Token Safety is an MCP server listed in the public MCP registry as io.github.baianomarceloeduardo-jpg/automaton-token-safety-m…. Base L2 token safety for AI agents: honeypot scans, swap simulation, approval and liquidity risk. This page covers its hosted endpoint (https://api.automaton-sovereign.workers.dev/mcp).
Is the Automaton Token Safety MCP server safe to use?
Automaton Token Safety scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Automaton Token Safety MCP server expose?
Automaton Token Safety exposes 20 tools: x402_conformance_check, simulate_base_transaction, token_scan, tx_simulate, approval_risk, and 15 more. Their descriptions and schemas cost roughly 1,733 tokens of context every time the server is loaded.
Does the Automaton Token Safety MCP server require authentication?
No. We connected to Automaton Token Safety without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Automaton Token Safety MCP server still maintained?
Automaton Token Safety is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.