Skavio USDC Paid Micro APIs

What Skavio USDC Paid Micro-APIs MCP server does

Skavio USDC Paid Micro-APIs MCP server connects an MCP client to Skavio LLC’s hosted tools through the Streamable HTTP endpoint at https://www.skavio.eu/mcp. The repository contains connection metadata and documentation rather than the production implementation.

The free skavio_catalog tool reports the available capabilities. Paid tools inspect native USDC transfer evidence, compare a payment with a recipient and exact amount, create a bounded blockchain evidence PDF, and audit public-domain DNS and TLS configuration. The evidence PDF is not a tax invoice.

Transfer inspection supports Base, Polygon, Arbitrum, Optimism, Ethereum, Avalanche, and Solana. The service’s own payment settlement remains on Base using native Circle USDC.

How it works

Connect an MCP-compatible client to the hosted Streamable HTTP endpoint, then use skavio_catalog to discover the current tool set. Paid calls use x402 MCP v2. If the service returns PaymentRequired, the client must obtain authorization from its wallet and retry with that authorization in params._meta["x402/payment"].

The advertised prices are 0.02 USDC for verify_native_usdc, 0.03 USDC for match_native_usdc_payment, and 0.05 USDC each for usdc_transfer_evidence_pdf and domain_dns_tls_audit. Prices and capabilities can change, so inspect current service responses before approving payment.

Wallet keys should remain in the MCP client. The related HTTP API advertises /x402/v1/usdc/verify, /x402/v1/usdc/match, and /x402/v1/usdc/evidence.pdf; callers should use the documented query parameters with an x402-compatible client.

Tools and capabilities

• skavio_catalog: Free discovery of available capabilities.
• verify_native_usdc: Inspects native USDC transfer evidence across the supported chains.
• match_native_usdc_payment: Checks whether a transfer matches the intended recipient and exact amount.
• usdc_transfer_evidence_pdf: Returns bounded blockchain evidence as a PDF.
• domain_dns_tls_audit: Performs a bounded DNS and TLS audit for a public domain.

Skavio USDC Paid Micro-APIs MCP server is suited to workflows that need transaction verification, payment matching, downloadable transfer evidence, or a basic public-domain configuration audit. It does not provide the separate Processing API’s PDF, OCR, invoice, or audio capabilities; that integration is described as under development and is not part of this MCP catalog.

Limitations and notes

Discovery and unsigned public challenges do not prove that a funded payment settled successfully, and the service makes no profitability or revenue claim. The hosted service may revise prices and capabilities. Check live responses before authorizing an invocation.

The repository does not include the production server source. It also does not document client-specific setup, environment variables, or a software license. Use a client that supports Streamable HTTP, MCP, and the required x402 wallet authorization flow.