# OTP (remote · orgtp.com)

Put AI agents on your org chart: seats, KPIs, to-dos, meetings and logged work, next to the people.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `orgtp.com`: 38/100, [markdown](https://verifymcp.io/servers/david-steel-otp/api-mcp.md), [page](https://verifymcp.io/servers/david-steel-otp/api-mcp)
- remote · `orgtp.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/david-steel-otp/api-mcp-public.md), [page](https://verifymcp.io/servers/david-steel-otp/api-mcp-public)
- npm · `otp-mcp-server`: 62/100, [markdown](https://verifymcp.io/servers/david-steel-otp/otp-mcp-server.md), [page](https://verifymcp.io/servers/david-steel-otp/otp-mcp-server)

## Channel facts

- Endpoint: `https://orgtp.com/api/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.3`

## 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**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the OTP MCP server?

OTP is a hosted endpoint at https://orgtp.com/api/mcp/public, 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 david-steel-otp 'https://orgtp.com/api/mcp/public'
```

### Cursor

```json
{
  "mcpServers": {
    "david-steel-otp": {
      "url": "https://orgtp.com/api/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "david-steel-otp": {
      "type": "http",
      "url": "https://orgtp.com/api/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.david-steel-otp]
url = "https://orgtp.com/api/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "david-steel-otp": {
      "type": "remote",
      "url": "https://orgtp.com/api/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add david-steel-otp --url 'https://orgtp.com/api/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  david-steel-otp:
    url: "https://orgtp.com/api/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "david-steel-otp": {
      "Transport": "http",
      "Url": "https://orgtp.com/api/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add david-steel-otp -t streamable-http -u 'https://orgtp.com/api/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "david-steel-otp": {
      "type": "http",
      "url": "https://orgtp.com/api/mcp/public"
    }
  }
}
```

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 75, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-04 (score 75, +1)

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

### 2026-11-02 (score 74, +1)

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

### 2026-10-31 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 72)

First indexed and scored.

## MCP tools (5)

### `explain_otp` (~197 tokens)

Explain what OTP is and why it exists

Explain OTP: what it is, the problem it exists to solve, its first principles, and how it actually works. Call this first when someone asks what OTP is, why it was built, what it believes, or how to think about it. Returns the constitution verbatim, plus a short published summary of how it works day to day, so the answer reflects what the product actually commits to rather than marketing copy. Ask for a topic to narrow it. This is public material with no account required. It does NOT carry financials, customer data, or unshipped roadmap.

Input parameters:

- `topic` (string): Which part to return. 'overview' = why OTP exists and the working axiom. 'principles' = the full constitution, the laws it holds itself to. 'product' = what it actually does day to day, and how it is…

### `otp_positioning` (~95 tokens)

How OTP is positioned against the alternatives

Explain where OTP sits in the market and why it is not the same thing as the tools it gets compared to (meeting and conversation intelligence, operating-system software, project management, HR systems). Call this when someone asks how OTP is different, who it competes with, why it is not just another meeting tool, or what category it is in. Public positioning material. Does NOT carry pricing strategy, deal terms, or roadmap.

### `otp_faq` (~106 tokens)

Common questions and confusions about OTP

Answer common questions and clear up common confusions about OTP: what an agent seat is, whether OTP replaces the tools a team already runs, what happens to the weekly meeting, what it means for AI agents to be accountable, and what OTP deliberately refuses to do. Call this when someone is stuck on a concept or pushing back on the premise.

Input parameters:

- `question` (string): The specific thing the person is confused about, if there is one. Omit to get the whole list.

### `browse_public_orgs` (~113 tokens)

Browse organizations that publish how they run

Browse real organizations that have published their operating system openly on OTP, with their industry, quality tier, and how many claims they have published. Call this when someone asks for proof, for examples, for who actually uses this, or wants to see what a published operating system looks like in practice. Returns only what those organizations chose to make public.

Input parameters:

- `industry` (string): Filter to one industry, e.g. "AI services".
- `limit` (number): How many to return. Defaults to 10.

### `search_public_claims` (~119 tokens)

Search what organizations have published about how they work

Search across the claims that organizations have published openly on OTP: how they coordinate, what they learned, what failed, and how confident they are in each. Call this when someone wants evidence on a specific practice, wants to know what other organizations do about a problem, or asks what the network has actually learned. Returns published public material only.

Input parameters:

- `limit` (number): How many results. Defaults to 10.
- `query` (string, required): What to search for, in plain language. E.g. "how do teams handle agent escalation".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/david-steel-otp/api-mcp-public#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72

## Common questions

### What is the OTP MCP server?

OTP is an MCP server listed in the public MCP registry as io.github.david-steel/otp. Put AI agents on your org chart: seats, KPIs, to-dos, meetings and logged work, next to the people. This page covers its hosted endpoint (https://orgtp.com/api/mcp/public).

### Is the OTP MCP server safe to use?

OTP scores 75 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 OTP MCP server expose?

OTP exposes 5 tools: explain_otp, otp_positioning, otp_faq, browse_public_orgs, search_public_claims. Their descriptions and schemas cost roughly 630 tokens of context every time the server is loaded.

### Does the OTP MCP server require authentication?

Its publisher declares no required credentials for OTP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the OTP MCP server still maintained?

OTP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://orgtp.com/api/mcp/public
- Website: https://orgtp.com/
- Changelog RSS feed: https://verifymcp.io/servers/david-steel-otp/api-mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/david-steel-otp/api-mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/david-steel-otp/api-mcp-public