What it does
eodrecord lets an agent read the published end-of-day record of a rules-based index model that tracks SPY and QQQ. The record shows what the model held and how it was allocated at each close, with a 90-day delay on the free view. The package holds no model data of its own. It answers the tool list locally and forwards each tool call upstream, returning the results unchanged. It also provides the fixed definitions of every published field, a ledger fingerprint for checking that the record was not rewritten, and a pointer to the current published state.
An agent would reach for it to review past allocation states, to look up what a field or signal means, or to check a record against its RFC 3161 and OpenTimestamps receipts. The four tools are get_public_record, which takes an optional days value from 1 to 260 (default 30); get_definitions; get_verification; and get_current_state. All four are read-only and do not purchase, subscribe or create keys.
Running it means the client opens a streamable HTTP session to the upstream endpoint on the first call and reuses it for the life of the process. The endpoint defaults to the vendor's address and can be overridden. An optional API key can be supplied, in which case it is sent as a Bearer header on every upstream request. Failures return as error results whose text begins with "eodrecord error:". The package can also run as a stdio MCP server, a command-line tool taking JSON arguments, or a Docker container, and its test suite runs against a stubbed upstream rather than the live network.
Limitations and requirements
The free public record is delayed by 90 days, and get_public_record returns at most 260 sessions. The current published state is available only to Core members, who receive it the evening it is published; without a key, get_current_state returns access information and the delayed record instead. The optional API key is for the caller's own use. The README labels the endpoint override, the key environment variable and the error text as reconstructions by this rebuild rather than details of the original package. The package is MIT licensed.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/eodrecord
Read the published end-of-day state of a rules-based SPY and QQQ index model.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it