Base Token Facts
NPM · BASE-FACTS-MCP
Base token checks for agents: simulated buy and sell, taxes, honeypots. Pay per call in USDC (x402).
Available components
Last scanned (11 hours ago)
Scores higher than 39% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 112 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 582 tokens (~64/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 13 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 78 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 7 Oct 26 39
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 18 Oct 2026 · Analysed npm/base-facts-mcp@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 112 packages
| Packages resolved | 112 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
base_facts_budget Spending so far (free) ~28
How much this session has paid, the per-call cap and the session budget. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
base_gas Base gas snapshot ($0.001) ~33
Current Base base fee, max priority fee, gas price (wei) and block usage. Costs $0.001.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
base_token_facts Base token facts ($0.005) ~61
Raw on-chain facts about a Base token contract: ERC20 metadata, owner(), proxy standard and implementation, admin function selectors found in the bytecode, block number. Costs $0.005.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Token contract address on Base |
No output schema declared.
No examples provided.
base_token_sellcheck Base token sell check ($0.005) ~89
Honeypot and tax check for a Base token: simulates a small buy and an immediate sell on its deepest pool (Uniswap v2/v3/v4, Aerodrome) inside eth_call. Returns buy tax, sell tax, round-trip loss and whether the sell reverted. Paid with x402 from your payer wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Token contract address on Base |
No output schema declared.
No examples provided.
base_token_sellcheck_size Base token sell check at your trade size ($0.01) ~120
The sell check at YOUR size: simulates a buy of amountEth (0.001 to 10 ETH) and an immediate sell inside eth_call. Returns buy tax, sell tax, round-trip loss, the buy price impact against a small trade (buyPriceImpactPct) and a depthWarning when the size is larger than the pool can absorb. Costs $0.01.
| Name | Type | Req | Description |
|---|---|---|---|
| amountEth | string | yes | Trade size in ETH, 0.001 to 10 |
| token | string | yes | Token contract address on Base |
No output schema declared.
No examples provided.
base_token_verdict Base token verdict ($0.01) ~93
Before buying a token on Base: risk level, score and flags (upgradeable proxy, mint, pause, blacklist, owner not renounced, DEX liquidity on Uniswap v2/v3 and Aerodrome), each with the on-chain fact behind it. Facts and heuristics, not financial advice. Costs $0.01 in USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Token contract address on Base |
No output schema declared.
No examples provided.
base_tx_summary Base transaction summary ($0.003) ~43
Status, from/to, gas used, fee in ETH and decoded ERC20 transfers of a Base transaction. Costs $0.003.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
No output schema declared.
No examples provided.
base_wallet_snapshot Base wallet snapshot ($0.002) ~48
ETH and USDC balances, transaction count (nonce) and whether the address is a contract, on Base. Costs $0.002.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address on Base |
No output schema declared.
No examples provided.
basename_resolve Basename resolve ($0.002) ~67
Resolve a Basename (name.base.eth) to its address, or an address to its verified primary Basename. Give exactly one of name or address. Costs $0.002.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| name | string | – | e.g. jesse.base.eth |
No output schema declared.
No examples provided.
How do I install the Base Token Facts MCP server?
Base Token Facts runs locally as an npm package, launched with npx -y base-facts-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · base-facts-mcp
claude mcp add yankiifr-base-facts-mcp -- npx -y base-facts-mcp
What is the Base Token Facts MCP server?
Base Token Facts is an MCP server listed in the public MCP registry as io.github.yankiifr/base-facts-mcp. Base token checks for agents: simulated buy and sell, taxes, honeypots. Pay per call in USDC (x402). This page covers its npm package (base-facts-mcp).
Is the Base Token Facts MCP server safe to use?
Base Token Facts scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. 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 Facts MCP server expose?
Base Token Facts exposes 9 tools: base_token_verdict, base_token_sellcheck, base_token_sellcheck_size, base_token_facts, base_wallet_snapshot, and 4 more. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.
Is the Base Token Facts MCP server still maintained?
Base Token Facts is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Base Token Facts MCP server under?
Base Token Facts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.