io.github.saltxd/chainward
NPM · CHAINWARD-MCP-SERVER
Check a Base or BNB Chain address before you pay it: on-chain risk reports, EAS attestations.
Available components
Last scanned (16 hours ago)
Scores higher than 53% 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 Security98
- 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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 793 tokens (~88/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 Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +37
- Injection markers: unverified → pass ▲ security
- Schema quality: 68 → 88 ▼ functional
- Tool coverage: 0% → 17% ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.50 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: excellent → good functional
- 12 Oct 26 −34
- Stability: 0.40 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.1 → 0.2.3 functional
- 11 Oct 26 +2
- Security disclosure: pass → unverified ▼ functional
- 4 Oct 26 +3
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.17 ▲ functional
- Security disclosure: fail → pass ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Sept 26 53
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 17 Oct 2026 · Analysed npm/chainward-mcp-server@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 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
check_counterparty ~233
Before paying or trusting an address on Base or BNB Chain, get ChainWard's verdict on it (the `verdict` field): a machine label pay / hold / unknown, a human text (Pay, Hold, Inactive, No track record or Couldn't check), the one reason it rests on, and its limits. The flags under it are the evidence. Pass chain: 'bsc' for a BNB Chain address (default 'base'). On Base, also the EAS attestation (uid + explorer link) when ChainWard has published one, so the result is verifiable on-chain (BNB Chain reports are not attested yet). Read from on-chain behavior only: Pay means nothing was found against paying, not a guarantee. If the address has no report yet, say so and point to the free check at https://chainward.ai (https://chainward.ai/?chain=bsc for BNB Chain).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain the address is on: 'base' (default) or 'bsc' (BNB Chain) |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
find_decodes_for_address ~61
Find every published ChainWard Decode that references a given Ethereum address. Returns an array (possibly empty) of decode metadata + URL. Use when the user asks "has ChainWard written about 0x...?".
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
get_activity_feed ~35
Recent labeled-agent activity across the ecosystem. Use when the user asks "what is happening right now?" or wants a live feed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_agent_economics ~142
Fetch economics for an ACP agent. From ACP (lifetime): revenue, agentic gross dollar product (aGDP), job count, success rate, unique buyer count. From the chain (last 30 days): revenue30d (USD value the wallet received), gasCost30d, txCount30d, profit30d (revenue30d minus gasCost30d) and gasEfficiency (revenue30d / gasCost30d). Do not compare lifetime revenue with 30-day gas. Use when the user asks about agent revenue, profitability, or whether on-chain activity justifies a market cap.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
get_agent_profile ~95
Fetch a full profile for a labeled agent on Base: identity, 24h/7d transaction stats, 7-day balance history (hourly buckets), 30-day gas history (daily), the most recent 20 transactions, and any related published Decodes. Returns 404 if ChainWard does not label this address. Heavier than lookup_agent — use when the user wants detail.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
get_observatory_overview ~61
Ecosystem-wide stats: total tracked agents, 24h transaction volume across all agents, gas burned, active-agent count, total portfolio value. Use when the user asks broad questions like "how active is the AI agent economy on Base?".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_top_agents ~44
Ranked leaderboard of agents on Base by transaction volume / revenue / activity. Use when the user asks "who are the top agents?" or "show me the most active agents".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_decodes ~47
List every published ChainWard Decode (investigative article on agent on-chain behavior), newest first. Each entry includes title, subtitle, date, URL, and the addresses that decode mentions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_agent ~75
Look up an Ethereum address on Base to see if ChainWard labels it as a known AI agent. Returns the label (name, framework), any ACP profile data, and pointers to published Decodes that mention this address. Use this BEFORE the user transacts with an unfamiliar address or token deployer.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.saltxd/chainward MCP server?
io.github.saltxd/chainward runs locally as an npm package, launched with npx -y chainward-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · chainward-mcp-server
claude mcp add saltxd-chainward -- npx -y chainward-mcp-server
What is the io.github.saltxd/chainward MCP server?
io.github.saltxd/chainward is an MCP server listed in the public MCP registry as io.github.saltxd/chainward. Check a Base or BNB Chain address before you pay it: on-chain risk reports, EAS attestations. This page covers its npm package (chainward-mcp-server).
Is the io.github.saltxd/chainward MCP server safe to use?
io.github.saltxd/chainward scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 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 io.github.saltxd/chainward MCP server expose?
io.github.saltxd/chainward exposes 9 tools: lookup_agent, get_agent_profile, get_agent_economics, get_observatory_overview, get_top_agents, and 4 more. Their descriptions and schemas cost roughly 793 tokens of context every time the server is loaded.
Is the io.github.saltxd/chainward MCP server still maintained?
io.github.saltxd/chainward is still listed as active in the MCP registry. We last reached this channel on 17 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 io.github.saltxd/chainward MCP server under?
io.github.saltxd/chainward declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.