Capitol Ledger
PYPI · CAPITOL-LEDGER-MCP
Read-only House stock disclosures and synthetic portfolio research. Approved pilot key required.
Available components
Last scanned (5 hours ago)
Scores higher than 72% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to joalbrecht/capitol-ledger-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 264 tokens (~88/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Analysed pypi/capitol-ledger-mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | joalbrecht/capitol-ledger-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/joalbrecht/capitol-ledger-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 3420252302 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:b093cd321b1b470b938227f6e9346b601c9202b045800b237c0e03c88d615154 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_portfolio ~66
Get a saved synthetic disclosure ledger's opening/closing allocations and audit metadata. Defaults to latest saved completed period, of any cadence. Pin report_id for reproducibility. This is not actual member holdings or the executable strategy portfolio.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| report_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_portfolio_changes ~54
Get purchases, sales, and weight changes for a saved report period; inspect coverage warnings. Pass the portfolio result's report_id to use exactly the same period.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| report_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_disclosures ~99
Search House disclosures; dates use filing availability. Return source links and amount ranges. Default window is 30 days. Maximum limit is 100. Reuse returned as_of when paging. Timestamps must include a UTC offset; side is purchase, sale, or exchange.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| available_after | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| side | – | – | – |
| ticker | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Capitol Ledger MCP server?
Capitol Ledger runs locally as a PyPI package, launched with uvx capitol-ledger-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · capitol-ledger-mcp
claude mcp add joalbrecht-capitol-ledger-mcp -- uvx capitol-ledger-mcp
What is the Capitol Ledger MCP server?
Capitol Ledger is an MCP server listed in the public MCP registry as io.github.joalbrecht/capitol-ledger-mcp. Read-only House stock disclosures and synthetic portfolio research. Approved pilot key required. This page covers its PyPI package (capitol-ledger-mcp).
Is the Capitol Ledger MCP server safe to use?
Capitol Ledger scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Capitol Ledger MCP server expose?
Capitol Ledger exposes 3 tools: search_disclosures, get_portfolio, get_portfolio_changes. Their descriptions and schemas cost roughly 219 tokens of context every time the server is loaded.
Is the Capitol Ledger MCP server still maintained?
Capitol Ledger is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Capitol Ledger MCP server under?
Capitol Ledger declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.