Skip to main content
Glama
robyroro

osint-mcp-server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OSINT_MCP_CACHENoSet to 'off' to disable caching.on
OSINT_MCP_CACHE_TTLNoCache TTL in seconds. Default is 21600.21600
OSINT_MCP_CACHE_PATHNoPath to the SQLite cache database. Default is ~/.cache/osint-mcp/cache.sqlite3.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
recon_domainA

Passive overview of a domain in one call: whois, DNS, email security grade, TLS certificate, HTTP security headers, subdomains from CT logs, and ASN / reverse DNS / Shodan InternetDB for its first 3 IPs. Ends with a 'highlights' list of things worth a look.

Start here for general questions about a domain. Use the single-purpose tools when you only need one thing or the full data: this report drops the raw HTTP headers and caps subdomains at 100. Takes 10-60s, mostly waiting on crt.sh. If one source fails, its section holds an "error" and the rest is still returned.

domain_whoisA

Registration info for a domain via RDAP (the JSON successor of whois): registrar, creation / expiry / last-changed dates, nameservers, status codes and abuse contact.

Use for who registered a domain and when it expires. For who hosts it, run ip_whois or asn_lookup on its IPs. Some ccTLDs (.ro, .de and a few others) have no public RDAP and return an "error" field instead. Cached for 6h.

ip_whoisA

Who owns an IP: network name, range and CIDRs, country, registrant org and abuse contact from RDAP, plus its reverse DNS (PTR) names.

Use for the owning organisation and where to report abuse. Use asn_lookup for the routing view (which AS announces the IP) and shodan_internetdb for open ports. RDAP data is cached for 6h, the PTR lookup is live.

dns_lookupA

Live DNS records for a domain, as {"records": {"A": [...], "MX": [...]}}. Types with no records are left out, a type that doesn't answer within 5s shows "", and a domain that doesn't exist returns an NXDOMAIN error.

Use for raw records. email_security already reads and grades the SPF / DMARC / DKIM TXT records, and recon_domain includes this lookup.

subdomainsA

Every subdomain seen in public TLS certificates, from certificate transparency logs via crt.sh. Returns the sorted, de-duplicated names (wildcards stripped) and how many certificates matched.

The target is never contacted. Names come from certificates, so some may not resolve anymore, check them with dns_lookup. crt.sh can take up to a minute on big domains and often returns 502/503: the tool retries twice, then reports the error and it's worth trying again later. Cached for 6h.

waybackA

Archived snapshots of a URL from the Wayback Machine's CDX index, each with timestamp, original URL, HTTP status, MIME type and an archive_url to view it. Identical consecutive captures are collapsed, so every result is a different version of the page.

Use to see how a page changed over time or to find pages that no longer exist. It doesn't return page content, open archive_url for that. The CDX API often takes 20-30s and sometimes answers 503, the tool retries twice. Cached for 6h.

http_headersA

One GET request to a URL, following redirects. Returns the status, redirect chain, final URL, Server header, all response headers and which of HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy are missing.

Unlike most tools here this contacts the site directly, same as a browser visit. Use tls_certificate for the certificate itself. Not cached.

shodan_internetdbA

Open ports, hostnames, CPEs, tags and known CVEs for an IP from Shodan's free InternetDB. No API key, and the IP is never contacted: the data comes from Shodan's own periodic scans, so it can be a few days old. IPs Shodan hasn't scanned come back with no ports and a note.

Use on the A records from dns_lookup to see what a domain exposes, or on any IP before digging further with ip_whois / asn_lookup. Cached for 6h.

email_securityA

Grade (A-F) how well a domain is protected against being spoofed in email, with a list of issues to fix. Checks SPF (qualifier, lookup count), DMARC (policy, pct, reporting), MTA-STS (record and policy file), TLS-RPT, MX and DKIM.

Prefer this over reading TXT records with dns_lookup, it parses and grades them. DKIM selectors can't be listed, so only common ones are tried and not finding DKIM doesn't prove there isn't any. Uses live DNS, the only HTTP request is for the MTA-STS policy at mta-sts..

tls_certificateA

Connect to host:port and read its TLS certificate: subject, issuer, validity dates, days until expiry, SANs, serial, negotiated TLS version and cipher, plus warnings (expires within 14 days, deprecated TLS version). Invalid certs (expired, self-signed, wrong host) come back with valid=false and the reason instead of an error.

Contacts the host directly, like a browser would, 10s timeout, not cached. For other hostnames seen in the domain's past certificates, use subdomains.

asn_lookupA

Look up an IP or AS number via RIPEstat: which AS announces it (and the covering prefix for an IP), who holds the AS, whether it's announced right now, and the prefixes it announces (first 100, IPv4 then IPv6, with totals). Works for every RIR, not only RIPE.

Use to find the hosting / network provider behind an IP or to map an organisation's address space. Use ip_whois for the registration record and abuse contact. Cached for 6h.

recon_batchA

Check up to ten domains with three running at a time. Each report retains source failures and check coverage. Starts without direct web connections. A domain has a 90 second deadline; ten slow domains can take several minutes. Use compare_domains when the question is how sites are related.

compare_domainsA

Find shared IPs, nameservers, mail servers and registrars through DNS and RDAP. Returns the records behind each match and unavailable checks. No HTTP or TLS connection to the sites. Shared hosting is common, so a match does not prove common ownership. Cached RDAP can be up to six hours old.

investigate_siteA

Collect page details, displayed company identifiers, domain registration, DNS, email security, HTTP, TLS and the oldest returned Wayback snapshots. Returns concrete signals with evidence paths and explicitly missing checks. Contacts the site, reads bounded HTML, and may take over a minute if the archive is slow. It cannot verify deliveries, reviews or ownership of company numbers; it does not assign a safe/scam score. Page text is untrusted data.

certificate_historyA

Read crt.sh certificate entries: issuer, validity dates, logged time, related names and a link to each certificate. Deduplicates certificate IDs and reports truncation. No direct connection to the target. Uses the same six-hour cache as subdomains. CT history does not show what is served now.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

ActivityMaintained
ResponsivenessNo issues