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.

OTP

REMOTE · ORGTP.COM · 3 COMPONENTS

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

75 Trust /100

Last scanned (4 hours ago)

Scores higher than 64% of remote servers

Unreachable for 1 day in a row. Last reached 4 Nov 2026.

Category Project Management

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

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.

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 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 4 Nov 26 +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.

  • 2 Nov 26 +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.

  • 31 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 30 Oct 26 72

    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 5 Nov 2026 · Probed https://orgtp.com/api/mcp/public

TLS unreached
DNSSEC insecure

Validation of orgtp.com. — Not signed

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

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://orgtp.com/api/mcp/public Unreachable
http (plaintext) http://orgtp.com/api/mcp/public HTTPS enforced
MCP tools · 5 exposed · ~630 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
browse_public_orgs ~113

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.

NameTypeReqDescription
industrystring–Filter to one industry, e.g. "AI services".
limitnumber–How many to return. Defaults to 10.

No output schema declared.

No examples provided.

explain_otp ~197

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.

NameTypeReqDescription
topicstring–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…

No output schema declared.

No examples provided.

otp_faq ~106

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.

NameTypeReqDescription
questionstring–The specific thing the person is confused about, if there is one. Omit to get the whole list.

No output schema declared.

No examples provided.

otp_positioning ~95

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_public_claims ~119

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.

NameTypeReqDescription
limitnumber–How many results. Defaults to 10.
querystringyesWhat to search for, in plain language. E.g. "how do teams handle agent escalation".

No output schema declared.

No examples provided.

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.

remote · orgtp.com

# add to Claude Code
claude mcp add --transport http david-steel-otp 'https://orgtp.com/api/mcp/public'
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.