get_research_file
shallowio.github.valuein/mcp-sec-edgar · Verify this server
Fetch the Auditable Research File behind one of the caller's own agent runs — the complete evidence chain an examiner asks for: the originating prompt, every tool the agent called in order, every `fact_id` it cited, every human approval, and which models were used. Assembled from the immutable audit ledger written as the run executed; nothing here is reconstructed or inferred. Name the subject EITHER way, and pass exactly one: `report_id` (a report you wrote or found — from `create_report`, `list_my_reports` or `search_reports`) or `run_id` (from `list_agent_runs`). Naming a REPORT is the richer call: it resolves the run behind that report AND adds two sections a run's ledger cannot carry — `human_review` (each figure a HUMAN verified, corrected, rejected or sourced externally, with who and when) and `sources` (the SEC filing, form, period and filed date behind each cited fact_id). It also echoes the resolved `run_id`. A run-keyed call omits both, because a run may produce several reports and 'the report for this run' has no honest answer; empty or absent there means NOT RESOLVED, never 'no sources'. `format: "pdf"` returns the SAME assembled file as a branded compliance PDF instead of inline JSON — a 15-minute presigned download URL (`url` + `filename`) for the human-facing artifact (cover with the completeness verdict, evidence chain table, provenance with clickable sec.gov links). The PDF is rendered fresh on every call — never cached — because an in-flight run's ledger can gain entries, and a stale 'complete' verdict is exactly the lie this document exists to prevent. ⚠️ ALWAYS READ `completeness` FIRST AND REPORT IT. `completeness.complete` is computed from the ledger, and `completeness.gaps` names every hole found — an irreversible action taken with no named approver, a state-changing action that cited no fact_id, an unrecorded model, a failed step. If you present this run as evidence, present the gaps too; a chain with holes that is quoted as if whole is the one thing this artifact exists to prevent. ⚠️ `found: false` IS NOT A FINDING ABOUT THE WORK. It is returned (not as an error) for an unknown id, an id belonging to another customer, and a report with no run on record — deliberately indistinguishable, so no caller can probe which. It means we hold no audit trail under that id. It does NOT mean the report is unaudited, unverified, or that the id does not exist, and it must never be reported that way. Tier: sp500+ (sample rejected).
1 trials · measured 8 days ago
get_research_file scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.valuein/mcp-sec-edgar, measured 25 Aug 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Category
- Finance & compliance
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-08-25 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/b8608218-05a7-4d6a-b8a3-39a604520005)