Home / MCP registry index / io.github.deriveit33z-ship-it/x402-apis

DeriveAI x402 APIs

io.github.deriveit33z-ship-it/x402-apis in the official MCP registry. Endpoint https://x402-apis-eta.vercel.app/api/mcp. Source: github.com/deriveit33z-ship-it/x402-apis.

The registry describes it as: 25 pay-per-request intelligence APIs for AI agents via x402 micropayments (USDC/Base)

We read its 25 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http x402-apis https://x402-apis-eta.vercel.app/api/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "x402-apis": {
      "url": "https://x402-apis-eta.vercel.app/api/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"x402-apis","type":"http","url":"https://x402-apis-eta.vercel.app/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

arabic_sentiment arabizi_translate web_scrape text_summarize crypto_data weather_data domain_enrich scrape_structured verify_email prayer_times profanity_filter legal_simplifier gold_price detect_language currency_convert screenshot due_diligence site_audit email_audit ip_intel username_osint domain_infra brand_scout competitor_analysis company_report

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-deriveit33z-ship-it-x402-apis/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-deriveit33z-ship-it-x402-apis)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
io.github.praneeth12098/x402-factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26