Skavio Agent Tools
New verified integration: Safe x402 buyer example — Node.js + Python. Free live HTTP 402 preview with no signup or wallet, plus opt-in Base USDC paid adapter with a per-call limit. No funded purchase is made by default. No-account visual examples.
[Skavio USDC Paid Micro-APIs MCP server — mcprush tool-list rating]
Official connection metadata and documentation for Skavio LLC's hosted MCP tools and x402 HTTP API. This repository contains discovery metadata, not the production server source.
Card-funded Agent Tools processing (no crypto wallet)
For authenticated Agent Tools document, OCR, invoice and audio processing, an administrator signs in to the Agent Tools Dashboard, selects Buy credits by card, chooses $5, $10, $20, $50, $100, $200 or $500, and completes a Stripe-hosted checkout. Verified settlement funds that same bound company wallet at 1 USD = 1,000 credits. Eligible jobs can then use the company's Agent Tools key with payment_mode=prepaid. USDC top-ups remain available.
Do not mix payment rails: the separate company Agent Tools MCP endpoint is https://getskavio.com/agent-tools/mcp, and OAuth Processing MCP is https://getskavio.com/processing/mcp. The four independently priced blockchain verification/DNS tools on https://getskavio.com/mcp and the paid HTTP x402 routes still require native USDC via x402. Card credits do not authorize those four calls, and neither MCP credential can initiate card charges.
Verification as of November 7, 2026: card checkout interface and private company binding deployed, isolated security and transactional ledger tests passed, and a Stripe TEST-mode unpaid $5 checkout was created and expired. A real paid external card-to-MCP completed job E2E has not yet been verified. Agent Tools docs · Prices.
Partner review / data-handling facts: public USDC MCP integration facts. Maintainer: Skavio LLC; email: [email protected]. GitHub contains metadata and documentation, not production source. Live runtime reports 1.30.0; registry descriptor 1.1.5 is independently versioned.
New practical guide: Verify an incoming USDC transfer from an AI agent using x402 — live 0.02/0.03/0.05 USDC operation prices, free HTTP 402 discovery and payment-safe steps. Try the hosted endpoint.
LIVE — DeepSeek-only x402 HTTP Web APIs: Seven-route discovery · OpenAPI. These four paid HTTP endpoints are separate from tenant-authenticated MCP Agent Tools:
All four use DeepSeek Search, Fetch or Flash with no alternate provider. An unsigned call returns an x402-v2 HTTP 402 quote; compatible clients sign and retry with PAYMENT-SIGNATURE. One real 0.01 USDC Web Fetch purchase on 28 October 2026 settled and delivered the requested result. Do not assume the other three have independent funded checkout results. Keys and signing remain in the buyer's wallet.
Separate authenticated company Agent Tools: Legacy enterprise API integration notes. Those older web operations and their provider migration are not part of this new DeepSeek-only paid HTTP release.
Use Skavio in Cursor and Claude Desktop
Connection instructions and ready-to-copy Cursor / Claude Desktop JSON · Cursor config · Claude Desktop config. The publicly discoverable MCP server is https://getskavio.com/mcp; separate OAuth-protected Processing MCP is at https://getskavio.com/processing/mcp. Plain MCP clients do not automatically process x402 payments.
Connect an MCP client using Streamable HTTP at https://getskavio.com/mcp. Discovery and the skavio_catalog tool are free. Paid invocations use x402 MCP v2: inspect PaymentRequired, then retry with an authorization supplied by your wallet client in params._meta["x402/payment"]. Keep wallet keys in your own client. Paid MCP invocations accept native Circle USDC via x402 v2 on Base (eip155:8453) or Solana (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp). The standalone HTTP Verify, Match and Evidence PDF routes accept Base USDC only. Obtain current payment requirements from the service.
Transfer inspection supports Base, Polygon, Arbitrum, Optimism, Ethereum, Avalanche and Solana. MCP x402 payment supports Base and Solana; the standalone HTTP x402 routes remain Base-only. Evidence PDFs are not tax invoices.
HTTP documentation: https://getskavio.com/x402/docs
The three established Base USDC verification routes remain public: /x402/v1/usdc/verify, /x402/v1/usdc/match, and /x402/v1/usdc/evidence.pdf. Four additional paid DeepSeek web POST routes are listed above; all seven are indexed in the canonical discovery document.
Public unsigned challenge and discovery checks do not establish successful funded settlement or profitability. No revenue claim is made. The current public tools/list also advertises tenant-authenticated document, OCR, invoice, audio and web Agent Tools. These require a valid Agent Tools credential and cannot be used anonymously. The separate OAuth-protected Processing API and its developer kit are at https://github.com/skavio-eu/skavio-processing-api.
Published in the official MCP Registry as eu.skavio/paid-micro-apis, version 1.1.5: https://registry.modelcontextprotocol.io/v0.1/servers/eu.skavio%2Fpaid-micro-apis/versions/1.1.5. Other directory registrations are tracked separately. Prices and capabilities may change; inspect current server responses before authorizing payment.
USDC payment verification for AI agents
Skavio USDC Payment Verification — x402 API inspects native Circle USDC transfers, matches an exact recipient and decimal amount, and generates blockchain evidence PDFs. Use it for merchant payment reconciliation, accountant transaction review and agent workflows. PDF evidence is not a tax invoice or a guarantee of third-party authorization.
- HTTP Verify: 0.02 native USDC; Match: 0.03 USDC; PDF: 0.05 USDC. Payment settles separately on Base through x402 v2. Inspection supports Base, Polygon, Arbitrum, Optimism, Ethereum, Avalanche and finalized Solana.
- API quickstart, schemas, errors and client configurations · seven-route discovery · OpenAPI.
- Skavio USDC Payment Verification & Proof MCP, version 1.1.5. Stable registry namespace and tool IDs are unchanged. Connect using
https://getskavio.com/mcp (Streamable HTTP).
- MCP has four paid blockchain/domain tools (
verify_native_usdc, match_native_usdc_payment, usdc_transfer_evidence_pdf, domain_dns_tls_audit), two free discovery tools, and twelve separate authenticated AgentTools processing/job/wallet relays. The DNS/TLS audit is 0.05 USDC and is not a vulnerability scan.
- A standard MCP client without a wallet x402 extension cannot automatically pay. Discovery is free. Paid MCP retries preserve
params._meta["x402/payment"]; HTTP retries use PAYMENT-SIGNATURE. Never send a private key or seed phrase. No custody or automatic spending is created by adding a server.
- PayAPI publishes separate live listings and historical settlement receipts for HTTP Verify, 0.02 USDC, exact recipient/amount Match, 0.03 USDC, and blockchain PDF evidence, 0.05 USDC. Each route was independently read back on 2026-10-17, and each prior Base USDC receipt was checked read-only. No new payment was made for this documentation update. This is blockchain evidence, not a tax invoice.
- RPC availability and finality affect results. No fixed latency SLA is promised. EVM requests use a 32-byte 0x hash; Solana uses its transaction signature. Match takes a recipient wallet and a positive exact USDC decimal string with at most six decimal places.
Cursor .cursor/mcp.json:
Claude Code:
Claude Desktop with Node.js and a reviewed stdio-to-HTTP bridge:
The bridge may download a third-party package and does not supply wallet payment support. Current Desktop remote connectors may accept the HTTPS URL directly.
First unpaid request (no signing or transfer):
Expect HTTP 402 and decode PAYMENT-REQUIRED. Inspect the exact amount, Base USDC asset and recipient before authorizing an x402 wallet client; only then retry the same request. After an ambiguous response, inspect recovery state instead of blindly paying again.
Separate Skavio PDF, OCR & Document Processing MCP, version 0.2.8, uses company OAuth at https://getskavio.com/processing/mcp and shared prepaid credits. Processing docs explain company ownership and measured jobs. Optional AgentTools relays require the caller's own key and current backend availability; preserve the idempotency key, poll status, download results and verify SHA256. HTTP /x402/v1/processing stays disabled.