Welcome to the Remote MCP Server powered by Tomba.io, a comprehensive Model Context Protocol (MCP) server that provides advanced email discovery, verification, and enrichment capabilities through a streamlined HTTP transport interface.
What is Remote MCP Server?
The Remote MCP Server is a cloud-hosted implementation of the Model Context Protocol that allows you to access Tomba.io's powerful email intelligence tools without the need for local installation or configuration. By leveraging our remote infrastructure, you get instant access to:
- 12 Professional Tools for email discovery and verification
- 3 Resources for comprehensive data access
- 12 Pre-built Prompts for common use cases
- Real-time Processing with high availability
- Scalable Infrastructure that grows with your needs
Key Advantages of Remote MCP
Instant Setup
No installation, no dependencies, no configuration files. Just connect and start using professional email intelligence tools immediately.
Always Up-to-Date
Our remote server is continuously updated with the latest features, bug fixes, and API improvements without any action required on your part.
Streamable HTTP Transport
The Remote MCP Server uses Streamable HTTP Transport for real-time, bidirectional communication. This modern approach provides:
- Server-Sent Events (SSE) for real-time notifications
- JSON-RPC 2.0 for structured API communication
- Session Management for stateful interactions
- WebSocket-like Experience over standard HTTP
Connection Endpoint
Code
This single endpoint handles all MCP operations through different HTTP methods:
- POST - Send JSON-RPC requests
- GET - Receive real-time notifications via SSE
- DELETE - Terminate sessions cleanly
Agent Skills
Install the Tomba MCP skill to help AI assistants effectively use the Tomba tools:
Code
The skill provides:
- Domain knowledge for email discovery and verification
- Best practices for lead generation workflows
- Authentication setup guidance
- Tool usage examples and patterns
View the skill catalog: https://mcp.tomba.io/.well-known/skills/index.json
Authentication Methods
Getting API Keys
- Sign up at app.tomba.io
- Navigate to Settings → API Keys
- Copy your API Key (starts with
ta_) and Secret Key (starts withts_)
The Tomba MCP Server supports two authentication methods for HTTP requests:
- Bearer Token (Recommended)
- Custom Headers (Legacy)
Method 1: Bearer Token (Recommended)
Encode your credentials as base64:
Code
Use in the Authorization header:
Code
Example:
Code
Method 2: Custom Headers (Legacy)
Send credentials as separate headers:
Code
Example:
Code
Rate Limits & Quotas
- Rate limits depend on your subscription plan
- Check remaining credits via the
tomba://usageresource - Free tier includes limited monthly searches and verifications