ChainWard MCP server: check a counterparty on Base before you pay it (EAS attestations + risk reports), plus read-side intelligence on AI agents
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
lookup_agentLook 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.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.
No input schema was published for this tool.
get_agent_profileFetch 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_age…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_age…
No input schema was published for this tool.
get_agent_economicsFetch ACP-derived economics for an agent: lifetime revenue, agentic gross dollar product (aGDP), job count, success rate, unique buyer count, 30-day on-chain gas cost, profit, and gas efficiency. Use when the user asks about agent revenue, profitability, or whether on-chain activity justifies a mar…Fetch ACP-derived economics for an agent: lifetime revenue, agentic gross dollar product (aGDP), job count, success rate, unique buyer count, 30-day on-chain gas cost, profit, and gas efficiency. Use when the user asks about agent revenue, profitability, or whether on-chain activity justifies a mar…
No input schema was published for this tool.
get_observatory_overviewEcosystem-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?".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?".
No input schema was published for this tool.
get_top_agentsRanked 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".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".
No input schema was published for this tool.
get_activity_feedRecent labeled-agent activity across the ecosystem. Use when the user asks "what is happening right now?" or wants a live feed.Recent labeled-agent activity across the ecosystem. Use when the user asks "what is happening right now?" or wants a live feed.
No input schema was published for this tool.
list_decodesList 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.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.
No input schema was published for this tool.
find_decodes_for_addressFind 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...?".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...?".
No input schema was published for this tool.
check_counterpartyBefore paying or trusting an address on Base, check what ChainWard's on-chain risk check says about it. Returns the neutral signal band and flag ids, plus the EAS attestation on Base (uid + explorer link) when ChainWard has published one, so the result is verifiable on-chain. Never a safety verdict…Before paying or trusting an address on Base, check what ChainWard's on-chain risk check says about it. Returns the neutral signal band and flag ids, plus the EAS attestation on Base (uid + explorer link) when ChainWard has published one, so the result is verifiable on-chain. Never a safety verdict…
No input schema was published for this tool.
9 of 9 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
ChainWard MCP server: check a counterparty on Base before you pay it (EAS attestations + risk reports), plus read-side intelligence on AI agents
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+41 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.