Skip to main content
agentscore-pay --mcp exposes the AgentScore CLI as an MCP server over stdio. AI agents and coding assistants can register the binary once and call every wallet, payment, and identity command as a tool; wallet management, x402/MPP payments, reputation lookups, on-the-fly assessments, verification sessions, operator credentials, and wallet attribution all in one server.

Install

Set AGENTSCORE_API_KEY for identity tools (reputation, assess, sessions, credentials, and associate-wallet) available on every tier and metered by quota (paid tiers raise the limits and unlock the full reputation response). Wallet and payment tools are local and need no key.

Register with your agent

This writes the MCP config for your agent so the tools appear automatically.

Manual config: Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

Manual config: Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) with the same shape.

Available tools

Every command from agentscore-pay --help is exposed as a tool. The most agent-relevant ones:

Wallet + payment

Identity (any tier: set AGENTSCORE_API_KEY)

Run agentscore-pay --llms for the full machine-readable manifest (or --llms --format json for JSON Schema).

Denial-code handling

assess decodes every denial code emitted by the AgentScore API into structured CliError codes with hint lines, so agents act from the response without parsing raw 4xx/5xx HTTP shapes. Codes include missing_identity, identity_verification_required, wallet_not_trusted, compliance_denied, wallet_signer_mismatch, wallet_auth_requires_wallet_signing, token_expired, invalid_credential, payment_required, api_error.

Use cases

Agent-to-agent trust; verify the reputation of another agent’s wallet before initiating a transaction. Gateway pre-screening; an agent acting as a gateway screens incoming requests by wallet reputation. Autonomous payment; discover a 402-gated endpoint, probe it with agentscore-pay check, dry-run with agentscore-pay pay --dry-run, then settle the payment via agentscore-pay pay. All without leaving the MCP loop. Identity bootstrap; an agent encounters an AgentScore-gated merchant for the first time, receives a missing_identity denial, calls sessions_create → polls sessions_get → uses the returned operator_token to retry the original request.

Environment variables

Running locally

The server communicates over stdio using the MCP protocol. Pipe {"jsonrpc":"2.0","id":1,"method":"tools/list"} to it to enumerate tools.