mcpbeat Sign in

Domain Osint MCP Server

answering

Domain Osint MCP is answering right now. Last checked 13 min ago. It exposes 2 tools.

Inspects live IPv4/IPv6 DNS resolution, TLS certificate issuer/expiry, and HTTP security grade.

Uptime history 68 hours of history
68 hours agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
207 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 12

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 October 2026. No other catalogue keeps this.

16 Oct 2 tools changed the parameters they ask for4 times that day get_agent_wallet_status, recon_domain_osint
16 Oct 2 tool descriptions were rewritten get_agent_wallet_status, recon_domain_osint
16 Oct a tool changed version
15 Oct 2 tool descriptions were rewritten get_agent_wallet_status, recon_domain_osint
15 Oct 2 tools changed the parameters they ask for get_agent_wallet_status, recon_domain_osint
14 Oct a tool changed the parameters it asks for recon_domain_osint
and 2 more, back to 14 October 2026

Nothing serious here today

Today is the operative word: we check Domain Osint MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add domain-osint-mcp --transport http https://domain-osint-72343955726.us-central1.run.app/mcp/domain-osint
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "domain-osint-mcp": {
      "url": "https://domain-osint-72343955726.us-central1.run.app/mcp/domain-osint"
    }
  }
}
~/.codex/config.toml
[mcp_servers.domain-osint-mcp]
url = "https://domain-osint-72343955726.us-central1.run.app/mcp/domain-osint"
.cursor/mcp.json
{
  "mcpServers": {
    "domain-osint-mcp": {
      "url": "https://domain-osint-72343955726.us-central1.run.app/mcp/domain-osint"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "domain-osint-mcp": {
      "url": "https://domain-osint-72343955726.us-central1.run.app/mcp/domain-osint"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent
get_agent_wallet_status
Show an agent's account: free calls used (of 5), prepaid USD balance, total spent, total calls and tokens saved. Free: it never charges or uses a free call. Call it before a batch of paid calls, or after a top-up to confirm the credit arrived. It does not process content or take payments; use the other tools on this server for that. Returns JSON with free_calls_used, balance_usd, total_spent_usd, total_tokens_saved.
recon
recon_domain_osint
Inspects live IPv4/IPv6 DNS resolution, TLS certificate issuer/expiry, and HTTP security grade. Use it when your task needs this for one domain; this endpoint offers only this tool and get_agent_wallet_status. Read-only; results are cached for 1 hour. $0.01 per call. Returns JSON with the result under data. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After that the tool returns a payment-required message (not an error) with a Stripe top-up link (from $2) and Base/Solana USDC addresses; pay, then repeat the same call with the same agent_id, or add tx_hash after a USDC transfer.

Endpoints

URLTransportStateLatencyChecked
https://domain-osint-72343955726.us-central1.run.app/mcp/domain-osint streamable-http answering 210 ms 13 min ago

Alternatives to Domain Osint MCP

same job, measured the same way
MCP Domain Auditor
by geekmarine

DNS resolution, HTTP security headers, and SPF/DMARC email hygiene audits.

1 tools answering
C
CyberSPF
by cyberspf

Assess a domain, IP or ASN: mail and DNS security, certificates, routing and a report card.

122 installs/wk local only
P
PCBLT — Live Checks
by pcblt

Live DNS, email-auth and redirect checks, HTTP security headers, uptime history, PC hardware prices.

12 tools answering
Recon Kit MCP
by nan786521

Read-only network & security recon tools (DNS, TLS, headers, CORS) for AI agents, each graded.

140 installs/wk local only
Security Headers
by basitalisandhu

Fetch a URL's response headers and grade CSP, HSTS, X-Frame-Options and related security headers.

local only
Mozilla Observatory
by pipeworx-io

MDN HTTP Observatory — grade any website's HTTP security headers and get the specific fixes, from…

44 tools answering
Domainintel MCP
by bishop81

Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.

32 installs/wk local only
Domain Lab
by domainlab

Track domain expiry, DNS, SSL and email security across registrars, and explain what changed.

answering

Domain Osint MCP — questions

Answers built from our own checks of this server.

What can Domain Osint MCP do?
It exposes 2 tools, read directly from the server on our last check. Among them: get_agent_wallet_status, recon_domain_osint. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Domain Osint MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 207 ms. The bar chart above shows every period we have measured.
How do I connect Domain Osint MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Domain Osint MCP need an API key?
No. Domain Osint MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Domain Osint MCP?
It answers our handshake in 207 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.