Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add OrcaQubits/agentic-commerce-skills-plugins --skill ap2-mcp-servergit clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-mcp-server)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-mcp-server"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-mcp-server"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/ap2-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.00947 |
| Opus 5.5 | $0.00015 | $0.00379 |
| Sonnet 5.5 | $0.00008 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
ap2-mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AP2 MCP Server Integration
Before writing code
Fetch live docs:
- Fetch
https://ap2-protocol.org/ap2/specification/for MCP server references - Fetch
https://ap2-protocol.org/ap2/implementation_considerations/for MCP integration details - Fetch
https://github.com/google-agentic-commerce/AP2/releasesto check MCP server availability status - Web-search
site:github.com google-agentic-commerce AP2 MCP serverfor MCP implementations
Conceptual Architecture
AP2 + MCP
While AP2's primary integration is with A2A (agent-to-agent), it also integrates with MCP (Model Context Protocol) for tool-based access to payment capabilities:
- A2A — Agent-to-agent: Shopping Agent ↔ Merchant Agent communication
- MCP — Agent-to-tool: Agent accessing payment APIs as tools
MCP's Role in the Stack
MCP provides the foundational layer for connecting agents to external resources:
Agent
├── A2A → Other Agents (Merchant, CP, MPP)
└── MCP → Payment Tools (APIs, databases, services)
AP2 MCP Server
The AP2 MCP server exposes payment-related tools that agents can call:
- Payment method management tools
- Mandate creation and signing tools
- Transaction status tools
- Receipt retrieval tools
Roadmap Status
AP2's primary binding has been the A2A extension, with MCP support arriving alongside it and expanding over time. Since the protocol moved to the FIDO Alliance for community governance, the roadmap is set there rather than in a single vendor repo.
Resolve the current state before building — do not assume the split above still holds:
- Check the AP2 repo's
CHANGELOG.mdandcode/for what the MCP surface actually exposes today. - Check FIDO Alliance working-group output (Agentic Authentication TWG, Payments TWG) for where the standard is heading.
- Confirm which binding — A2A extension or MCP — is the supported path for your integration.
MCP Tool Patterns for Payments
Note: The following tool names are entirely speculative/hypothetical examples illustrating what an AP2 MCP server might expose. They are not from any published AP2 MCP server specification or implementation. Always check the latest AP2 roadmap and GitHub repositories for actual MCP tool definitions.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +1 lines 799dcc3c4682
- 2mo ago First seen · 98 lines · 38 tokens per session scan A d4368fc97660
ap2-mcp-server is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (40 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 947 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
internet-court
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow…
okx-agent-payments-protocol
Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channelid, opening / closing / topping up / settling / refunding a…
okx-dapp-discovery
Plugin router for 20 third-party DeFi protocols (Polymarket, Aave, Hyperliquid, PancakeSwap, Morpho, Raydium, Curve, Compound, Pendle, Lido, ether.fi, GMX, Kamino, Orca, Meteora, Clanker, pump.fun, Uniswap) and their protocol-native tokens (HYPE, HLP, eETH, weETH, stETH, wstETH, LDO, GHO, CAKE, CRV, COMP, RAY, ETHFI…
jupiter-lend
Interact with Jupiter Lend Protocol. Read-only SDK (@jup-ag/lend-read) for querying liquidity pools, lending markets (jlTokens), and vaults. Write SDK (@jup-ag/lend) for lending (deposit/withdraw) and vault operations (deposit collateral, borrow, repay, manage positions).
lifi
LI.FI REST API for cross-chain and same-chain token swaps, bridging, DeFi deposits (Composer), yield discovery (Earn), and intent-based execution (Intents). USE THIS SKILL WHEN USER WANTS TO: Swap tokens between different blockchains (e.g., "swap USDC on Ethereum to ETH on Arbitrum") Bridge tokens to another chain…
debridge
Complete deBridge Protocol SDK for building cross-chain bridges, message passing, and token transfers on Solana. Use when building cross-chain applications, bridging assets between Solana and EVM chains, or implementing trustless external calls.