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.

io.github.david-steel/otp-mcp-server

NPM · @ORGTP/MCP-SERVER

Public MCP for OTP (orgtp.com). Query cross-org best practices, learnings, publishers, patterns.

Available components

0 this week 84 Trust /100

Last scanned (17 hours ago)

Scores higher than 75% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 661 tokens (~66/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1
    • Stability: 0.97 → pass security
  • 19 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 17 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 15 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.93 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 21 Nov 2026 · Analysed npm/@orgtp/mcp-server@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~661 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
otp_about ~40

Explain what OTP (Organization Transport Protocol) is, what problem it solves, and how it works. Start here if you've never heard of OTP. No arguments.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

otp_get_org ~68

Get a specific organization's public profile: who they are, what they publish, their agent roster (if exposed), and links to their work.

NameTypeReqDescription
slugstringyesThe org's OTP slug (e.g. 'sneeze-it'). If unknown, use otp_list_publishers first.

No output schema declared.

No examples provided.

otp_get_org_chart ~66

Fetch a publisher's public agent + human org chart. Shows seats, accountability, and which seats are filled by humans vs agents. Powerful for seeing what an L8 organization actually looks like.

NameTypeReqDescription
slugstringyesPublisher slug (e.g. 'sneeze-it').

No output schema declared.

No examples provided.

otp_get_patterns ~68

Surface convergent patterns across OTP organizations: practices that multiple orgs have independently arrived at. The 'everyone is solving this the same way' signal.

NameTypeReqDescription
limitnumber––
topicstring–Optional topic filter, e.g. 'sales', 'agents', 'ops'.

No output schema declared.

No examples provided.

otp_list_publishers ~46

List organizations actively publishing on OTP. Returns name, slug, publish count, and last-publish date for each.

NameTypeReqDescription
limitnumber–Max results (default 25).

No output schema declared.

No examples provided.

otp_network_learnings ~76

Surface what organizations on the OTP network have learned recently. Each learning is a captured correction or success: what failed, what to do, why. The cross-org coordination intelligence feed.

NameTypeReqDescription
limitnumber–Max results (default 20).
since_daysnumber–Look back this many days (default 7).

No output schema declared.

No examples provided.

otp_publishing_guide ~48

Return the step-by-step guide for becoming an OTP publisher: how to capture learnings, publish your first OOS claim, and connect your agent army to the network. No arguments.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

otp_rules_for_role ~87

Get the rules and learnings that apply to a specific role or agent type. Useful when you're building an agent and want to inherit the network's accumulated wisdom for that seat.

NameTypeReqDescription
limitnumber––
rolestringyesRole or agent archetype, e.g. 'chief-of-staff', 'sales-agent', 'project-manager', 'ad-analyst'.

No output schema declared.

No examples provided.

otp_sample_kpis ~65

Show what KPIs OTP-publishing organizations are tracking. Useful for benchmarking your own scorecard against the network.

NameTypeReqDescription
categorystring–Optional category filter, e.g. 'revenue', 'ops', 'agents', 'people'.
limitnumber––

No output schema declared.

No examples provided.

otp_search_best_practices ~97

Search OTP's public best practices library across all publishing organizations. Returns vetted operational patterns that have worked in real companies. Use for any 'what's the best way to...' question.

NameTypeReqDescription
limitnumber–Max results (default 10, max 50).
querystringyesNatural-language description of the topic, e.g. 'pipeline reactivation', 'agent retirement protocol', 'L10 meeting structure'.

No output schema declared.

No examples provided.

Install

How do I install the io.github.david-steel/otp-mcp-server server?

io.github.david-steel/otp-mcp-server runs locally as an npm package, launched with npx -y @orgtp/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @orgtp/mcp-server

# add to Claude Code
claude mcp add david-steel-otp-mcp-server -- npx -y @orgtp/mcp-server
Common questions

What is the io.github.david-steel/otp-mcp-server server?

io.github.david-steel/otp-mcp-server is listed in the public MCP registry as io.github.david-steel/otp-mcp-server. Public MCP for OTP (orgtp.com). Query cross-org best practices, learnings, publishers, patterns. This page covers its npm package (@orgtp/mcp-server).

Is the io.github.david-steel/otp-mcp-server server safe to use?

io.github.david-steel/otp-mcp-server scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.david-steel/otp-mcp-server server expose?

io.github.david-steel/otp-mcp-server exposes 10 tools: otp_about, otp_search_best_practices, otp_network_learnings, otp_list_publishers, otp_get_org, and 5 more. Their descriptions and schemas cost roughly 661 tokens of context every time the server is loaded.

Is the io.github.david-steel/otp-mcp-server server still maintained?

io.github.david-steel/otp-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.david-steel/otp-mcp-server server under?

io.github.david-steel/otp-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.david-steel/otp-mcp-server server?

VerifyMCP ran 16 checks on io.github.david-steel/otp-mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.