diegosilva-05/agentic-payment-mcp
MCP server for agentic payment validation — KYA identity verification, deterministic fraud scoring, and capture pre-flight for agentic commerce platforms
Platform-specific configuration:
{
"mcpServers": {
"agentic-payment-mcp": {
"command": "npx",
"args": [
"-y",
"agentic-payment-mcp"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
> Prototype — Python 3.11 · MCP SDK · Pydantic v2 · pytest-asyncio
As payments evolve from transactional services into intelligent agentic experiences, agentic commerce platforms face a structural gap: shopping agents (LLMs orchestrating purchase flows) need to initiate payment operations, but acquiring infrastructure was designed for human-driven, session-authenticated requests, not autonomous AI clients with delegated authority. This MCP server implements the validation layer that bridges that gap — enforcing Know-Your-Agent (KYA) identity binding, deterministic fraud signal scoring, and capture pre-flight governance before any payment request reaches the SEP (Single Entry Point). It ensures that AI-initiated payment operations satisfy the same identity, risk, and regulatory requirements as human-initiated ones, without adding a dependency on LLM inference to the authorization critical path.
---
┌─────────────────────────────────────────────────────────────────────────────┐
│ AGENTIC COMMERCE FLOW │
│ │
│ ┌────────────────┐ MCP Protocol ┌─────────────────────────────┐ │
│ │ Shopping Agent │ ◄──────────────────► │ MCP Server │ │
│ │ (LLM client) │ stdio / HTTP+SSE │ (this project) │ │
│ └────────────────┘ │ │ │
│ │ │ 1. validate_agent │ │
│ │ Orchestrate tool calls │ KYA gate (15 ms) │ │
│ │ Select next step based │ │ │
│ │ on tool output │ 2. check_fraud_signals │ │
│ │ │ Risk scoring (25 ms) │ │
│ │ Loading reviews...