corpus.333.ecoCAUTION
An MCP server for an open-licensed corpus, served with verifiable provenance — sha256, DOI and OpenTimestamps with every response.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
An MCP server for an open-licensed corpus — mechanism papers, essays, institutional positions, white papers and the Letters to Miss Aquarius — served with verifiable provenance.
152 documents. 144 CC0-1.0 · 8 CC-BY-4.0. 108 carry a DOI; 152 carry an OpenTimestamps proof.
Written by `npm run build` from the index itself — see scripts/build-index.mjs.
npx @333eco/corpus
Every response carries the document's sha256, its DOI where one exists, and whether an OpenTimestamps proof is anchored beside the source. A retrieval server normally asks to be believed. This one hands over the means to check it.
Why that matters
An agent that cites a passage is in a worse position than a human who does: it cannot walk to the shelf. It takes whatever the transport delivered, and nothing about a plausible-looking response distinguishes the canonical text from a paraphrase, a truncation, or a substitution somewhere upstream.
So the check moves into the response:
"provenance": {
"sha256": "91a41c759b1e9fdac3c0da667fe32a906aef98e4edec4832c09ac27b2c7663c0",
"doi": "10.5281/zenodo.22217516",
"opentimestamps": true,
"deposited_matches_current": true,
"hostile_review": null,
"verify": {
"sha256": "printf '%s' \"$(cat )\" | shasum -a 256 # compare to provenance.sha256",
"doi": "https://doi.org/10.5281/zenodo.22217516",
"opentimestamps": "ots verify defensive-publications/zero-point-game.md.ots"
}
}The verify block is an instruction, not a promise — it tells you exactly what to run, so you do not have to trust this sentence either.
hostile_review is the date of the latest ruled review by an outside reader chosen as the one most likely to find the document wrong, whose section structure still matches the text served — or null, stated rather than omitted. It is derived from the corpus's public reviews.json (roles only, never names), and a st
bde2b2d9b9c5OBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add corpus-333-eco-worker -- npx -y [email protected]
{
"mcpServers": {
"corpus-333-eco-worker": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (7)
7 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
claim | read | The claim or topic you want to test, in your own words. |
corpus-document | read | Any document in the corpus, addressed by its slug — e.g. corpus://co-presence-gated-redemption. |
orient | read | A worked example of the discovery tools: what genres and topic categories exist, how many documents |
quote | read | Optional: the passage you intend to cite. |
slug | read | Document slug, e.g. co-presence-gated-redemption. Completable. |
verify_a_quote | read | A worked example of the verification path: fetch a document, then check the served text against the |
what_would_falsify | read | A worked example of the program tools: search the prediction register for the registered falsifier of a |
Trust audit
CAUTIONgrade B · trust 83/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (5 observation(s))
- Network
- declared (11 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (15)
if (outbound) fail(`the in-process worker made ${outbound} outbound request(s) during a handshake`, "A test run must not send a live beacon — it pushes a notification to the founder's phone.");export const beacon = (env, ctx, { event, client, country, data }) => {method: "beacon",
import { clientOf, record, missOf, resultsOf, beacon } from "./telemetry.mjs";beacon(env, ctx, { event: "corpus_error", client, country, data: { method: String(msg.method ?? ""), message: String(e.message).slice(0, 200) } });" e.g. --from ../../../TH/publications ../../../H3/publications"
import { RESOURCE_TEMPLATES, listResources, readResource, completeArgument } from "../../src/resources.mjs";import { structured } from "../../src/results.mjs";import { envelope } from "../../src/envelope.mjs";import { PROMPTS, getPrompt } from "../../src/prompts.mjs";raw = atob(String(cursor));
start = Number(atob(String(cursor)));
wrangler
dist/corpus.json
Gates applied: no_behavioural_pass, no_license.
bde2b2d9b9c5full audit observations/trust-audit/mcp-server/333eco__corpus.333.eco.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | bde2b2d9b9c5 | CAUTION | B | 83 | first audit |
Questions
What is the @333eco/corpus MCP server?
An MCP server for an open-licensed corpus, served with verifiable provenance — sha256, DOI and OpenTimestamps with every response.
What tools does @333eco/corpus expose?
7 in total: 7 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is @333eco/corpus safe to connect to an agent?
With care. The audit graded it B (83/100) and found 15 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does @333eco/corpus need?
No credential environment variables were found in its source, so it appears to need none.
How current is this page?
The grade is for one exact copy of the source (bde2b2d9b9c5), read on 2026-10-11. The repository is watched and re-audited when it changes.