Does it require API keys?

No API keys are needed; it uses the streamable-http transport.

Can it prevent payments?

It only provides intelligence; the agent or user still decides whether to pay.

Is it local or remote?

It is a remote server accessed over streamable-http.

counterparty-intelligence

Identify x402 payment counterparties as service, relayer, treasury or buyer.

MCP ServerAI & KnowledgeRemote (streamable-http)

View source

Updated 2026-06-22

What is the counterparty-intelligence MCP server?

This MCP server provides counterparty classification for x402 micropayments. Agents query it to determine whether the destination address represents an actual service provider, a payment relayer, a treasury wallet, or an end buyer.

By returning structured intelligence before payment execution, it reduces misdirected funds and improves transparency in agent-driven commerce flows.

Install & connect

Add this to your MCP client config. Pick your client below and copy.

{
  "mcpServers": {
    "counterparty-intelligence": {
      "url": "https://data.crestsystems.ai/mcp"
    }
  }
}

Example prompts

Once connected, try asking your AI client:

“Check the counterparty for this x402 destination address before I pay

“Is 0xabc... a real service or a relayer?

“Classify the recipient of this upcoming payment

“Tell me if this address is a treasury wallet

Security & permissions

Requires remote streamable-http access; no local filesystem or API keys are needed beyond the MCP connection itself.

What you can do with counterparty-intelligence

Pre-payment verification

Confirm the intended recipient type before an agent authorizes an x402 payment.

Treasury monitoring

Detect when funds are routed to internal treasury addresses rather than external vendors.

Relayer detection

Flag payments that would pass through intermediaries instead of reaching the final service.

How to use counterparty-intelligence

1Add the server URL to your MCP client configuration.
2Connect using streamable-http transport.
3Send a counterparty address or payment context in your prompt.
4Review the returned classification before authorizing payment.
5Log results for audit or compliance purposes.