Base Token Safety Inspector MCP server
io.github.heyryker/base-token-safetyheyrykerstreamable-httpv1.0.1Scanned
Pay-per-call rug-pull, honeypot and token safety checks for any ERC-20 on Base (x402, USDC).
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Base Token Safety Inspector MCP server can do
The Base Token Safety Inspector MCP server is published by the GitHub account heyryker. It has 2 tools. It can create or change data (2 tools: token_safety_check and token_deep_safety_check), but cannot delete data. None of its tools only reads.
2 tools bring in text other people can write (token_safety_check and token_deep_safety_check).
The fixed checks matched 2 findings (base64-blob). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
token_deep_safety_checkDeep Base token safety / rug-pull / honeypot check: everything in token_safety_check plus DEX liquidity (Uniswap, Aerodrome), holder shares, mint/blacklist/fee functions, a simulat…Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The input schema at properties.address.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.address.description: "...ex characters, e.g. 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC). Checksummed..."
Description, as the server wrote it Deep Base token safety / rug-pull / honeypot check: everything in token_safety_check plus DEX liquidity (Uniswap, Aerodrome), holder shares, mint/blacklist/fee functions, a simulated buy, and a 0-100 risk score with a low/medium/high verdict. Price: $0.02 USDC on Base via x402, charged only on success.
Annotations the server declares
- title: Base token deep safety check (rug-pull / honeypot)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
token_safety_checkBase token safety check before you swap or accept a token: ERC-20 metadata, supply, upgradeable proxy, owner / renounced, paused, and risk flags.Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The input schema at properties.address.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.address.description: "...ex characters, e.g. 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC). Checksummed..."
Description, as the server wrote it Base token safety check before you swap or accept a token: ERC-20 metadata, supply, upgradeable proxy, owner / renounced, paused, and risk flags. Read-only, about 1 second. Price: $0.005 USDC on Base via x402, charged only on success.
Annotations the server declares
- title: Base token safety check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:19 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://a1.project-swarm.xyz/mcp: tools/list returned 2 tools to an anonymous client, including token_safety_check (write), token_deep_safety_check (write)
Findings
Matches of fixed checks, with the text they matched.
The input schema at properties.address.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.address.description: "...ex characters, e.g. 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC). Checksummed..."
The input schema at properties.address.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.address.description: "...ex characters, e.g. 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC). Checksummed..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:token_deep_safety_checkChanges thingstitledescriptioninputSchemaannotations
- Changed:token_safety_checkChanges thingstitledescriptioninputSchemaannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http base-token-safety https://a1.project-swarm.xyz/mcpclaude mcp add --transport http base-token-safety https://a1.project-swarm.xyz/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__base-token-safety__token_safety_check",
"mcp__base-token-safety__token_deep_safety_check"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as base-token-safety. Review it before you use it.
Capability tags behind 2 rules
- mcp__base-token-safety__token_safety_check untrusted-input
- mcp__base-token-safety__token_deep_safety_check untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.heyryker/base-token-safety/verify?hash=43751fddc7396feadb093cada4327c03b74fc3299c910fa8cfb9da416b15863d" | jq -e '.changed == false'Pinned hash 43751fddc739, from Nov 17, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.heyryker/base-token-safety/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.heyryker/base-token-safety)Source: MCP Registry. Synced Nov 17, 2026, 04:17 UTC.
Base Token Safety Inspector MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Base Token Safety Inspector MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Base Token Safety Inspector MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Base Token Safety Inspector MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Base Token Safety Inspector MCP server have?
- 2 tools: 2 write. token_safety_check and token_deep_safety_check.
Does the Base Token Safety Inspector MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Base Token Safety Inspector MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Base Token Safety Inspector MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.