Buildability
Buildability tools verify that a paper's implementation can be reproduced from source. Use the MCP tools to fetch reproducibility requirements and submit build attempts with verified telemetry.
Overview
The buildability surface connects paper proof to execution. It provides precomputed reproducibility requirements for papers in the corpus and accepts authenticated build-attempt telemetry to track which papers have been independently verified.
Read-mostly
Public tools are search, receipt, and reproducibility requirements only. No live web scraping.
Precomputed
Buildability reads deterministic fixtures and proof-wave ledgers, not runtime lookups.
Signed when available
Receipts report unsigned, not_verified, or verified status as stored. Unsigned receipts block completion.
Authenticated telemetry
Build attempt submission requires a developer key, caps descriptions, redacts logs, and deduplicates retries.
MCP tools
Two MCP tools cover the buildability workflow: one for reading requirements and one for submitting results.
get_repro_requirements
Returns the reproducibility requirements for a paper: dependencies, build steps, expected outputs, and environment constraints. This is a read-only tool that requires no authentication for public papers.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_repro_requirements",
"arguments": {
"paper_ref": "2401.12345v1"
}
}
}Paper reference format
2401.12345v1). The same identifier works across Signal Canvas, buildability, and Build Loop routes.submit_build_attempt
Reports a build attempt result. Requires authentication. The server validates the payload, redacts sensitive data from logs, and deduplicates retries by idempotency key.
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "submit_build_attempt",
"arguments": {
"paper_ref": "2401.12345v1",
"status": "succeeded",
"description": "Built from source and ran the smoke test.",
"repository_url": "https://github.com/acme/worlddb",
"external_run_url": "https://ci.acme.dev/runs/123",
"idempotency_key": "build-attempt-2026-04-25-worlddb"
}
}
}Authentication required
Authorization: Bearer s2s_YOUR_KEY. Unauthenticated submissions are rejected.Code examples
Fetch reproducibility requirements via REST before starting a build.
curl -H "Authorization: Bearer s2s_YOUR_KEY" \
"https://sciencetostartup.com/api/buildability/2401.12345v1"Verification flow
The typical buildability workflow follows three steps:
- 1Call get_repro_requirements with the paper reference to fetch dependencies and build steps.
- 2Execute the build locally or in CI using the returned requirements.
- 3Submit the result via submit_build_attempt with the status, repository URL, and commit SHA.
Canonical identifiers