Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agent402.Tools: pay-per-call web tools

NPM · AGENT402-MCP · 2 COMPONENTS

Agentic Finance: 500+ agent tools, multi-chain USDC over x402 or MPP, or free via proof-of-work

+15 this week 87 Trust /100

Last scanned (8 hours ago)

Scores higher than 91% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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 Security91
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects ws 8.20.1, reached via viem > ws. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 210 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to MikeyPetrillo/Agent402). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 700 tokens (~140/item across 5 items; 5 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 Management71
  • Stability check failed: the tool surface changed between 0.13.7 and 0.13.27: 2 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Changelog

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.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.13.26 → 0.13.27 functional
  • 1 Nov 26 0
    • Tool safety: pass → unverified ▼ security
    • Stability: fail → unverified ▼ security
    • CVE-2023-54404 no longer affects this package ▲ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Package version: 0.13.25 → 0.13.26 functional
    • Package version: 0.13.11 → 0.13.25 functional
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.13.24 → 0.13.25 functional
  • 29 Oct 26 −15
    • CVE-2026-48779 affects this package: high ▼ security
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: fail → unverified ▼ security
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Dependency health: 0.94 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 0.13.20 → 0.13.24 functional
    • Package version: 0.13.20 → 0.13.22 functional
    • Package version: 0.13.20 → 0.13.21 functional
  • 28 Oct 26 0
    • Tool safety: pass → unverified ▼ security
    • Stability: fail → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 203 → 140 ▲ functional
    • Destructive annotations: 0 → pass functional
    • Package version: 0.13.19 → 0.13.20 functional
  • 26 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
Diagnostics

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 5 Nov 2026 · Analysed npm/agent402-mcp@0.13.27

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo MikeyPetrillo/Agent402
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/MikeyPetrillo/Agent402/.github/workflows/deploy.yml@refs/heads/main
Rekor log index 3637493940
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:e0fe8ad8f2a1b7579c8063efed027c5fd1ed801bd1aa44d3eb961d4862bbcf01aec067ccd8fc7c9e6117f0a184c2d5ef96ec9de32253b462beb748ae4

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-96hv-2xvq-fx4p CVE-2026-48779 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 210 packages
Packages resolved 210
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~430 tokens

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 →

Tool Tokens
catalog.call ~132

Call any Agent402 tool by slug (find slugs with catalog.find or catalog.search). Payment is handled automatically: USDC via x402 if this server has a wallet key, otherwise free proof-of-work on eligible pure-CPU tools (no wallet needed). Wallet-keyed highlights: live search/answer, stock-quote, render, transcribe, memory, and the /v1 LLM gateway tiers.

NameTypeReqDescription
paramsobject–Tool input parameters, matching the tool's inputSchema
slugstringyesTool slug from catalog.search, e.g. "search" or "unit-convert"
NameTypeReqDescription
result–yesNative tool output (shape depends on slug)
slugstringyesCatalog slug that ran

No examples provided.

catalog.find ~108

Resolve a plain-language task to the single best-matching Agent402 tool through the hosted /api/find resolver. Returns { task, matches } with the top pick first. Run the pick with catalog.call and the slug and params it lists. Use catalog.search to compare several candidates.

NameTypeReqDescription
limitnumber–Max results (default 5)
taskstringyesWhat you want to do, e.g. "search the web for x402 adoption" or "convert miles to km"
NameTypeReqDescription
hintstring––
matchesarray–Alias of results on the stdio package
messagestring––
relatedSellersarray––
resultsarray–Ranked matches; top pick first
taskstringyes–
usagestring––
workflowsarray––
workflowsUsagestring––

No examples provided.

catalog.search ~114

Keyword search over the Agent402 catalog of 500+ tools (0 loaded by this server). Returns matching tools and workflow templates; run one with catalog.call. Pure-CPU tools are free through proof-of-work; the others are paid per call in USDC when a wallet key is set.

NameTypeReqDescription
limitnumber–Max results (default 10)
querystringyesWhat you need, e.g. "search the web for x402", "answer a question with citations", "convert miles to km"
NameTypeReqDescription
hintstring–Shown when the match is weak - points at demand.request
messagestring–Present when nothing matched
resultsarrayyesMatching catalog tools
usagestring––
workflowsarray–Matching skill-pack workflows
workflowsUsagestring––

No examples provided.

payment.info ~45

How this MCP server is paying for Agent402 calls (USDC wallet vs proof-of-work), and what that unlocks. Includes Claude Code / Cursor / npm install one-liners.

Input schema present but exposes no named parameters.

NameTypeReqDescription
balanceAndHistoryobject––
connectorstring––
ecosystemstring––
freeTierobject––
installobject––
modestring––
networkstring––
networksarray––
notestring––
payobject––
payableWithComputeinteger––
positioningstring––
servicestring––
solanaWallet––Solana address when a key is configured
spendControls–––
toolsinteger––
wallet––EVM address when a key is configured
walletOnlyinteger––
workflows––Skill-pack count or detail object

No examples provided.

server.describe ~31

Describe this stdio MCP server: the tools it lists, install commands, free vs paid, and discovery URLs.

Input schema present but exposes no named parameters.

NameTypeReqDescription
clientsSeenSinceBootobject––
connectorstring––
docsstring––
ecosystemstring––
freeHereinteger––
installobject––
maintainerstringyes–
missingAToolstring––
paidAccessstring––
rateLimitstring––
servicestringyes–
startHereobjectyes–
toolsinteger––
toolsEvergreenstring––
walletOnlyinteger––
workflowsobject––

No examples provided.

Install

How do I install the Agent402.Tools: pay-per-call web tools MCP server?

Agent402.Tools: pay-per-call web tools runs locally as an npm package, launched with npx -y agent402-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 · agent402-mcp

# add to Claude Code
claude mcp add mikeypetrillo-agent402 -- npx -y agent402-mcp
Common questions

What is the Agent402.Tools: pay-per-call web tools MCP server?

Agent402.Tools: pay-per-call web tools is an MCP server listed in the public MCP registry as io.github.MikeyPetrillo/agent402. Agentic Finance: 500+ agent tools, multi-chain USDC over x402 or MPP, or free via proof-of-work. This page covers its npm package (agent402-mcp).

Is the Agent402.Tools: pay-per-call web tools MCP server safe to use?

Agent402.Tools: pay-per-call web tools scores 87 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Agent402.Tools: pay-per-call web tools MCP server expose?

Agent402.Tools: pay-per-call web tools exposes 5 tools: catalog.search, catalog.find, catalog.call, payment.info, server.describe. Their descriptions and schemas cost roughly 430 tokens of context every time the server is loaded.

Is the Agent402.Tools: pay-per-call web tools MCP server still maintained?

Agent402.Tools: pay-per-call web tools is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Agent402.Tools: pay-per-call web tools MCP server under?

Agent402.Tools: pay-per-call web tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.