MARGINNOOK / DEVELOPER PREVIEW
MCP integration and evidence reads
Map HTTP operation IDs to the actual MCP tool names.
Developer preview. Hosted API is not live yet. Explore fixed synthetic samples; anonymous uploads, hosted execution and payments remain closed.
Tool names are different from HTTP IDs
| HTTP business ID | MCP name |
|---|---|
report.failures | test_failures |
data.aggregate | aggregate |
document.search | search_document |
Local Streamable HTTP endpoint: http://127.0.0.1:8000/mcp/. Public MCP access is closed. Use the official compatible SDK for protocol negotiation and structured results.
Evidence read
{"resource_id":"<normalized-text-or-result-handle>","offset":0,"length":4000}Call read_evidence. Maximum read length is 8,000 Unicode characters; follow next_offset. JSON fragments are text, not complete JSON objects. Use normalized_source_resource for document coordinates. Never insert both content and structuredContent into model context without an explicit reason.
Waiting and failures
The MCP server waits up to 22 seconds, then may return pending. Client runtime handles polling with one 180-second task deadline. Tool errors have code, category, retryable and retry_after; quota and platform capacity are separate. Finding failed tests is successful report processing.