usdc_x402_payments_intel

Real-time analytics on x402 protocol USDC micropayments for MCP endpoints on Base network. Unique competitive advantage: aggregates internal production telemetry (our own traffic data) with on-chain USDC Transfer events and Bazaar marketplace listings — data no external competitor can access. Fou...

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io
Critical RISK CLASS
Category Financial
Parameters 61 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/usdc-x402-payments-intel.md

What usdc_x402_payments_intel does on Mcp Knowledge

AI agents use usdc_x402_payments_intel to commit financial operations through Mcp Knowledge, usually the final step of a payment, billing, or trading workflow. A call moves real money.

ParameterTypeRequiredDescription
mode string Yes Analytics mode: facilitator_stats=network-wide settlements | endpoint_intel=per-URL analytics | agent_caller_profile=per-wallet analytics | price_radar=price di
async boolean If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
category string Tool category for price_radar mode. Defaults to all.
period_days number Lookback window in days (5-90, default 30)
endpoint_url string MCP endpoint URL for endpoint_intel mode (e.g. https://mcp.gapup.io/mcp)
wallet_address string EVM wallet address for agent_caller_profile mode (0x...)

Parameters from the server's own tool schema.

Why usdc_x402_payments_intel is rated Critical

This tool directly interfaces with USDC payment flows on the Base blockchain network, aggregating financial transaction data including settlement statistics, payment volumes, and on-chain transfer events. Even if primarily analytical, it connects to live financial infrastructure (Coinbase CDP API, Base mainnet RPC) involving real USDC transfers.

From the tool's definition Real-time analytics on x402 protocol USDC micropayments... facilitator_stats — Coinbase x402 facilitator settlement statistics (volume, count, top payees/payers)... on-chain USDC Transfer events... Coinbase CDP API

Questions about usdc_x402_payments_intel

What does the usdc_x402_payments_intel tool do? +

Real-time analytics on x402 protocol USDC micropayments for MCP endpoints on Base network. Unique competitive advantage: aggregates internal production telemetry (our own traffic data) with on-chain USDC Transfer events and Bazaar marketplace listings — data no external competitor can access. Four modes: (1) facilitator_stats — Coinbase x402 facilitator settlement statistics (volume, count, top payees/payers). Uses Coinbase CDP API if COINBASE_X402_API_KEY is set; falls back to Base mainnet RPC scan of USDC transfers to known facilitator addresses. (2) endpoint_intel — Per-MCP-endpoint analytics: tx count, USDC volume, unique callers, success rate, catalog size. For gapup-mcp.io endpoints: reads internal JSONL telemetry (richest data source, unique). (3) agent_caller_profile — Anonymous profile of a calling agent wallet: tx count, USDC spent, top endpoints, inferred persona (depth-seeker / bulk-scanner / generalist / researcher / explorer). Wallet anonymised via SHA-256. (4) price_radar — USDC price distribution by tool category (data_lookup / synthesis / compliance / competitive) from Bazaar + internal catalog. Returns median, P25, P75. Network: Base mainnet. USDC contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Cache: 30 min LRU. Timeout per source: 8s. Optional env: COINBASE_X402_API_KEY (higher-fidelity facilitator stats). It is categorised as a Financial tool in the Mcp Knowledge MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does usdc_x402_payments_intel accept? +

usdc_x402_payments_intel accepts 6 parameters: mode, async, category, period_days, endpoint_url, wallet_address. Required: mode. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on usdc_x402_payments_intel? +

Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for usdc_x402_payments_intel: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Knowledge. Nothing to install.

What risk level is usdc_x402_payments_intel? +

usdc_x402_payments_intel is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit usdc_x402_payments_intel? +

Yes. Add a rate_limit block to the usdc_x402_payments_intel rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block usdc_x402_payments_intel completely? +

Set action: deny in the PolicyLayer policy for usdc_x402_payments_intel. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides usdc_x402_payments_intel? +

usdc_x402_payments_intel is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mcp Knowledge, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Knowledge's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.