Mcp Server
380+ live data, validation and utility APIs in one MCP server: IP, DNS, email, FX, weather and more.
387+ APIs accessible through the Model Context Protocol
Website • Documentation • API Explorer • Report Bug
🚀 Overview
The APIVerve MCP Server provides seamless access to 387+ production-ready APIs through the Model Context Protocol. Connect AI assistants like Claude, ChatGPT, and other MCP-compatible clients to a vast ecosystem of data and functionality.
✨ Features
- 🎯 387+ APIs - Weather, news, geocoding, validation, conversion, and more
- 🔐 OAuth 2.0 Authentication - Secure, industry-standard authentication
- 📊 Token-Based Pricing - Pay only for what you use
- 🚀 High Performance - Cloud-hosted with 99%+ uptime
- 📖 Rich Documentation - Complete API documentation with examples
- 🔄 Auto-Updated - Always access the latest API features
📦 Installation
APIVerve is a remote MCP server — there is nothing to run locally. Point your client at the URL below and it will handle sign-in for you.
One-click install
This repo is also a Cursor plugin (.cursor-plugin/) and a Gemini CLI extension (gemini-extension.json): each adds the server plus a skill that tells the agent when and how to use the tools.
Gemini CLI:
gemini extensions install https://github.com/apiverve/mcp-server
Quick setup
npx @apiverve/mcp-server
Configures VS Code and Cursor, and prints the manual step for Claude Desktop. Target one client with npx @apiverve/mcp-server cursor.
For headless setups, pass a key instead of using sign-in:
npx @apiverve/mcp-server --api-key YOUR_API_KEY
Python users can do the same with pip install apiverve-mcp then apiverve-mcp (or apiverve-mcp --api-key YOUR_API_KEY).
Manual setup
Claude Desktop — remote servers are added through the app, not a config file:
Settings → Connectors → Add custom connector →
https://api.apiverve.com/v1/mcp
VS Code (mcp.json):
{
"servers": {
"apiverve": {
"type": "http",
"url": "https://api.apiverve.com/v1/mcp"
}
}
}
Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"apiverve": {
"url": "https://api.apiverve.com/v1/mcp"
}
}
}
🔑 Authentication
Two ways in — pick whichever fits:
OAuth (default, recommended) — leave the config as shown above. On first use the server returns an authorization challenge and your client walks you through sign-in. No key is stored on disk, and access can be revoked from the dashboard.
API key — add your key as a header. Useful for CI and headless environments where no browser is available:
{
"mcpServers": {
"apiverve": {
"url": "https://api.apiverve.com/v1/mcp",
"headers": { "x-api-key": "YOUR_API_KEY" }
}
}
}
Claude Desktop's Custom Connectors cannot send custom headers, so it is OAuth-only.
From the project's README.