Erudite Intelligence x402 Services
io.github.EruditeIntelligencePublished by GitHub account EruditeIntelligencev1.0.0Updated Oct 24, 2026
80 paid MCP tools via x402 USDC micropayments. Crypto data, web scraping, auditing, and more.
The publisher's own server: EruditePay Blockchain Intelligence
Overview
A remote MCP endpoint offering 80 paid tools for crypto data, web scraping, and auditing, billed per use via x402 USDC micropayments.
- What you can do
- This server exposes a catalog of 80 tools that an assistant can call, covering crypto data, web scraping, and auditing according to the provider's description. Each tool is paid: calls are settled through x402 USDC micropayments rather than a subscription. It runs as a remote streamable HTTP endpoint, so no local package is installed.
- When to use it
- Worth considering when an assistant needs occasional crypto data, scraping, or auditing capabilities and you are willing to pay per call in USDC. Less suitable if you need free, unlimited, or offline tooling, or if you cannot manage a crypto wallet for micropayments.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the provider's endpoint. Network access is required. The manifest declares no authentication, environment variables, or headers, but per-call x402 USDC micropayments imply a funded wallet or payment setup on the client side.
Installation
In SourceWeft
- Open Erudite Intelligence x402 Services in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.EruditeIntelligence%2Fx402-services/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"erudite-intelligence-x402-services": {
"type": "http",
"url": "https://mcp.eruditepay.com/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.