miscsubjects.com
Object Invocation Protocol · protocol specification

OIP vs MCP

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

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-mcp-comparison
**Machine bundle:** https://miscsubjects.com/api/articles/oip-mcp-comparison/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.

What is OIP vs MCP

OIP stands for Object Invocation Protocol. MCP stands for Model Context Protocol: an open standard where an AI model connects to an MCP server over a session and the server exposes tools, resources, and prompts the model can call. OIP and MCP are two different protocols.

Why this build cares about OIP vs MCP

This build cares about OIP vs MCP because they serve different purposes. OIP uses plain URLs and receipts with no persistent session. MCP uses a persistent session.

How to see or use it live with curl

You can use curl to invoke an object on miscsubjects.com by sending a POST request to /api/dispatch with a JSON body containing the key and body of the object. You can also use curl to get a receipt for an invocation by sending a GET request to /api/dispatch with the receipt ID as a query parameter.

How it relates to MCP

OIP differs from MCP in that OIP does not require a persistent session. Any model that can open a URL can act with OIP. MCP requires a persistent session and is used for more complex interactions between the model and the server.

Where the proof lives

The proof of an invocation lives in the append-only ledger at /api/dispatch?receipt=inv_ID. You can use curl to retrieve the receipt for an invocation and verify that it was successful.

Latest clarity reviews (live)

Fresh models are sent this article's bundle and asked two separate questions: how clear is the machine JSON, and how clear is the English body. Scores are 0 to 10. The full history is in the append-only ledger.

  • 2026-07-03 02:35 · model @cf/meta/llama-3.3-70b-instruct-fp8-fast · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 7/10

- gaps named: Detailed explanation of MCP; Comparison of OIP and MCP in different scenarios

How the loop self-corrects: a failing review queues a model revision of this article (a new append-only version). A missing concept named by a reviewer queues a brand-new machine-written article, which then enters the same review cycle.

1
version
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 vs MCP. 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-mcp-comparison · 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:06 · 0 tok · virtual-oip
verify chain →
Live ledger · 15 payloads · 9 turns
recent activity · inspect
PROTOCOL_RUN dispatch · 2026-07-03 02:35 · t_46k58r3l
PROTOCOL_RUN dispatch · 2026-07-03 02:35 · t_46k58r3l
OIP_ARTICLE_REVIEW oip-review · HTTP 200 · 2026-07-03 02:35 · t_ff6hyrkv
OIP_ARTICLE_REVIEW oip-review · HTTP 200 · 2026-07-03 02:23 · t_zhnrexlh
PROTOCOL_RUN dispatch · 2026-07-03 00:11 · t_ngxxkvoi
PROTOCOL_RUN dispatch · 2026-07-03 00:11 · t_ngxxkvoi
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-mcp-comparison · GET /api/articles/oip-mcp-comparison · GET /api/articles/oip-mcp-comparison/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…