OpenDataRoomWhat is an MCP request ledger?
An MCP request ledger records calls received by a Model Context Protocol server. OpenDataRoom records search text, requested files and excerpt ranges, timestamps and whether requests were allowed or refused.
How does a request become a record?
- A recipient’s compatible AI app calls a tool such as search_files or read_file.
- The service checks the connection’s access and expiry.
- The ledger records the request and its outcome before an authorised response is released.
Repeated unauthenticated attempts may be throttled before an individual ledger entry is created. Those refusals use short-lived security rate counters; authorised requests still require their audit record.
Search and read are separate events
A search may return matching excerpts or no matches. A read requests a specific document excerpt. The recorded search text is the argument sent by the AI app; it may differ from the person’s original question. Some apps make requests automatically.
Who can review private request details?
In the private-wallet build, the pack owner unlocks encrypted request details in their browser. Company administration alone does not grant access to another owner’s private ledger. Subscriber retention applies, with pagination and export of the displayed page. Earlier hosted-drop records have a different privacy boundary.
Trace the source and response
Records include the request ID, authorised connection, time, request arguments, source-file and extracted-text hashes, and excerpt ranges where applicable. Ranges use UTF-16 code units. A read response also records a hash of the returned text. The updated hosted service and local connector retain response hashes and metadata, without retaining the prepared response body. Historical receipts may still contain response bodies; unlocked exports include them when available. Protect downloaded copies.
The technical outcome “response_prepared” means the server prepared a response. It does not prove delivery, that the AI relied on it, or that anyone read it. Keep that distinction when using records in an audit.
What if someone needs more information?
A search miss is not proof of a missing fact. Automatic gap detection and no-match notifications are retired. A recipient can explicitly submit a request, comment or note to the pack owner from their connected AI. These messages are separate from ordinary document requests and private chats. The owner sees them in Recipient inbox for up to 90 days, or until deleted sooner. No agent or automatic research is started. How recipient messages work.
What does a record establish?
It establishes server activity, not that a person read the answer or intended to act on it. Connections are tied to email-verified recipients or signed-in members; this does not prove personal action. Full AI conversations are not supplied to this service.
Is the ledger tamper-proof?
The application refuses updates to recorded requests, but the ledger is not an independently immutable or tamper-proof archive.
Preparing useful source files
For a fundraising pack, keep TAM, SAM and SOM calculations with their source assumptions and founder experience with dated biographies. For a fund update, label reporting periods and distinguish realised from unrealised figures. The service shares your materials; the recipient’s AI performs the analysis.
Investor guidance from Y Combinator and Sequoia highlights market size and team background as useful source material.