Mcp Ap2

io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.4Updated Oct 27, 2026

DEPRECATED: no live endpoint (AP2 is a spec; ap2.googleapis.com serves no API)

VerifiedSTDIODesktop onlyFinance AI & ML

Server details

Identifier: io.github.codespar/mcp-ap2
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account codespar for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.codespar%2Fmcp-ap2.svg)](https://sourceweft.com/mcp/io.github.codespar%2Fmcp-ap2?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Deprecated MCP server for Google's AP2 agent payment protocol; it exposes 22 payment, mandate and credential tools but reaches no live service.

What you can do: Register, list, inspect and revoke AI agents as payers, with trust status and spend usage
Request, inspect and list payment authorizations, then execute authorized payments and review transactions
Read audit trails and audit events across transactions, and list partner payment methods
Create and verify intent, cart and payment mandates, presentations and receipts
Resolve decentralized identifiers through an AP2 universal resolver
When to use it: Only for reference or experimentation with the AP2 specification's data model. The package is deprecated, no tool reaches a service, and the documented endpoints return errors, so it is not usable for real agent payments.
Requirements: Runs locally via npx from the npm package. Requires the AP2_API_KEY secret, sent as a Bearer token, and AP2_AGENT_ID, sent as an X-Agent-Id header; optional AP2_SANDBOX and AP2_BASE_URL. No portal issues these credentials, and the default endpoints do not work.

Before you install

Deprecated and alpha: no live endpoint, so calls cannot succeed. It asks for an API key and agent ID that no issuer provides. The tool set covers payments, mandates and receipts, so if a working endpoint were configured it could authorize and execute spending and revoke agent authorizations.

Installation

In SourceWeft

Open Mcp Ap2 in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-ap2

Deprecated: no live endpoint. Measured on 2026-09-27: ap2.googleapis.com answers every path with Google's generic Error 404 (Not Found) page, and sandbox.ap2.googleapis.com (used with AP2_SANDBOX=true) fails the TLS handshake, because the certificate served there covers *.googleapis.com and not the extra label. AP2 is an open specification, not an API Google hosts. No tool in this server reaches a service. The package is deprecated on npm and stays in this repository for reference only. If you have a working endpoint, point the server at it with AP2_BASE_URL. To bring the package back, open an issue in mcp-dev-latam with the provider's documented base URL.

Alpha release — published under the alpha npm dist-tag. Pin exact versions during 0.x.x-alpha. Install with npm install <pkg>@alpha.

MCP server for AP2 — Google's Agent-to-Agent Payment Protocol (authorization, audit, and trust for agentic payments)

[npm] [License: MIT]

What is AP2?

AP2 (Agent-to-Agent Payment Protocol) is Google's open framework for authorization, audit, and trust in agentic payments. It answers the critical questions: Who authorized this payment? What limits apply? What's the full audit trail?

The specification is published at ap2-protocol.org.

Quick Start

Claude Desktop

Add to ~/.config/claude/claude_desktop_config.json:

json

{  "mcpServers": {    "ap2": {      "command": "npx",      "args": ["-y", "@codespar/mcp-ap2"],      "env": {        "AP2_API_KEY": "your-key",        "AP2_AGENT_ID": "your-agent-id"      }    }  }}

{  "mcpServers": {    "ap2": {      "command": "npx",      "args": ["-y", "@codespar/mcp-ap2"],      "env": {        "AP2_API_KEY": "your-key",        "AP2_AGENT_ID": "your-agent-id"      }    }  }}

Claude Code

Cursor / VS Code

Add to .cursor/mcp.json or .vscode/mcp.json:

json

{  "servers": {    "ap2": {      "command": "npx",      "args": ["-y", "@codespar/mcp-ap2"],      "env": {        "AP2_API_KEY": "your-key",        "AP2_AGENT_ID": "your-agent-id"      }    }  }}

{  "servers": {    "ap2": {      "command": "npx",      "args": ["-y", "@codespar/mcp-ap2"],      "env": {        "AP2_API_KEY": "your-key",        "AP2_AGENT_ID": "your-agent-id"      }    }  }}

Tools (22)

Tool	Purpose
`register_agent`	Register an AI agent as a trusted payer in the AP2 network.
`get_agent`	Get agent registration details, trust status, and current spend usage
`list_agents`	List registered agents with optional filters
`revoke_agent`	Revoke an agent's payment authorization.
`authorize_payment`	Request payment authorization with scoped limits.
`get_authorization`	Get authorization details including status, limits, and expiry
`list_authorizations`	List payment authorizations with optional filters
`execute_payment`	Execute an authorized payment.
`get_audit_trail`	Get the complete audit trail for a transaction — every authorization, approval, execution, and settlement e..
`list_audit_events`	List audit events across all transactions with filters
`list_payment_methods`	List payment methods offered by the AP2 partner network
`get_transaction`	Get full transaction details including authorization, execution, and settlement status
`list_transactions`	List transactions with optional filters
`create_intent_mandate`	Create an AP2 intent mandate — a Verifiable Credential expressing the user's intent to delegate a transacti..
`create_cart_mandate`	Create an AP2 cart mandate — a signed, locked-cart commitment from a merchant binding line items, totals, a..
`create_payment_mandate`	Create an AP2 payment mandate — the final Verifiable Credential authorizing settlement against a cart mandate.
`verify_credential`	Verify a Verifiable Credential (intent, cart, or payment mandate).
`create_presentation`	Create a Verifiable Presentation bundling one or more credentials (e.g.
`verify_presentation`	Verify a Verifiable Presentation and all embedded credentials, including holder binding and challenge nonce.
`resolve_did`	Resolve a Decentralized Identifier (DID) to its DID document via the AP2 universal resolver.
`create_receipt`	Create a signed receipt for a settled payment — a tamper-evident record linking transaction, mandates, and..
`verify_receipt`	Verify a receipt's signature, issuer, and chain back to the originating mandates.

Authentication

The server sends AP2_API_KEY as an Authorization: Bearer header and AP2_AGENT_ID as an X-Agent-Id header on every request (src/index.ts:69-73).

There is no portal issuing those credentials. The developer portal this README used to link, developers.google.com/ap2, answers HTTP 404, as does the ap2-spec repository it pointed at. The published specification is at ap2-protocol.org.

Environment Variables

Variable	Required	Description
`AP2_API_KEY`	Yes	Sent as `Authorization: Bearer`
`AP2_AGENT_ID`	Yes	Sent as the `X-Agent-Id` header
`AP2_SANDBOX`	No	`true` switches `BASE_URL` to `https://sandbox.ap2.googleapis.com/v1`, which fails TLS

Use Cases

Authorized agent purchases — Agent requests spend authorization, gets approval with limits, then executes payment
Multi-agent commerce — Agent A authorizes Agent B to make payments on its behalf with scoped limits
Compliance & audit — Full audit trail of every authorization, approval, execution, and settlement
Cross-rail payments — AP2 bridges card payments, bank transfers, wallets, and x402 micropayments

Roadmap

v0.2 (planned)

create_policy — Define reusable authorization policies
delegate_authority — Allow agent-to-agent authorization delegation
get_spend_report — Get spend analytics and reports
OAuth 2.0 authentication flow

v0.3 (planned)

Webhook support for real-time authorization events
Multi-currency support with automatic FX
Integration with x402 as payment method

Want to contribute? Open a PR or request a tool.

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/payments/ap2/README.md at commit d0a519a

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.0-alpha.4LatestSep 27, 2026
v0.2.0-alpha.3Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts