Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/eodrecord

NPM · @RENETURCIOS/EODRECORD · 2 COMPONENTS

Read the published end-of-day state of a rules-based SPY and QQQ index model.

+5 this week 75 Trust /100

Last scanned (12 hours ago)

Scores higher than 51% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 190 tokens (~47/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 55

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@reneturcios/eodrecord@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~190 tokens

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 →

Tool Tokens
get_current_state ~45

The current published state is delivered to Tideline Core members the evening it is published. Without a Tideline key this returns how Core access works and where the delayed public record is.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_definitions ~36

Fixed definitions of every published field (market regime, allocation states, extension, distance to next signal, signals) and the publication schedule.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_public_record ~76

Tideline's published end-of-day model states and allocation changes, shown with a 90-day delay (the data of tideline.jbpscapital.com/record). Read-only; published states only, nothing re-computed.

NameTypeReqDescription
daysinteger–Number of most recent sessions in the delayed record to return (default 30).

No output schema declared.

No examples provided.

get_verification ~33

Latest public ledger fingerprint with its RFC 3161 and OpenTimestamps receipts, and how to verify the record independently.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/eodrecord MCP server?

io.github.CloudCorpRecords/eodrecord runs locally as an npm package, launched with npx -y @reneturcios/eodrecord mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/eodrecord

# add to Claude Code
claude mcp add cloudcorprecords-eodrecord -- npx -y @reneturcios/eodrecord mcp
Common questions

What is the io.github.CloudCorpRecords/eodrecord MCP server?

io.github.CloudCorpRecords/eodrecord is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/eodrecord. Read the published end-of-day state of a rules-based SPY and QQQ index model. This page covers its npm package (@reneturcios/eodrecord).

Is the io.github.CloudCorpRecords/eodrecord MCP server safe to use?

io.github.CloudCorpRecords/eodrecord scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/eodrecord MCP server expose?

io.github.CloudCorpRecords/eodrecord exposes 4 tools: get_public_record, get_definitions, get_verification, get_current_state. Their descriptions and schemas cost roughly 190 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/eodrecord MCP server still maintained?

io.github.CloudCorpRecords/eodrecord is still listed as active in the MCP registry. We last reached this channel on 21 November 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 io.github.CloudCorpRecords/eodrecord MCP server under?

io.github.CloudCorpRecords/eodrecord declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.CloudCorpRecords/eodrecord MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/eodrecord, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.