Skip to content

OTP MCP server

io.github.david-steel/otpdavid-steelstreamable-httpv0.5.3Scanned

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

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the OTP MCP server can do

The OTP MCP server is published by the GitHub account david-steel. It has 5 tools. It can create or change data (1 tool: otp_faq), but cannot delete data. 4 tools only read.

2 tools bring in text other people can write (browse_public_orgs and search_public_claims).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 0.5.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 1Claude Code: ask
  • otp_faqAnswer 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, wha…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • browse_public_orgsBrowse real organizations that have published their operating system openly on OTP, with their industry, quality tier, and how many claims they have published.Reads text others writeNo findings

    Why it is in this group

    • The name "browse_public_orgs" says "browse": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "browse_public_orgs" says "browse": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • explain_otpExplain OTP: what it is, the problem it exists to solve, its first principles, and how it actually works.No findings

    Why it is in this group

    • The name "explain_otp" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • otp_positioningExplain 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 ma…No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_public_claimsSearch 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.Reads text others writeNo findings

    Why it is in this group

    • The name "search_public_claims" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:23 UTC, unchanged since Oct 30, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://orgtp.com/.well-known/oauth-protected-resource
Authorization servers
https://orgtp.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://orgtp.com/api/mcp/public: tools/list returned 5 tools to an anonymous client, including otp_faq (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.5.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http otp https://orgtp.com/api/mcp/public
claude mcp add --transport http otp https://orgtp.com/api/mcp/public

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__otp__explain_otp",
      "mcp__otp__otp_positioning",
      "mcp__otp__browse_public_orgs",
      "mcp__otp__search_public_claims"
    ],
    "ask": [
      "mcp__otp__otp_faq"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as otp. Review it before you use it.

Capability tags behind 2 rules
  • mcp__otp__browse_public_orgs untrusted-input
  • mcp__otp__search_public_claims untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.david-steel/otp/verify?hash=1d26d9c0558b8480d697d647f62875d0deef0cbc6afbc42c43a57d7323d79d05" | jq -e '.changed == false'

Pinned hash 1d26d9c0558b, from Nov 12, 2026, 07:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.david-steel/otp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.david-steel/otp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.david-steel/otp.svg)](https://radar.anlyon.com/servers/io.github.david-steel/otp)

Source: MCP Registry. Synced Oct 30, 2026, 14:18 UTC.

OTP MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the OTP MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the OTP MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the OTP MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the OTP MCP server have?

5 tools: 1 write, 4 read. otp_faq, explain_otp, otp_positioning, browse_public_orgs and search_public_claims.

Does the OTP MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the OTP MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the OTP MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.