apiverve/mcp repository overview

⁠APIVerve MCP Server

Give your AI agent 350+ real-world APIs — weather, geocoding, finance, DNS, validation, text, AI, images, and more — over the Model Context Protocol.

This is the official APIVerve⁠ MCP⁠ server for any stdio-based MCP client — Claude Desktop, Claude Code, Cursor, Windsurf, and others. It's a lightweight bridge: it speaks stdio to your client and forwards to APIVerve's hosted MCP endpoint, so every API stays current server-side with nothing to update locally.

⁠What your agent can do

Once connected, your assistant can call any APIVerve API as a tool — for example:

• "Is [email protected] a valid, non-disposable email?" → emailvalidator
• "What's the 5-day forecast for San Francisco?" → weatherforecast
• "Convert 250 USD to EUR at today's rate." → currencyconverter
• "Look up the WHOIS and SSL status for example.com." → whoislookup, sslchecker
• "Summarize and run sentiment on this review." → textsummarizer, sentimentanalysis

350+ tools across weather, finance, networking/DNS, validation, geolocation, text & language, AI/vision, and utilities.

⁠Setup — Claude Desktop

Add this to claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "apiverve": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "APIVERVE_API_KEY", "apiverve/mcp"],
      "env": {
        "APIVERVE_API_KEY": "your_key"
      }
    }
  }
}

Restart Claude Desktop; the APIVerve tools appear in the tools menu.

⁠Setup — Cursor / Windsurf / other MCP clients

The same server block works in any client that supports stdio MCP servers (Cursor: ~/.cursor/mcp.json; Windsurf: mcp_config.json):

{
  "mcpServers": {
    "apiverve": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "APIVERVE_API_KEY", "apiverve/mcp"],
      "env": { "APIVERVE_API_KEY": "your_key" }
    }
  }
}

⁠Setup — Claude Code

claude mcp add apiverve -e APIVERVE_API_KEY=your_key -- docker run -i --rm -e APIVERVE_API_KEY apiverve/mcp

⁠Authentication

Get a free API key (no card) at apiverve.com⁠ and pass it as APIVERVE_API_KEY. Without a key, the bridge falls back to an interactive OAuth flow.

⁠Try it standalone

docker run -i --rm -e APIVERVE_API_KEY=your_key apiverve/mcp

It speaks the MCP protocol over stdio, so it's normally launched by a client rather than used directly.

⁠Troubleshooting

• Tools don't appear: fully quit and reopen the client after editing the config (a reload isn't always enough).
• Auth errors: confirm APIVERVE_API_KEY is set in the env block and the key is active at apiverve.com⁠.
• docker: command not found: the client must be able to see Docker on its PATH (install/start Docker Desktop).

⁠Supported tags

• apiverve/mcp:latest — newest release
• apiverve/mcp:1.1.0 — pinned version

Architectures: linux/amd64, linux/arm64.

⁠Prefer a hosted connection?

No Docker required — APIVerve's MCP endpoint is also reachable directly at https://api.apiverve.com/v1/mcp for clients that support remote (streamable-HTTP) MCP servers.

⁠Links

• 🌐 Website & free API key: https://apiverve.com?utm_source=dockerhub&utm_medium=readme&utm_campaign=mcp_image⁠
• 📚 Documentation: https://docs.apiverve.com?utm_source=dockerhub&utm_medium=readme&utm_campaign=mcp_image⁠
• 🧩 Model Context Protocol: https://modelcontextprotocol.io⁠
• 💻 Source: https://github.com/apiverve/mcp-server⁠

Made by APIVerve⁠ — 350+ APIs, one key, one bill.