What APIVerve MCP server does
The APIVerve MCP server connects MCP clients to APIVerve’s catalog of more than 368 APIs through a single remote endpoint. The catalog covers weather and environmental data, location and geocoding, validation and verification, conversions and calculations, news and content, random data generation, and financial data. The repository specifically demonstrates the emailvalidator tool, while the service describes the wider catalog as available through MCP.
This setup is useful when an agent needs to call external API functions without maintaining separate MCP servers for each provider. Example tasks include validating an email address, checking weather, converting currencies, looking up a timezone, or retrieving other supported API results.
How it works
The APIVerve MCP server uses streamable HTTP at https://api.apiverve.com/v1/mcp. A compatible client initializes a session, discovers the available tools, and calls a selected tool with JSON input. Each API is represented by a tool with an identifier, a description that includes token cost information, and a JSON Schema describing required and optional parameters.
The service supports MCP protocol version 2025-06-18 and can negotiate down to versions 2025-03-26 and 2024-11-05. The server is cloud-hosted, so the standard connection does not require a local process. A command-line helper can configure Cursor and VS Code, and Python clients can connect directly with the MCP SDK and streamable HTTP transport.
Setup and configuration
For interactive use, configure the remote URL in the MCP client. Claude Desktop adds it through Settings, Connectors, and Add custom connector. VS Code uses an HTTP server entry in mcp.json, while Cursor uses a remote server entry in ~/.cursor/mcp.json.
OAuth 2.0 with PKCE is the default authentication path. The client receives an authorization challenge and guides the user through sign-in. For CI, headless processes, or other environments without a browser, provide an APIVerve API key using the x-api-key header. The command-line setup supports both Node.js and Python installation paths and accepts an API key argument.
Claude Desktop custom connectors cannot send custom headers, so that configuration uses OAuth rather than API-key authentication. API keys are available from the APIVerve website, which also provides a free tier.
Tools and capabilities
The APIVerve MCP server presents APIs as callable MCP tools. Supported catalog areas include:
- Weather, air quality, marine weather, and UV information
- Reverse geocoding, IP lookup, timezone lookup, airport lookup, and distance calculation
- Email and phone validation, domain availability, and SSL certificate checks
- Currency, unit, date, and BMI calculations
- News, RSS conversion, web scraping, and metadata extraction
- Random users, passwords, and Lorem Ipsum text
emailvalidator is the documented example tool. A client can call it with an email value after discovering the tool schema. Token costs vary by API, with simple calls starting at one credit according to the provided pricing information.
Limitations and notes
Usage is governed by APIVerve’s token-based pricing. A free tier is available, while pay-as-you-go and enterprise plans are also offered. The number of credits consumed depends on the selected API and its complexity.
Authentication or connection problems may require checking the API key, correcting the OAuth redirect URI, or authorizing the connection again. Usage and token limits can be reviewed in the APIVerve dashboard. The repository does not describe individual input schemas for every catalog API, so developers should consult the API documentation or marketplace before relying on a specific operation.