Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.thetempleofdoom.osint-mcp/osint-terminal

REMOTE · OSINT-MCP.THETEMPLEOFDOOM.COM · SCANNED SEP 26

454 OSINT recon tools + server-side entity correlation & person sweeps. Keyless.

56 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability29
  • Instruction-quality not yet verified: the AI judgement didn't run.Unverified
  • Tool/resource definitions use about 13426 tokens (~29/item across 457 items; 457 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 457 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • Manipulation not yet verified: none of the 457 captured unit(s) of tool text has been judged yet, so we will not certify text no model has read as clean.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the com.thetempleofdoom.osint-mcp/osint-terminal server?

com.thetempleofdoom.osint-mcp/osint-terminal is a hosted endpoint at https://osint-mcp.thetempleofdoom.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · osint-mcp.thetempleofdoom.com

# add to Claude Code
claude mcp add --transport http com-thetempleofdoom-osint-mcp-osint-terminal 'https://osint-mcp.thetempleofdoom.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-thetempleofdoom-osint-mcp-osint-terminal": {
      "url": "https://osint-mcp.thetempleofdoom.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-thetempleofdoom-osint-mcp-osint-terminal": {
      "type": "http",
      "url": "https://osint-mcp.thetempleofdoom.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-thetempleofdoom-osint-mcp-osint-terminal]
url = "https://osint-mcp.thetempleofdoom.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thetempleofdoom-osint-mcp-osint-terminal": {
      "type": "remote",
      "url": "https://osint-mcp.thetempleofdoom.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-thetempleofdoom-osint-mcp-osint-terminal --url 'https://osint-mcp.thetempleofdoom.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-thetempleofdoom-osint-mcp-osint-terminal:
    url: "https://osint-mcp.thetempleofdoom.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-thetempleofdoom-osint-mcp-osint-terminal": {
      "Transport": "http",
      "Url": "https://osint-mcp.thetempleofdoom.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-thetempleofdoom-osint-mcp-osint-terminal -t streamable-http -u 'https://osint-mcp.thetempleofdoom.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-thetempleofdoom-osint-mcp-osint-terminal": {
      "type": "http",
      "url": "https://osint-mcp.thetempleofdoom.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
    • New tool “agent_manifest” functional
    • New tool “correlate_sweep” functional
    • New tool “person_sweep” functional
  • 23 Sept 26 55

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 26 Sept 2026 · Probed https://osint-mcp.thetempleofdoom.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thetempleofdoom.com CN=WE1,O=Google Trust Services,C=US 16 Aug 2026 14 Nov 2026 ECDSA 256 ECDSA-SHA256 8554684b5ee7e09e0e9320057a46c58e
SANs: thetempleofdoom.com, *.thetempleofdoom.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of osint-mcp.thetempleofdoom.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
thetempleofdoom.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=2592000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://osint-mcp.thetempleofdoom.com/mcp Verified 200
http (plaintext) http://osint-mcp.thetempleofdoom.com/mcp HTTPS enforced 301 https://osint-mcp.thetempleofdoom.com/mcp
MCP tools · 457 exposed · ~13,426 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
passwordcheck ~32

Password Pwned: HIBP k-anonymity breach check (safe)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

paste_domain ~34

Paste Domain Search: Find domain in public pastes via psbdmp.ws (no key)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

paste_email ~37

Paste Email Search: Find email in public pastes via Wayback CDX + search links (no key)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

peeringdb ~31

PeeringDB: Network type, traffic, IX/facility presence

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

peeringnet ~32

PeeringDB Net: Peering policy / traffic / IX presence for ASN

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

peers ~26

ASN Peers: Upstream/downstream BGP neighbours

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

permissions_pol ~29

Permissions Policy: Permissions-Policy: camera/mic/geo controls

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

person_sweep ~43

Person-focused sweep: checks ~30 username/email/social presence tools for one name/handle and returns where it exists plus extracted entities.

NameTypeReqDescription
namestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

pgp ~29

PGP Key: Public key published on keys.openpgp.org

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phishing_intel ~28

Phishing Intel: Phishing kit tracking + URL detection

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phone ~26

Phone Number: E.164 country/region (offline)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phone_leak ~28

Phone Leak Check: Search for phone number in leaked databases

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phoneapps ~30

Messaging Links: WhatsApp / Telegram / Viber / Signal deep links

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phonecc ~28

Calling Code: Country, trunk & intl dialing prefixes (offline)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phonefmt ~33

Phone Format: E.164 / national / international / RFC3966 formats (offline)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phonenanp ~34

NANP Area Code: +1 number → US/Canada region (offline subset)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phonepivot ~33

Phone Lookups: Caller-ID / reputation site links (Truecaller, Sync.me…)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phonespam ~28

Spam Reports: Robocall / scam report-database links

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

phonevcard ~29

vCard: Generate a .vcf contact card (offline)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

pluscode ~31

Plus Code: Coords → Open Location Code / Google Plus Code (offline)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

port ~26

Port Reference: Service + exposure notes for a port number

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

portlookup ~27

Port Lookup: IANA port → service name (offline)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

portquick ~27

Port Check: Quick TCP port scan (2s timeout)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

portscan ~27

Port Scan: TCP connect scan: common + camera ports

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

pubmed ~27

PubMed: PubMed biomedical paper search (NCBI)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

punycode ~40

Punycode/IDN: IDN domain ↔ Punycode (xn--) homograph check (offline)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

pwstrength ~24

Password Strength: Offline entropy/strength estimate

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

pypi ~26

PyPI Package: Python package metadata + links

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

pypiproject ~28

PyPI Project: PyPI version/license/links

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

pypistats ~27

PyPI Downloads: PyPI recent download counts

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

qrcode ~27

QR Code: Generate a QR code for text/URL

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

quakes ~36

Earthquakes: USGS recent quakes — global or near coords (M2.5+)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

quoted_printable ~29

Quoted-Printable: Quoted-printable encode/decode

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

railfence ~30

Rail Fence: Rail-fence cipher over 3 rails (offline)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

random_fact ~22

Random Fact: Random trivia fact

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

randomuser ~30

Random Identity: Synthetic identity for sockpuppet hygiene (randomuser.me)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

ransomware_tracker ~29

Ransomware Groups: Ransomware gang profiles + recent hits

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

rdap ~33

RDAP Registration: Structured domain registration record (RDAP/IANA bootstrap, no key)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

rdap_domain ~27

RDAP Domain: RDAP structured domain registration data

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

rdapip ~29

RDAP IP: Authoritative RDAP record for an IP

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

reddit_sub ~29

Reddit Subreddit: Subreddit: subscribers, active users, description

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

reddit_user ~28

Reddit User: Reddit user: karma, age, verified status

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

redirects ~23

Redirect Tracer: Full HTTP redirect chain

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

referrer_pol ~30

Referrer Policy: Referrer-Policy header — URL leakage risk

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

regdomain ~31

Registered Domain: Extract eTLD+1 registered domain from URL (offline)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

restcountry ~31

Country Detail: Capital/region/income by name or ISO (World Bank)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

reversedns ~23

Reverse DNS: PTR record / hostname

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

reverseip ~24

Reverse IP: Other domains sharing the host

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

revgeo ~31

Reverse Geocode: lat,lon -> address (OSM Nominatim)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

revgeocode ~28

Reverse Geocode: Coordinates → nearest address (OSM)

NameTypeReqDescription
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the com.thetempleofdoom.osint-mcp/osint-terminal server?

com.thetempleofdoom.osint-mcp/osint-terminal is listed in the public MCP registry as com.thetempleofdoom.osint-mcp/osint-terminal. 454 OSINT recon tools + server-side entity correlation & person sweeps. Keyless. This page covers its hosted endpoint (https://osint-mcp.thetempleofdoom.com/mcp).

Is the com.thetempleofdoom.osint-mcp/osint-terminal server safe to use?

com.thetempleofdoom.osint-mcp/osint-terminal scores 56 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.thetempleofdoom.osint-mcp/osint-terminal server expose?

com.thetempleofdoom.osint-mcp/osint-terminal exposes 457 tools: dns, whois, subdomains, tls, headers, and 452 more. Their descriptions and schemas cost roughly 13,426 tokens of context every time the server is loaded.

Does the com.thetempleofdoom.osint-mcp/osint-terminal server require authentication?

No. We connected to com.thetempleofdoom.osint-mcp/osint-terminal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.thetempleofdoom.osint-mcp/osint-terminal server still maintained?

com.thetempleofdoom.osint-mcp/osint-terminal is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.