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.

OTInstaller Registry

REMOTE · API.OTINSTALLER.COM

Read-only search of the OTInstaller registry of OSINT tools and guides, with consent classes.

+3 this week 72 Trust /100

Last scanned (6 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

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 Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 697 tokens (~116/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://api.otinstaller.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=otinstaller.com CN=WE1,O=Google Trust Services,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 d5e40dcce3779f79138ce03838b44c1e
SANs: otinstaller.com, api.otinstaller.com, *.api.otinstaller.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 api.otinstaller.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
otinstaller.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.otinstaller.com/mcp Verified 200
http (plaintext) http://api.otinstaller.com/mcp Inconclusive 405
MCP tools · 6 exposed · ~530 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
get_tool ~73

A tool's inputs, outputs, API keys, network access and ethics flags, the consent class `ot mcp` will put a run in, what a run does in plain words, and how to install and run it with ot.

NameTypeReqDescription
toolstringyesthe tool, namespace/name or namespace/name@version

No output schema declared.

No examples provided.

list_types ~37

The input types tools take, the entity types they find, the categories, and which input types each entity type can feed (the pivot map).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_guide ~65

One page of a guide, as Markdown, with the list of its pages and the tools it uses.

NameTypeReqDescription
guidestringyesthe guide, namespace/name or namespace/name@version
pagestring–the page path from pages; the first page by default

No output schema declared.

No examples provided.

search_guides ~95

Search the registry's investigation guides (methods, checklists, references) by words, target type or level.

NameTypeReqDescription
cursorstring–next_cursor from the previous page
input_typestring–only guides about this target type
levelstring–beginner, intermediate or advanced
limitinteger–results per page (default 20)
querystring–words to search for

No output schema declared.

No examples provided.

search_tools ~205

Search the registry's OSINT tools by words, the input type they take, the entity type they find, or category. passive_only keeps the tools ot runs without asking the person.

NameTypeReqDescription
categorystring–only this category, such as domain-dns or social-media
cursorstring–next_cursor from the previous page
input_typestring–only tools that take this input type (email, username, domain, ip, url, phone, ...); list_types lists them
limitinteger–results per page (default 20)
no_keysboolean–only tools that need no API key
output_typestring–only tools that find this entity type
passive_onlyboolean–only tools that run offline, touch no target and collect no personal data
querystring–words to search for in names, summaries and tags
runtimestring–docker or pipx

No output schema declared.

No examples provided.

suggest_pivots ~55

For entity types found so far (a subdomain, an account, an email ...), the tools that take them as input, best first.

NameTypeReqDescription
entity_typesarrayyesentity types, as list_types lists them

No output schema declared.

No examples provided.

Install

How do I install the OTInstaller Registry MCP server?

OTInstaller Registry is a hosted endpoint at https://api.otinstaller.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 · api.otinstaller.com

# add to Claude Code
claude mcp add --transport http com-otinstaller-registry 'https://api.otinstaller.com/mcp'
Common questions

What is the OTInstaller Registry MCP server?

OTInstaller Registry is an MCP server listed in the public MCP registry as com.otinstaller/registry. Read-only search of the OTInstaller registry of OSINT tools and guides, with consent classes. This page covers its hosted endpoint (https://api.otinstaller.com/mcp).

Is the OTInstaller Registry MCP server safe to use?

OTInstaller Registry scores 72 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 OTInstaller Registry MCP server expose?

OTInstaller Registry exposes 6 tools: search_tools, get_tool, list_types, suggest_pivots, search_guides, read_guide. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.

Does the OTInstaller Registry MCP server require authentication?

No. We connected to OTInstaller Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the OTInstaller Registry MCP server still maintained?

OTInstaller Registry is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.