Telegram MCP vs OpenOSINT
A side-by-side look at the Telegram MCP and OpenOSINT MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Telegram MCP 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?
Choose Telegram MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
GROQ_API_KEY, TELEGRAM_ALIASES_FILE, TELEGRAM_CONTACT_FUZZY, TELEGRAM_TRANSCRIBE_GROQ_MAX_MB.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 59/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | GROQ_API_KEYTELEGRAM_ALIASES_FILETELEGRAM_CONTACT_FUZZYTELEGRAM_TRANSCRIBE_GROQ_MAX_MB | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,866 | 1,783 |
| Directory activity | 7 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 20 |
| Full listing | View Telegram MCP | View OpenOSINT |
Tools & capabilities
Telegram MCP tools
No tool names declared yet. Check the project README from 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.
Telegram MCP
{
"mcpServers": {
"chigwell-telegram-mcp": {
"command": "uvx",
"args": [
"telegram-mcp"
],
"env": {
"GROQ_API_KEY": "YOUR_GROQ_API_KEY_HERE",
"TELEGRAM_ALIASES_FILE": "YOUR_TELEGRAM_ALIASES_FILE_HERE",
"TELEGRAM_CONTACT_FUZZY": "YOUR_TELEGRAM_CONTACT_FUZZY_HERE",
"TELEGRAM_TRANSCRIBE_GROQ_MAX_MB": "YOUR_TELEGRAM_TRANSCRIBE_GROQ_MAX_MB_HERE"
}
}
}
}
OpenOSINT
{
"mcpServers": {
"openosint": {
"command": "uvx",
"args": [
"--from",
"openosint",
"openosint-mcp"
]
}
}
}
Frequently asked questions
Telegram MCP is categorized under Communication and uses a local stdio subprocess. OpenOSINT belongs to Communication and uses a local stdio subprocess. Pick Telegram MCP 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.
Telegram MCP 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 chigwell-telegram-mcp and openosint as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Telegram MCP has a quality signal of 59/100 (Good) with 7 views, 0 installs and 1,866 GitHub stars. OpenOSINT has 67/100 (Great) with 1 views, 0 installs and 1,783 GitHub stars.