Provenance-aware span recall: a zero-setup context-broker MCP for coding and document agents.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"pasr-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# PASR **Provenance-Aware Span Recall** — a zero-setup context broker your coding agent calls as an MCP tool. It hands the model the *few* lines that answer the question, each with a `file:line` and the reason it was picked — and tells the agent when it asked the wrong tool. [](https://pypi.org/project/pasr-mcp/) [](https://pypi.org/project/pasr-mcp/) [](https://github.com/Apheironn/pasr/actions/workflows/ci.yml) [](LICENSE) <p align="center"><img src="https://raw.githubusercontent.com/Apheironn/pasr/main/docs/assets/demo.svg" alt="pasr explain — one MCP call, 42,768 to 2,718 tokens, a receipt for every line" width="820"></p> ## The problem An agent working in a real repo has two bad options: read whole files and burn its context window on code that never mattered, or grep-and-guess and miss the file that held the answer. Either way, **you cannot see what it looked at** — no record, no line numbers, no reason. ## What PASR does ### Budgeted You set a token ceiling; PASR never returns more, and it packs whole spans — never a truncated function. If the full file set already fits, you get it back unchanged. <p align="center"><img src="https://raw.githubusercontent.com/Apheironn/pasr/main/docs/assets/concept-budgeted.svg" width="760" alt="a budget bar: 2,718 tokens kept under a 3,000-token ceiling, 282 free"></p> ### Traceable Every span carries `file:line`, a token count, its retrieval score, and *why* it was kept (`bm25`, `symbol`, `active_window`, …). A byte-stable receipt — of what was kept *and* what was dropped — lands on disk for every call. <p align="center"><img src="https://raw.githubusercontent.com/Apheironn/pasr/main/docs/assets/concept-traceable.svg" width="760" alt="anatomy of one returned span: where i…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.