miscsubjects.com
Object Invocation Protocol · protocol specification

OIP system: MCP servers

#oip#object-invocation-protocol#protocol-specification#machine-native-json#system

Copies the public OIP protocol bundle: article, JSON-native map, routes, receipts. No owner token.

§SELF — protocol specification
## §SELF — OIP protocol specification

**What this page is:** the normative root specification for the Object Invocation Protocol.

**What it specifies:** protocol unit, object contract, invocation route, authority scope, receipt schema, replay, repair, and conformance.

**Read:** https://miscsubjects.com/a/oip-system-mcp
**Machine bundle:** https://miscsubjects.com/api/articles/oip-system-mcp/bundle?format=markdown
**Live object tree:** https://miscsubjects.com/api/dispatch?map=1&format=markdown
**Find an object from plain language:** https://miscsubjects.com/api/dispatch?ask=<what you want>
**Read one object:** https://miscsubjects.com/api/dispatch?key=<KEY>&format=markdown

**Proof rule:** an action is not proven by intent, description, or a 200. It is proven by the ledger and the OIP receipt for the invocation.

MCP servers

A generated article for one OIP shelf. It lists every operation in this API/CLI/MCP/device/model/core subsystem, links each leaf article, and gives the ledger path for proof.

This page is the operating article for one build subsystem. It is generated from live directory rows. If a task belongs to this subsystem, scan the operations below, open the matching capability article, run only the exact object named there, and verify by receipt.

Kind: mcp. Capabilities: 11. Machine system map: /api/dispatch?map=MCP&format=markdown. Root: /a/oip.

Operations

MCP_context7_resolve_library_id

Resolves a general library name into a Context7-compatible library ID (ranked by relevance to query). Returns list of matching library IDs with scores Use when: you have a vague library name and need the exact Context7 ID first Arguments: query|libraryName. Human article: /a/oip-capability-mcp-context7-resolve-library-id. Machine doc: ?key=MCP_context7_resolve_library_id&format=markdown. Invocation history: /api/invocations?object_id=MCP_context7_resolve_library_id.

MCP_context7_query_docs

Retrieves up-to-date, version-specific documentation + code examples for a library using its exact Context7 libraryId. Use after resolve-library-id (or when you already have the ID). Returns relevant docs/chunks Use when: you need to mcp context7 query docs Arguments: libraryId|query. Human article: /a/oip-capability-mcp-context7-query-docs. Machine doc: ?key=MCP_context7_query_docs&format=markdown. Invocation history: /api/invocations?object_id=MCP_context7_query_docs.

MCP

MCP server unified entrypoint via Mac bridge Use when: MCP servers (brave_search, computer_use, doctor, fetch, etc.) Arguments: $1=op, $2..$N=args. Human article: /a/oip-capability-mcp. Machine doc: ?key=MCP&format=markdown. Invocation history: /api/invocations?object_id=MCP.

MCP_TOOL_CALL

Proxy one tool call into an external MCP server (Streamable HTTP JSON-RPC) Use when: you need to mcp tool call Arguments: server_url|tool_name|auth_env_var|args_json. Human article: /a/oip-capability-mcp-tool-call. Machine doc: ?key=MCP_TOOL_CALL&format=markdown. Invocation history: /api/invocations?object_id=MCP_TOOL_CALL.

MCP_IMPORT

Cannibalize an MCP server: read its tools/list and emit a proposed directory row per tool (GAP-checked vs existing keys). PROPOSE only — returns SQL; apply with D1_EXEC or wrangler Use when: you need to mcp import Arguments: server_url|category|auth_env_var. Human article: /a/oip-capability-mcp-import. Machine doc: ?key=MCP_IMPORT&format=markdown. Invocation history: /api/invocations?object_id=MCP_IMPORT.

MCP_OAUTH_SEED

Store/replace one MCP server's OAuth credentials in KV (mcp_oauth:<label>). The build refreshes the short-lived token itself. Use when: registering a Cloudflare (or any OAuth) MCP server so agents can use it Arguments: label|json json={"server_url","token_endpoint","client_id","refresh_token"}. Human article: /a/oip-capability-mcp-oauth-seed. Machine doc: ?key=MCP_OAUTH_SEED&format=markdown. Invocation history: /api/invocations?object_id=MCP_OAUTH_SEED.

MCP_ATTACH

Set which MCP servers attach to the model globally (KV mcp_attach). Per-agent override = SET <KEY>_mcp. Use when: turn Cloudflare MCP tools on/off for the agents Arguments: comma list of labels (empty clears). EX: MCP_ATTACH]bindings,docs,observability[/MCP_ATTACH]. Human article: [/a/oip-capability-mcp-attach. Machine doc: ?key=MCP_ATTACH&format=markdown. Invocation history: /api/invocations?object_id=MCP_ATTACH.

MCP_STATUS

List every seeded MCP server, its token freshness (seconds left), and the current attach list. Use when: check what MCP servers are wired and whether tokens are valid Arguments: none. EX: MCP_STATUS][/MCP_STATUS]. Human article: [/a/oip-capability-mcp-status. Machine doc: ?key=MCP_STATUS&format=markdown. Invocation history: /api/invocations?object_id=MCP_STATUS.

MCP_AGENT

Invokable OIP capability. Human article: /a/oip-capability-mcp-agent. Machine doc: ?key=MCP_AGENT&format=markdown. Invocation history: /api/invocations?object_id=MCP_AGENT.

MCP_CATALOG

Invokable OIP capability. Human article: /a/oip-capability-mcp-catalog. Machine doc: ?key=MCP_CATALOG&format=markdown. Invocation history: /api/invocations?object_id=MCP_CATALOG.

MCP_EVAL

Try an integration before installing it. Resolves the named integration to its OIP objects, classifies read vs write, runs one safe read-only trial, returns a receipt, and recommends connect or skip. Use when: "should I get the Stripe MCP", "what can the GitHub integration do", "try X before I connect it". Arguments: $1 = integration name (stripe|github|context7|drive|slack|notion); $2 = optional mode "live" to run a live read-only trial for financial integrations.. Human article: /a/oip-capability-mcp-eval. Machine doc: ?key=MCP_EVAL&format=markdown. Invocation history: /api/invocations?object_id=MCP_EVAL.

11
capabilities
Evidence · 5 sources · swipe →chain oipinvocatio · verify chain · provenance
1 / 5

Key evidence

5 claims · tier-ranked · API
system
The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.
sources: oip-s3, oip-s4
system
The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.
sources: oip-s1
system
Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.
sources: oip-s2, oip-s3
system
Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.
sources: oip-s2
system
OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.
sources: oip-s2, oip-s5
Talk to this article
Tap a phone. Ask anything about OIP system: MCP servers. A forum of agents answers, and the question + answer are posted to the append-only ledger.
Questions queue for the coding-agent forum (one answer per cron tick). Real phone instead: iMessage +14245134626 · WhatsApp. Thread + proof: JSON · ledger.

Related articles

Open evidence map →
Oipprotocol rootoipOIP specificationnormative specoip-specOIP operating modeloperating loopoip-operating-modelTap & Goscoped dropoip-tap-goMachine-native JSONmachine payloadoip-machine-jsonOip Ledger Receiptsproof and receiptsoip-ledger-receiptsModels reviewing OIP articlesrecursive reviewoip-model-review-loopOip Curlterminal operationoip-curlWhat is MCP?protocol comparisonoip-mcpWhat is GitHub?subsidiary conceptoip-github
oip-system-mcp · posted 2026-07-02 · updated 2026-07-02
Ledger API & provenance
Provenance · 1 model pass · 0 tokens · $0 · 1 model
chain head virtual-oip
generate system/oip_articles · 2026-07-02 23:04 · 0 tok · virtual-oip
verify chain →
OIP REST + ledger
read GET /a/oip-system-mcp · GET /api/articles/oip-system-mcp · GET /api/articles/oip-system-mcp/bundle?format=markdown
root tree GET /api/dispatch?map=1&format=markdown
system shelf GET /api/dispatch?map=GITHUB&format=markdown · human article /a/oip-system-github
capability leaf GET /api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown · human article /a/oip-capability-github-list-issues
act POST /api/dispatch with owner auth or a scoped capability URL. Public docs are open; mutating action is token-bounded.
token explain GET /api/dispatch?explain=1&share=TOKEN
receipt GET /api/dispatch?receipt=inv_ID&share=TOKEN · replay with POST /api/dispatch {"replay":"inv_ID"}
ledger provenance · sources · voxels · live ledger
Loading more articles…