Api Quant M2m

Name: Api Quant M2m
Author: Quant-M2M

by Quant-M2Mcommunityv2.0.0

Serveur MCP distant accessible via SSE qui donne à un agent IA deux outils en temps réel : extraction de texte d’une page web et consultation du prix USD d’une cryptomonnaie. L’accès est autorisé par une adresse wallet et un paiement USDC on-chain sur Base.

From the registry: Web scraping and crypto price oracle MCP. Pay 1 USDC on Base for 1h access.

GitHub Repository

Install & configure

Prerequisites

required
Pay for access on Base with USDC
This server requires prepaid on-chain access. Approve 1 USDC (or more) to the ApiAccessVault contract, then call pay(amount). 1 USDC grants 1 hour of access; payments are cumulative.
required
Have a wallet address with active access credit
Requests must include an X-Wallet-Address header for a wallet that has an active paid credit window; otherwise the server returns 401.
required
Install Node.js to use the recommended mcp-remote bridge
The recommended connection method uses npx to run mcp-remote locally, which bridges the remote SSE MCP server into stdio for MCP clients that expect a local command.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `api-quant-m2m` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Pay for access on Base with USDC** — This server requires prepaid on-chain access. Approve 1 USDC (or more) to the ApiAccessVault contract, then call pay(amount). 1 USDC grants 1 hour of access; payments are cumulative.
- **Have a wallet address with active access credit** — Requests must include an X-Wallet-Address header for a wallet that has an active paid credit window; otherwise the server returns 401.
- **Install Node.js to use the recommended mcp-remote bridge** — The recommended connection method uses npx to run mcp-remote locally, which bridges the remote SSE MCP server into stdio for MCP clients that expect a local command.

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["mcp-remote","https://quant-m2m.xyz/sse","--header","X-Wallet-Address:<your-wallet-address>"]

Note: Remote MCP server exposed over SSE at https://quant-m2m.xyz/sse with tool calls routed to https://quant-m2m.xyz/messages. Authentication is via the required HTTP header X-Wallet-Address. README also shows a custom Python bridge alternative, but the portable recommended path is npx mcp-remote.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: Remote MCP server exposed over SSE at https://quant-m2m.xyz/sse with tool calls routed to https://quant-m2m.xyz/messages. Authentication is via the required HTTP header X-Wallet-Address. README also shows a custom Python bridge alternative, but the portable recommended path is npx mcp-remote.