io.github.david-steel/otp-mcp-server
NPM · @ORGTP/MCP-SERVER · SCANNED SEP 22
Public MCP for OTP (orgtp.com). Query cross-org best practices, learnings, publishers, patterns.
Available components
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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 135 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add david-steel-otp-mcp-server -- npx -y @orgtp/mcp-server
{
"mcpServers": {
"david-steel-otp-mcp-server": {
"command": "npx",
"args": [
"-y",
"@orgtp/mcp-server"
]
}
}
} {
"servers": {
"david-steel-otp-mcp-server": {
"command": "npx",
"args": [
"-y",
"@orgtp/mcp-server"
]
}
}
} codex mcp add david-steel-otp-mcp-server -- npx -y @orgtp/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"david-steel-otp-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@orgtp/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add david-steel-otp-mcp-server --command npx --arg -y --arg @orgtp/mcp-server
mcp_servers:
david-steel-otp-mcp-server:
command: "npx"
args: ["-y", "@orgtp/mcp-server"] {
"McpServers": {
"david-steel-otp-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@orgtp/mcp-server"
]
}
}
} assistant mcp add david-steel-otp-mcp-server -t stdio -c npx -a -y @orgtp/mcp-server
{
"mcpServers": {
"david-steel-otp-mcp-server": {
"command": "npx",
"args": [
"-y",
"@orgtp/mcp-server"
]
}
}
} 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.
- 21 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
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 22 Sept 2026 · Analysed npm/@orgtp/mcp-server@0.1.1
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Publisher 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| topic | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20). |
| since_days | number | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| role | string | yes | Role 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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter, e.g. 'revenue', 'ops', 'agents', 'people'. |
| limit | number | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 10, max 50). |
| query | string | yes | Natural-language description of the topic, e.g. 'pipeline reactivation', 'agent retirement protocol', 'L10 meeting structure'. |
No output schema declared.
No examples provided.
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 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 22 September 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.