Base Token Audit — ERC-20 honeypot check and swap route data
REMOTE · ANGEL.OROBOROS-DESIGN.COM
ERC-20 honeypot and rug-pull check on Base and Ethereum, plus free swap route data.
Available components
Last scanned (21 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 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 Security63
- 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 1 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 547 tokens (~273/item across 2 items; 2 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 Management0
- Stability check failed: schema churn in the 7 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “buy_pack_with_card” 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
- “buy_pack_with_card” reworded the description of “email” cosmetic
- “token_risk” reworded the description of “bundle_token” cosmetic
- “token_risk” reworded the description of “payer_address” cosmetic
- Tool “buy_pack_with_card” changed its title: TradeSignal: pack by card → Angel: 5,000 calls by card cosmetic
- 16 Nov 26 0
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “get_swap_route” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “buy_pack_with_card” rewrote its description, which is the text the model reads security
- Tool coverage: 62% → 57% ▼ functional
- Schema quality: 817 → 536 ▲ functional
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “token_risk” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 62
First indexed and scored.
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 21 Nov 2026 · Probed https://angel.oroboros-design.com/mcp/base-token-audit
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.oroboros-design.com | CN=YR2,O=Let's Encrypt,C=US | 28 Oct 2026 | 26 Jan 2027 | RSA 2048 | SHA256-RSA | 5c407b368cf93bd9f2f03db9f58a77f6c9f |
| SANs: *.oroboros-design.com, oroboros-design.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of angel.oroboros-design.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| oroboros-design.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://angel.oroboros-design.com/mcp/base-token-audit | Verified | 200 | |
| http (plaintext) | http://angel.oroboros-design.com/mcp/base-token-audit | HTTPS enforced | 308 | https://angel.oroboros-design.com/mcp/base-token-audit |
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 →
buy_pack_with_card Angel: 5,000 calls by card ~118
For businesses without USDC: 5,000 calls €9.00, one-time, 90 days, businesses only, paid in EUR by card or Link. Returns checkout_url for a person to open; the checkout asks for the company or freelance name. After payment the success page (Accept: application/json) returns the key, and it is e-mailed. After: any tool with bundle_token.
| Name | Type | Req | Description |
|---|---|---|---|
| calls | integer | – | – |
| string | – | Where the key is sent (optional; Stripe asks otherwise). |
No output schema declared.
No examples provided.
token_risk Honeypot and rug-pull check for an ERC-20 before swap or approve ~295
Honeypot and rug-pull check for an ERC-20 on Base or Ethereum before a swap, approval or signature, read straight from the contract: upgradeable proxy (EIP-1967, beacon, clone), owner powers in the bytecode (mint, pause, blacklist, fee or max-tx setters, trading switch, burn from any address), owner renounced or active and the owner's share of supply; known issuers labeled. Risk low, medium or high with reasons. Signals, not investment advice. Free with a key (500 calls) or 5 calls a day without one; then 0.02 USDC per call via x402, or 1 call from a key. After: preflight before your agent pays or signs on the site that offers this token (the result's next field has the exact call).
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_token | string | – | Your key instead of paying per call: free (500 calls, POST /key) or bought by card. The connection header X-Bundle-Token works too. |
| chain | string | – | – |
| payer_address | string | – | Wallet you pay from (optional; the x402 price is the same for every address). |
| payment_tx | string | – | Hash of a USDC transfer on Base to payTo (≥ the price, ≤ 72 h old) instead of an x402 signature. |
| token | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Base Token Audit — ERC-20 honeypot check and swap route data MCP server?
Base Token Audit — ERC-20 honeypot check and swap route data is a hosted endpoint at https://angel.oroboros-design.com/mcp/base-token-audit, 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 · angel.oroboros-design.com
claude mcp add --transport http com-oroboros-design-angel-base-token-audit 'https://angel.oroboros-design.com/mcp/base-token-audit'
What is the Base Token Audit — ERC-20 honeypot check and swap route data MCP server?
Base Token Audit — ERC-20 honeypot check and swap route data is an MCP server listed in the public MCP registry as com.oroboros-design.angel/base-token-audit. ERC-20 honeypot and rug-pull check on Base and Ethereum, plus free swap route data. This page covers its hosted endpoint (https://angel.oroboros-design.com/mcp/base-token-audit).
Is the Base Token Audit — ERC-20 honeypot check and swap route data MCP server safe to use?
Base Token Audit — ERC-20 honeypot check and swap route data scores 62 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 Base Token Audit — ERC-20 honeypot check and swap route data MCP server expose?
Base Token Audit — ERC-20 honeypot check and swap route data exposes 2 tools: token_risk, buy_pack_with_card. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.
Does the Base Token Audit — ERC-20 honeypot check and swap route data MCP server require authentication?
No. We connected to Base Token Audit — ERC-20 honeypot check and swap route data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Base Token Audit — ERC-20 honeypot check and swap route data MCP server still maintained?
Base Token Audit — ERC-20 honeypot check and swap route data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Base Token Audit — ERC-20 honeypot check and swap route data MCP server?
VerifyMCP ran 12 checks on Base Token Audit — ERC-20 honeypot check and swap route data, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Base Token Audit — ERC-20 honeypot check and swap route data: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.