# OTInstaller Registry (remote · api.otinstaller.com)

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

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.otinstaller.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-otinstaller-registry/api.md), [page](https://verifymcp.io/servers/com-otinstaller-registry/api)

## Channel facts

- Endpoint: `https://api.otinstaller.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 697 tokens (~116/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-otinstaller-registry 'https://api.otinstaller.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-otinstaller-registry": {
      "url": "https://api.otinstaller.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-otinstaller-registry": {
      "type": "http",
      "url": "https://api.otinstaller.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-otinstaller-registry]
url = "https://api.otinstaller.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-otinstaller-registry": {
      "type": "remote",
      "url": "https://api.otinstaller.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-otinstaller-registry --url 'https://api.otinstaller.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-otinstaller-registry:
    url: "https://api.otinstaller.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-otinstaller-registry": {
      "Transport": "http",
      "Url": "https://api.otinstaller.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-otinstaller-registry -t streamable-http -u 'https://api.otinstaller.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-otinstaller-registry": {
      "type": "http",
      "url": "https://api.otinstaller.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 72, +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.

### 2026-11-02 (score 71, +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.

### 2026-10-31 (score 70, +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.

### 2026-10-29 (score 69, +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.

### 2026-10-27 (score 68, +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.

### 2026-10-25 (score 67, +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.

### 2026-10-23 (score 66, +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.

### 2026-10-22 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `search_tools` (~205 tokens)

Search tools

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.

Input parameters:

- `category` (string): only this category, such as domain-dns or social-media
- `cursor` (string): next_cursor from the previous page
- `input_type` (string): only tools that take this input type (email, username, domain, ip, url, phone, ...); list_types lists them
- `limit` (integer): results per page (default 20)
- `no_keys` (boolean): only tools that need no API key
- `output_type` (string): only tools that find this entity type
- `passive_only` (boolean): only tools that run offline, touch no target and collect no personal data
- `query` (string): words to search for in names, summaries and tags
- `runtime` (string): docker or pipx

### `get_tool` (~73 tokens)

Get a tool

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.

Input parameters:

- `tool` (string, required): the tool, namespace/name or namespace/name@version

### `list_types` (~37 tokens)

List input and entity types

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

### `suggest_pivots` (~55 tokens)

Suggest pivots

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

Input parameters:

- `entity_types` (array, required): entity types, as list_types lists them

### `search_guides` (~95 tokens)

Search guides

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

Input parameters:

- `cursor` (string): next_cursor from the previous page
- `input_type` (string): only guides about this target type
- `level` (string): beginner, intermediate or advanced
- `limit` (integer): results per page (default 20)
- `query` (string): words to search for

### `read_guide` (~65 tokens)

Read a guide page

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

Input parameters:

- `guide` (string, required): the guide, namespace/name or namespace/name@version
- `page` (string): the page path from pages; the first page by default

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-otinstaller-registry/api#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 67
- 2026-10-25: 67
- 2026-10-24: 66
- 2026-10-23: 66
- 2026-10-22: 65
- 2026-10-21: 65

## 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.

### What did VerifyMCP test on the OTInstaller Registry MCP server?

VerifyMCP ran 12 checks on OTInstaller Registry, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about OTInstaller Registry: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.otinstaller.com/mcp
- Repository: https://github.com/OTInstaller/otinstaller
- Website: https://otinstaller.com/docs/agents#remote-server
- Changelog RSS feed: https://verifymcp.io/servers/com-otinstaller-registry/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-otinstaller-registry/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-otinstaller-registry/api.json
- HTML version of this page: https://verifymcp.io/servers/com-otinstaller-registry/api