← All servers
A

Automaton Token Safety

warnings

api.automaton-sovereign.workers.dev

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

https://api.automaton-sovereign.workers.dev/mcpWebsiteUnknownnot observedMCP 2025-06-18v2.2.3last checked 22 Nov 2026spoke MCP on 100% of 95 checks (30 days)initialize in 911 ms

Last checked 22 Nov 2026

  • ✓Answered the MCP handshake (MCP 2025-06-18)
  • –Auth scheme could not be determined
  • ✓Lists 20 tools
  • !1 warning
  • ✓Spoke MCP on 95 of 95 checks (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

–Claude CodeUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude Code docs · read on 2026-08-30

–Claude (claude.ai & Desktop)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

–ChatGPTUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

ChatGPT docs · read on 2026-08-30

–CursorUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Cursor docs · read on 2026-08-30

–VS Code (Copilot)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 22 Nov 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
Unknown
Protected-resource metadata
✕Not found

Without it a client has to guess where the authorization server lives.

Anonymous access
Refused — credentials required

What the probe found

warningThe server refused to initialize

It speaks JSON-RPC but rejected the handshake: "Not found"

No server card

Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.

Tools

approval_riskattestattestation_pubkeyhash_sha256healthliquidity_riskmerkle_provemerkle_verifyoracle_basepricingread_ledgersecurity_scansentiment_analysissentinel_latestsimulate_base_transactiontoken_scantx_simulateuuidverify_attestationx402_conformance_check

Contract history

30 Sep 2026v2.2.3no contract changes
27 Sep 2026v2.2.2first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sign in to claim this listing by proving control of its host.

Sponsor this listing

Pins it in a sponsor slot on the directory front page for 30 days, labelled Sponsored.

Sign in to sponsor · $59 / 30 days

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge
Markdown[![MCP status](https://mcpi.app/servers/automaton-token-safety/badge.svg)](https://mcpi.app/servers/automaton-token-safety)
HTML<a href="https://mcpi.app/servers/automaton-token-safety"><img src="https://mcpi.app/servers/automaton-token-safety/badge.svg" alt="MCP status" height="20"></a>

Contract badge, opt-in: what the probe has observed of this contract over 90 days. It shows recent breaking changes, and it is an observation, not a guarantee.

MCP contract badge
Markdown[![MCP contract](https://mcpi.app/servers/automaton-token-safety/contract.svg)](https://mcpi.app/servers/automaton-token-safety)