Remote MCP Server - Introduction

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:

• 8 Professional Tools for email discovery and verification
• 5 Resource Types for comprehensive data access
• 7 Pre-built Workflows 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
 
https://mcp.tomba.io/mcp

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

Authentication Methods

The Tomba MCP Server supports two authentication methods for HTTP requests:

1. Authorization Header (Recommended)
2. Separate Headers (Legacy)

Method 1: Authorization Header (Recommended)

Use the standard Authorization header with a Bearer token format:

Code
 
Authorization: Bearer <api-key>+<secret-key>

Example:

Code
 
curl -X POST https://mcp.tomba.io/mcp \
  -H "Authorization: Bearer ta_1234567890abcdef+ts_abcdef1234567890" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Method 2: Separate Headers (Legacy)

Use separate x-tomba-key and x-tomba-secret headers:

Code
 
x-tomba-key: <api-key>
x-tomba-secret: <secret-key>

Example:

Code
 
curl -X POST https://mcp.tomba.io/mcp \
  -H "x-tomba-key: ta_1234567890abcdef" \
  -H "x-tomba-secret: ts_abcdef1234567890" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'