Skip to content
MCP Server Directory logo
finance-ecommerce

Inferventis

Live financial data MCP for FX, stocks, crypto, Open Banking, Stripe data, and financial calculations, with pay-per-call x402 micropayments.

Reviewed overview

MCP server overview

what is Inferventis? Inferventis is a production-grade MCP (Model Context Protocol) server that delivers live financial data and structured financial tools — FX, stocks, crypto, Open Banking (PSD2), Stripe payment data, and built-in financial calculations — with support for pay-per-call micropayments via the x402 standard.

how to use Inferventis?

  • Developers: subscribe for an API key and call the /mcp endpoint (JSON-RPC). Example: POST /mcp with x-api-key header. Supported integration examples include Claude Desktop config and curl examples shown on the site.
  • Autonomous agents: use the /mcp-pay endpoint with x402 micropayments. Agents submit calls with a wallet-signed on-chain payment (USDC on Base or Base Sepolia testnet). A payment interceptor library (example: x402-axios) handles 402 → pay → retry automatically. Testnet USDC is available from faucets for testing.

key features

  • Live data endpoints: FX (currency_convert), real-time stock quotes (finnhub_stock_quote), crypto prices (crypto_price via CoinGecko), Open Banking transactions (TrueLayer), and Stripe payments.
  • Financial utilities: financial_calculator for compound interest, amortisation, IRR, ROI, mortgages, etc. No external API required.
  • Semantic discovery: tool_finder uses local all-MiniLM-L6-v2 embeddings to rank tools by intent and manifest quality (scoring blends cosine similarity and manifest completeness).
  • Micropayments: x402 Payment Required flow (HTTP 402) with USDC on Base as the primary rail. Default price $0.001 USDC per call; low gas overhead and fast on-chain verification.
  • Developer-first: API key mode with Stripe metered billing for humans; registry-published for automated agent discovery (ai.inferventis/inferventis-mcp).
  • Security model: read-only server access, private keys never stored on server, Coinbase facilitator for verification.

typical use cases

  1. Autonomous agents and pipelines that need pay-per-call access to live market and banking data without human-managed accounts.
  2. Trading and portfolio apps needing real-time stock and crypto prices.
  3. Currency conversion services and FX tooling using live rates.
  4. Financial dashboards and billing/reconciliation tools integrating Stripe and Open Banking data.
  5. Testing and health checks using echo_structured to validate MCP connectivity.
  6. Tool discovery workflows: map plain-English intents to the best available tool via tool_finder.

FAQ (from the project)

  • Do I need an API key?

    Two options: yes for developer/API-key mode (use /mcp), or no for autonomous agents using x402 micropayments (use /mcp-pay).

  • How much does a call cost?

    Default is $0.001 USDC per call (plus minimal gas). Pricing and billing examples are documented; Stripe metered billing is used for API-key users.

  • Which networks are supported for x402 payments?

    Primary: Base mainnet (eip155:8453). Testnet: Base Sepolia (eip155:84532). Polygon support planned.

  • How fast are payments/verification?

    Payment + verification on Base is near-instant (around ~1 second typical) using on-chain proof and facilitator verification.

  • Is my private key exposed to the server?

    No. Private keys remain with the agent/wallet; the server performs read-only verification of on-chain receipts.

  • How does semantic tool discovery work?

    tool_finder embeds your plain-English intent locally with MiniLM, scores tools by cosine similarity (80%) and manifest quality (20%), and returns a ranked list.

  • How can I test integration?

    Use the provided curl example or the Node x402-axios sample. For agent testing use testnet USDC from faucets. The server also exposes an echo_structured tool to validate connectivity.