Token Safety (Base)
REMOTE · TOKEN-SAFETY-MCP.RESTOCKALARM.WORKERS.DEV
Base token safety: one-call verdict, risk score, rug check, holders, momentum. x402 + free demo.
Available components
Last scanned (7 hours ago)
Scores higher than 44% 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 5 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 849 tokens (~169/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management38
- Stability check failed: schema churn in the 17 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 31 to 35.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 21 to 25.
- 30 Oct 26 −1
- Schema quality: 134 → 169 ▼ functional
- “holder_check” reworded the description of “address” cosmetic
- “momentum_score” reworded the description of “address” cosmetic
- “rug_check” reworded the description of “address” cosmetic
- “token_risk” reworded the description of “address” cosmetic
- “token_verdict” reworded the description of “address” cosmetic
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “holder_check” rewrote its description, which is the text the model reads security
- Tool “rug_check” rewrote its description, which is the text the model reads security
- Tool “token_risk” rewrote its description, which is the text the model reads security
- Tool “token_verdict” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 8 to 11.
- 27 Oct 26 −2
- Stability: 0.23 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “token_safety_demo” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “token_verdict” rewrote its description, which is the text the model reads security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 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://token-safety-mcp.restockalarm.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=restockalarm.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 66ad299737d55ae0be2abd504f58c66d93c |
| SANs: *.restockalarm.workers.dev, restockalarm.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 token-safety-mcp.restockalarm.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://token-safety-mcp.restockalarm.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://token-safety-mcp.restockalarm.workers.dev/mcp | Inconclusive | 405 |
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 →
holder_check ~119
PAUSED: holder_check answers paused without asking for payment and is never charged (its top-holder source was a third-party API we no longer use). For holder concentration use token_risk (holder_concentration).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht… |
No output schema declared.
No examples provided.
momentum_score ~131
Momentum score 0-100 for an ERC-20 on Base from 24 h volume, volume vs liquidity and price change, with confidence low/medium/high. Null for stablecoins. Use to rank Base tokens by activity. $0.02 via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht… |
No output schema declared.
No examples provided.
rug_check ~139
Rug-pull check for an ERC-20 on Base: rug_pull true/false, confidence and 5 signals (liquidity removal, wash trading, LP lock, owner wallet, sell tax from our own sell simulation). Use before buying a new Base token. $0.02 via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht… |
No output schema declared.
No examples provided.
token_risk ~141
Risk score 0-100 (higher = riskier) for an ERC-20 on Base: derived liquidity view, holder concentration, sell-blocked/tax flags from our own on-chain sell simulation. Use before buying or listing an unknown Base token. $0.01 via x402. Not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht… |
No output schema declared.
No examples provided.
token_verdict ~167
One-call verdict for an ERC-20 on Base: runs token risk (incl. holder concentration), rug-pull and momentum checks plus contract flags (proxy, blacklist, pause, selfdestruct, own on-chain sell simulation) and returns avoid / high_risk / caution / low_risk with a one-line English summary. Use once before buying or listing an unknown Base token. $0.01 via x402. Not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET ht… |
No output schema declared.
No examples provided.
How do I install the Token Safety (Base) MCP server?
Token Safety (Base) is a hosted endpoint at https://token-safety-mcp.restockalarm.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 · token-safety-mcp.restockalarm.workers.dev
claude mcp add --transport http dev-workers-restockalarm-token-safety-mcp-token- 'https://token-safety-mcp.restockalarm.workers.dev/mcp'
What is the Token Safety (Base) MCP server?
Token Safety (Base) is an MCP server listed in the public MCP registry as dev.workers.restockalarm.token-safety-mcp/token-safety. Base token safety: one-call verdict, risk score, rug check, holders, momentum. x402 + free demo. This page covers its hosted endpoint (https://token-safety-mcp.restockalarm.workers.dev/mcp).
Is the Token Safety (Base) MCP server safe to use?
Token Safety (Base) scores 63 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 Token Safety (Base) MCP server expose?
Token Safety (Base) exposes 5 tools: token_verdict, token_risk, rug_check, holder_check, momentum_score. Their descriptions and schemas cost roughly 697 tokens of context every time the server is loaded.
Does the Token Safety (Base) MCP server require authentication?
No. We connected to Token Safety (Base) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Token Safety (Base) MCP server still maintained?
Token Safety (Base) 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.