# Automaton Token Safety (remote · api.automaton-sovereign.workers.dev)

Base L2 token safety for AI agents: honeypot scans, swap simulation, approval and liquidity risk.

- Trust score: 71/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.automaton-sovereign.workers.dev`: 71/100 (this document), [markdown](https://verifymcp.io/servers/baianomarceloeduardo-jpg-automaton-token-safety-mcp/api.md), [page](https://verifymcp.io/servers/baianomarceloeduardo-jpg-automaton-token-safety-mcp/api)
- npm · `@celorodrigues/token-safety-mcp`: 79/100, [markdown](https://verifymcp.io/servers/baianomarceloeduardo-jpg-automaton-token-safety-mcp/celorodrigues-token-safety-mcp.md), [page](https://verifymcp.io/servers/baianomarceloeduardo-jpg-automaton-token-safety-mcp/celorodrigues-token-safety-mcp)

## Channel facts

- Endpoint: `https://api.automaton-sovereign.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1733 tokens (~86/item across 20 items; 20 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 64% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http baianomarceloeduardo-jpg-automaton-token-safety- 'https://api.automaton-sovereign.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "baianomarceloeduardo-jpg-automaton-token-safety-": {
      "url": "https://api.automaton-sovereign.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "baianomarceloeduardo-jpg-automaton-token-safety-": {
      "type": "http",
      "url": "https://api.automaton-sovereign.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.baianomarceloeduardo-jpg-automaton-token-safety-]
url = "https://api.automaton-sovereign.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "baianomarceloeduardo-jpg-automaton-token-safety-": {
      "type": "remote",
      "url": "https://api.automaton-sovereign.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add baianomarceloeduardo-jpg-automaton-token-safety- --url 'https://api.automaton-sovereign.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  baianomarceloeduardo-jpg-automaton-token-safety-:
    url: "https://api.automaton-sovereign.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "baianomarceloeduardo-jpg-automaton-token-safety-": {
      "Transport": "http",
      "Url": "https://api.automaton-sovereign.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add baianomarceloeduardo-jpg-automaton-token-safety- -t streamable-http -u 'https://api.automaton-sovereign.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "baianomarceloeduardo-jpg-automaton-token-safety-": {
      "type": "http",
      "url": "https://api.automaton-sovereign.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 71, +53)

- [security regression] HTTPS: unverified → fail
- [security improvement] Stability: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] 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.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] Tool coverage: unverified → 100

### 2026-11-02 (score 18, −53)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] HTTPS: fail → unverified
- [security regression] Stability: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-27 (score 71, 0)

- [security] Stability: 0.97 → pass

### 2026-10-26 (score 71, +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.

### 2026-10-24 (score 70, +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.

### 2026-10-22 (score 69, +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.

### 2026-10-20 (score 68, +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.

### 2026-10-17 (score 67, +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.

## MCP tools (20)

### `x402_conformance_check` (~103 tokens)

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.

Input parameters:

- `url` (string, required): Full URL of the x402-protected endpoint to check.

### `simulate_base_transaction` (~175 tokens)

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 }.

Input parameters:

- `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, required): Target contract or recipient address on Base (0x...).
- `value` (string): ETH value in wei, decimal or 0x-hex (default 0).

### `token_scan` (~131 tokens)

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.)

Input parameters:

- `address` (string, required): Token contract on Base (0x...)
- `payment` (string): Optional X-PAYMENT base tx hash of the USDC payment.

### `tx_simulate` (~174 tokens)

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.)

Input parameters:

- `amount` (string, required): ETH for a buy, token units for a sell (positive decimal string)
- `payment` (string)
- `side` (string, required): Trade direction being simulated
- `token` (string, required): Token contract to trade (0x...)
- `wallet` (string, required): Address simulated as the trader (0x...)

### `approval_risk` (~136 tokens)

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.

Input parameters:

- `owner` (string, required): Address whose approvals are audited (0x...)
- `payment` (string)
- `spenders` (array): Extra spenders to check beyond the log window
- `token` (string, required): ERC-20 token contract (0x...)

### `liquidity_risk` (~130 tokens)

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.

Input parameters:

- `pair` (string): Analyze only this pool instead of all pools (0x...)
- `payment` (string)
- `token` (string, required): Token contract to audit (0x...)

### `sentinel_latest` (~163 tokens)

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.

Input parameters:

- `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

### `security_scan` (~141 tokens)

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.

Input parameters:

- `address` (string, required): Token or contract address on Base (0x...).
- `payment` (string): Optional X-PAYMENT base tx hash of the USDC payment.

### `attest` (~102 tokens)

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.

Input parameters:

- `data` (string, required): Payload to attest (any string).
- `payment` (string): Optional X-PAYMENT base tx hash of the USDC payment.

### `verify_attestation` (~51 tokens)

FREE. Verify a ledger entry by index or by data hash: recomputes hash, checks ECDSA signature and chain link.

Input parameters:

- `dataHash` (string)
- `index` (integer)

### `attestation_pubkey` (~35 tokens)

FREE. Get the ECDSA P-256 public key (PEM) and keyId used to sign ledger entries.

### `read_ledger` (~34 tokens)

FREE. Read the attestation ledger (paginated).

Input parameters:

- `from` (integer)
- `limit` (integer)

### `oracle_base` (~80 tokens)

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.

Input parameters:

- `payment` (string): Optional X-PAYMENT base tx hash of the USDC payment.

### `merkle_prove` (~66 tokens)

PAID 0.001 USDC/call. Generate a cryptographic Merkle inclusion proof for a list of items and target element.

Input parameters:

- `items` (array, required): Array of items
- `payment` (string)
- `target` (string): Target item or index

### `merkle_verify` (~44 tokens)

FREE. Verify a cryptographic Merkle inclusion proof against a root.

Input parameters:

- `item` (string, required)
- `proof` (array, required)
- `root` (string, required)

### `sentiment_analysis` (~61 tokens)

PAID 0.001 USDC/call. Web3 token risk, security checks, and sentiment scoring with signed verdict.

Input parameters:

- `asset` (string, required): Asset symbol (e.g. ETH, AERO, VIRTUAL)
- `payment` (string)

### `hash_sha256` (~42 tokens)

PAID 0.001 USDC/call. SHA-256 hex of a string.

Input parameters:

- `input` (string, required)
- `payment` (string)

### `uuid` (~31 tokens)

PAID 0.001 USDC/call. Generate a UUIDv4.

Input parameters:

- `payment` (string)

### `pricing` (~19 tokens)

FREE. Full pricing terms, endpoints, and payment mechanics.

### `health` (~15 tokens)

FREE. Service liveness and version.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/baianomarceloeduardo-jpg-automaton-token-safety-mcp/api#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 18
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 68
- 2026-10-20: 68
- 2026-10-19: 67
- 2026-10-18: 67
- 2026-10-17: 67
- 2026-10-16: 66
- 2026-10-15: 66
- 2026-10-14: 65
- 2026-10-13: 65
- 2026-10-12: 64
- 2026-10-10: 63
- 2026-10-09: 63
- 2026-10-06: 61
- 2026-10-04: 60
- 2026-10-03: 60

## Common questions

### 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.

## Links

- Remote endpoint: https://api.automaton-sovereign.workers.dev/mcp
- Website: https://api.automaton-sovereign.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/baianomarceloeduardo-jpg-automaton-token-safety-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/baianomarceloeduardo-jpg-automaton-token-safety-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/baianomarceloeduardo-jpg-automaton-token-safety-mcp/api