Imap MCP Server vs OpenOSINT

A side-by-side look at the Imap MCP Server and OpenOSINT MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Imap MCP Server logoImap MCP ServerCommunication · Local subprocess (stdio)IMAP/SMTP MCP server to search, read, organize, send, reply & forward email for AI assistants71GreatAuth: otherOpenOSINT logoOpenOSINTCommunication · Local subprocess (stdio)AI-powered OSINT agent & MCP server. 16 tools: email, breach, IP, WHOIS, DNS, Shodan, GitHub & more.67GreatAuth: not declared

Verdict: choose Imap MCP Server for communication work as a local process; choose OpenOSINT for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Imap MCP Server logoChoose Imap MCP Server when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You want tools like imap_add_account, imap_update_account, imap_list_accounts.
Explore Imap MCP Server

OpenOSINT logoChoose OpenOSINT when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search_breach, search_whois, search_ip.
Explore OpenOSINT

Feature & specification comparison

Rows where the two servers differ are marked.

SpecImap MCP Server logoImap MCP ServerOpenOSINT logoOpenOSINT
CategoryCommunicationCommunication
Quality signal71/100 · Great67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthotherNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1111,783
Directory activity 7 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools4020

Tools & capabilities

Imap MCP Server tools 40

  • imap_add_accountAdd a new IMAP account configuration
  • imap_update_accountUpdate an existing IMAP account. Useful for fixing SMTP settings without removing and re-adding the account.
  • imap_list_accountsList all configured IMAP accounts
  • imap_remove_accountRemove an IMAP account configuration
  • imap_connectConnect to an IMAP account
  • imap_disconnectDisconnect from an IMAP account
  • imap_test_accountTest an existing account connection without re-entering credentials. Validates IMAP connectivity and returns folder count and message count.
  • imap_search_emailsNote: on some servers a 'flagged' or starred message carries a custom keyword (e.g. an Open-Xchange color label or Apple's $MailFlagBit*) instead of, or in addition to, the \Flagged system flag. After any flagged search, inspect each result's customKeywords field before concluding a message is or isn't flagged — do not rely on the flagged filter alone. Search for emails matching criteria (sender, recipient, subject, body text, date range, read/flagged status). Use this to FIND messages when you know something about them but not their UID — e.g. "emails from amazon last week", "unread invoices". By default searches a single folder (INBOX). Set searchAllFolders=true to scan every mailbox at once — this catches messages filed away by rules (e.g. a receipt routed to a custom folder); Trash/Spam/Drafts are skipped unless you opt in. By default returns lightweight headers (uid, from, subject, date, and folder when searching across folders); set `includeBody=true` to also return the parsed body in one round-trip instead of paying the N+1 cost of calling imap_get_email per match. For the newest messages without criteria, prefer imap_get_latest_emails.
  • imap_get_emailRead the FULL content of a single email by its UID (body, sender/recipients, date, attachment list, optional raw headers and text-attachment previews). By default the body is returned as clean Markdown in markdownContent and raw HTML is omitted so it never crosses the boundary; set bodyFormat to "html" for the legacy raw htmlContent, or "text" for plain text only. Use after imap_search_emails or imap_get_latest_emails gives you a uid. Body text is truncated to maxContentLength to protect the context window — raise it for long messages. To fetch attachment bytes, use imap_download_attachment.
  • imap_upload_fileUpload a file to the server for use as an email attachment. Returns a path that can be used with imap_send_email attachments. This allows sending large attachments without hitting context window limits. Max size: 26214400 bytes (configurable via IMAP_MAX_UPLOAD_SIZE). Uploads are auto-deleted after 86400000 ms (configurable via IMAP_UPLOAD_TTL_MS).
  • imap_download_attachmentDownload a single attachment from an email (folder + uid + attachment filename/contentId, as listed by imap_get_email). Images are returned inline for viewing; PDFs are saved and their text is extracted inline (extractText); other files are saved to the shared downloads directory (or savePath). Use when the user wants the actual file contents, not just the message body.
  • imap_mark_as_readMark one or many emails as read. Accepts a single UID or an array — pass an array to flag N messages in one IMAP STORE round-trip (useful when triaging).
  • +28 more on the listing page

OpenOSINT tools 20

  • search_breachCheck if an email appears in data breaches via HaveIBeenPwned. Uses HIBP_API_KEY env var. [passive] One request to haveibeenpwned.com.
  • search_whoisRetrieve WHOIS registration data for a domain. [passive] Queries the registry/registrar WHOIS server, not the target.
  • search_ipRetrieve geolocation and ASN data for an IP address via ipinfo.io. [passive] One request to ipinfo.io.
  • generate_dorksGenerate targeted Google dork URLs for any target (name, email, username, domain). [passive] Builds Google search URLs locally; sends nothing.
  • search_pasteSearch Pastebin dumps for an email or username via psbdmp.ws. [passive] One request to psbdmp.ws.
  • search_shodanQuery Shodan for host intelligence or banner search. IP address → host lookup (open ports, org, CVEs). Any other string → keyword/service search. Uses SHODAN_API_KEY env var. [passive] Shodan API; reads Shodan's existing index, requests no new scan.
  • search_virustotalCheck IP, domain, URL, or file hash against VirusTotal's 70+ antivirus engines and threat intelligence. Auto-detects input type. Uses VIRUSTOTAL_API_KEY env var. [passive] IP, domain and hash lookups read VirusTotal's existing data. URL submission is a separate active mode, off by default: it makes VirusTotal fetch the URL and makes it visible to the VirusTotal community.
  • search_censysSearch Censys for internet-facing infrastructure data. IP address → open ports, services, ASN, country. Domain → certificate history, SANs, issuer, first/last seen. Uses CENSYS_API_ID and CENSYS_SECRET env vars. [passive] Censys API; returns data Censys already holds.
  • search_ip2locationEnhanced IP intelligence using IP2Location Security Plan. Returns geolocation, ISP, ASN, and detects VPN, proxy, Tor exit nodes, and datacenter hosting. Sponsored integration. Uses IP2LOCATION_API_KEY env var. [passive] One request to api.ip2location.io.
  • search_abuseipdbCheck an IP address against the AbuseIPDB v2 API for abuse reputation. Returns abuse confidence score (0–100%), total reports, country, ISP, domain, and last reported timestamp. Shows a warning when score exceeds 50%. Uses ABUSEIPDB_API_KEY env var. [passive] One request to api.abuseipdb.com.
  • search_githubSearch GitHub for a username, email, or keyword. For exact username matches: returns full profile, recent repos, and emails discovered from commit history. For other queries: top 5 matching accounts. Optional GITHUB_TOKEN env var raises rate limit from 60 to 5000 req/h. [passive] A few requests to api.github.com.
  • search_rdapStructured domain registration lookup via RDAP (the machine-readable successor to WHOIS): registrar, registration and expiry dates, name servers and status codes. Registrant contact details are redacted by policy. No API key required. [passive] Queries IANA and the registry's RDAP server, not the target.
  • +8 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Imap MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "imap-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "imap-mcp-server"
      ]
    }
  }
}

OpenOSINT

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openosint": {
      "command": "uvx",
      "args": [
        "--from",
        "openosint",
        "openosint-mcp"
      ]
    }
  }
}

Frequently asked questions

Imap MCP Server is categorized under Communication and uses a local stdio subprocess. OpenOSINT belongs to Communication and uses a local stdio subprocess. Pick Imap MCP Server for communication work and OpenOSINT for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Imap MCP Server is listed as free. Auth: other. OpenOSINT has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add imap-mcp-server and openosint as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Imap MCP Server has a quality signal of 71/100 (Great) with 7 views, 0 installs and 111 GitHub stars. OpenOSINT has 67/100 (Great) with 1 views, 0 installs and 1,783 GitHub stars.