Skip to main content
Glama
Sign In
osint-mcp-server

osint-mcp-server

by robyroro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to osint-mcp-server

  • romania-mcp

    robyroro
    A
    license
    A
    quality
    B
    maintenance
    Romanian public data with no API keys: ANAF company status by CUI (VAT, fiscally inactive, deregistered), filed financial statements, Portal Just court cases and BNR exchange rates. Includes shop_check, which flags whether an online shop looks like a scam.
    6
    28 PyPI
    MIT

Related Servers

  • io.github.blisspixel/recon

    pueo-labs
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables agents to map a domain's public technology and identity footprint — email providers and controls, identity indicators, SaaS, and cloud infrastructure — as evidence-backed, machine-readable observations marked passive by default, where missing evidence reads as "not observed" rather than "not used". Runs locally with one-domain lookups, multi-domain comparisons, and explicit collection failures.
    728 PyPI
    5
    Apache 2.0

  • OpenOSINT

    kush-coder
    A
    license
    A
    quality
    C
    maintenance
    Enables MCP-compatible AI clients to run passive OSINT investigation tools for domains, IPs, emails, usernames, breaches, DNS, WHOIS, and reputation checks through natural-language tool calls. It exposes 16 passive tools by default, plus graph and batch helpers, with additional active tools available when explicitly enabled.
    20
    MIT

  • Darknet MCP

    Vinaysati
    A
    license
    B
    quality
    B
    maintenance
    Enables AI agents to investigate domains, emails, IPs, hashes, URLs, onion addresses, Bitcoin addresses and CVEs across 68 tools spanning 19 threat-intelligence and dark-web source categories, returning bounded evidence with provenance, coverage and explicit skipped, errored or inconclusive checks. It also ships a local investigation dashboard for running combined lookups, reviewing source readiness and downloading JSON reports.
    68
    2
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 15 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but the aggregate recon_domain and investigate_site overlap in scope with several single-purpose tools. Descriptions explicitly guide the agent on when to use each, but the boundary between passive domain overview and active site investigation could still cause misselection.

Naming Consistency3/5

Names mix noun_noun (domain_whois, dns_lookup), verb_noun (compare_domains, investigate_site), recon_ prefixes (recon_domain, recon_batch), and single words (subdomains, wayback). The set remains readable, but no single predictable convention governs all tools.

Tool Count5/5

15 tools is well within a reasonable range for a domain OSINT server and each tool targets a distinct data source or operation (WHOIS, DNS, TLS, CT logs, Wayback, Shodan, ASN, etc.). No tool feels redundant or like padding.

Completeness4/5

The surface covers core domain OSINT needs: registration, DNS, email security, TLS, HTTP headers, certificate transparency, Wayback, IP ownership/routing, and Shodan ports. Minor gaps include no historical DNS lookup, no registrant-to-domain pivoting, and no active port scanning, but agents can largely work around these.

Maintenance

ActivityNo data
ResponsivenessSyncing

Resources