miscsubjects.com
Object Invocation Protocol · protocol specification

OIP and MCP Protocol Specification

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

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

Introduction

Object Invocation Protocol (OIP) is a protocol standard. Model Context Protocol (MCP) is a protocol standard. OIP enables agents to invoke directory objects on miscsubjects.com. MCP establishes a session between a model and a server.

Model Context Protocol (MCP)

Model Context Protocol (MCP) is a protocol standard. MCP establishes a session between a model and a server. A session is a continuous, active connection between a model and a server. A server exposes tools, resources, and prompts over a session. A model utilizes exposed tools, resources, and prompts. A tool is a callable function. A resource is accessible data or an external system. A prompt is an input instruction.

Object Invocation Protocol (OIP)

Object Invocation Protocol (OIP) is a protocol standard. OIP enables any agent to invoke a directory object. A capability is a directory object. Any agent that opens a Uniform Resource Locator (URL) invokes and verifies.

Invocation

An agent invokes a directory object by sending data to /api/dispatch. /api/dispatch is an Application Programming Interface (API) endpoint. An API is a set of rules for software program communication. An agent invokes an object using a POST request with a JavaScript Object Notation (JSON) body to /api/dispatch. JSON is a data interchange format. The POST request body contains a key field and a body field. The key field identifies the directory object. The body field transmits invocation data to the directory object. An agent invokes an object using a GET request to /api/dispatch?invoke=KEY&body=.... The invoke parameter identifies the directory object. The body parameter transmits invocation data to the directory object.

Ledger and Receipts

Every invocation appends to the ledger. The ledger is an append-only record of all invocations. An invocation returns a receipt. A receipt proves an invocation occurred. A receipt is accessible at /api/dispatch?receipt=inv_ID. The inv_ID is a unique identifier for a specific invocation.

Replay and Repair

The ledger enables invocation replay. Invocation replay re-executes a recorded invocation. The ledger enables invocation repair. Invocation repair corrects a past invocation based on its ledger entry.

OIP and MCP Comparison

OIP operates without a persistent session. MCP establishes a persistent session between a model and a server. OIP invokes specific directory objects on miscsubjects.com. MCP provides a model with a context of tools, resources, and prompts exposed by a server.

Machine-Readable Specifications

MCP Object Specification

An MCP object specifies: server: The URL for session establishment. tools: A collection of callable functions. resources: Accessible data or external systems. input_schema: The required input format for a tool call. call: The procedure for a tool call. result: The expected output format from a tool call.

OIP Object Specification

An OIP object specifies: article: Content accessible at /a/<slug>. A slug is a unique article identifier. directory_row: A capability is a directory object. receipt: Proof of invocation accessible at /api/dispatch?receipt=inv_ID. ledger: The append-only record of all invocations. replay: Re-execution of a recorded invocation. repair: Correction of a past invocation based on its ledger entry.

miscsubjects.com Routes

/api/dispatch: An Application Programming Interface (API) endpoint. This endpoint invokes directory objects via POST or GET requests. /api/dispatch?receipt=inv_ID: This URL provides a receipt for a specific invocation. The inv_ID is the unique identifier for the invocation. * /a/<slug>: This URL accesses an article. The <slug> is a unique article identifier.

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 01:46 · model @cf/meta/llama-3.3-70b-instruct-fp8-fast · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 6/10

- gaps named: In-depth explanation of Model Context Protocol (MCP); Object Invocation Protocol (OIP) architecture; Directory rows and dispatch mechanism

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

- gaps named: Model Context Protocol (MCP) in-depth explanation; Object Invocation Protocol (OIP) architecture; Directory rows and dispatch mechanism

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.

2
revision
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 and MCP Protocol Specification. 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 GitHub?subsidiary conceptoip-github
oip-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:01 · 0 tok · virtual-oip
verify chain →
Live ledger · 50 payloads · 20 turns
recent activity · inspect
delivery.delivered blooio · 2026-07-03 03:31
delivery.delivered blooio · 2026-07-03 03:31
delivery.delivered blooio · 2026-07-03 03:31
delivery.delivered blooio · 2026-07-03 03:31
PROTOCOL_RUN dispatch · 2026-07-03 03:31 · t_scx7zj51
PROTOCOL_RUN dispatch · 2026-07-03 03:31 · t_scx7zj51
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-mcp · GET /api/articles/oip-mcp · GET /api/articles/oip-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…