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.JRCage/ribcage-agent-services

NPM · RIBCAGE-AGENT-SERVICES-MCP

Verification and research desk for agents: packet validation, token screens, settlement checks.

60 Trust /100

Last scanned (21 hours ago)

Scores higher than 36% 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 & Transparency32
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 396 tokens (~49/item across 8 items; 8 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 Coverage67
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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.

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.

  • 21 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Oct 26 45

    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 22 Oct 2026 · Analysed npm/ribcage-agent-services-mcp@1.0.1

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 · 8 exposed · ~396 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
create_watch ~63

Register a standing watch ($1.00/month; one free 7 days). Fires once per change with old/new/source/timestamp.

NameTypeReqDescription
cadencestring––
notifystring––
targetstringyes–
typestringyes–

No output schema declared.

No examples provided.

data_catalog ~26

Settled-data catalog: our own graded records only; venue data excluded on venue terms.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

edit_text ~57

Editing of human-facing text. Standard $5.00/1,000 words; deep $15.00/1,000 words.

NameTypeReqDescription
contactstring––
levelstring––
textstringyes–

No output schema declared.

No examples provided.

grade_log ~45

Grade a prediction log instantly: Brier score + calibration. $0.50/log up to 500; one log up to 50 free.

NameTypeReqDescription
predictionsarrayyes–

No output schema declared.

No examples provided.

research_memo ~43

Queue a scoped research memo. From $2.00; scope and price quoted before any charge.

NameTypeReqDescription
contactstring––
questionstringyes–

No output schema declared.

No examples provided.

token_screen ~42

Deep Solana token screen from public data with raw receipts. $0.10; cached repeat 15 min $0.02.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

validate_packet ~61

Queue a packet (up to 40 claims) for primary-source validation with receipts. $0.25/packet; free evaluation tier 10 calls/day.

NameTypeReqDescription
contactstring––
packetstringyes–
tierstring––

No output schema declared.

No examples provided.

verify_settlement ~59

Verify a single Kalshi/Polymarket settlement claim against the venue print. $0.05; out-of-scope free.

NameTypeReqDescription
claimed_outcomestring––
marketstringyes–
venuestringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.JRCage/ribcage-agent-services MCP server?

io.github.JRCage/ribcage-agent-services runs locally as an npm package, launched with npx -y ribcage-agent-services-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 · ribcage-agent-services-mcp

# add to Claude Code
claude mcp add jrcage-ribcage-agent-services -- npx -y ribcage-agent-services-mcp
Common questions

What is the io.github.JRCage/ribcage-agent-services MCP server?

io.github.JRCage/ribcage-agent-services is an MCP server listed in the public MCP registry as io.github.JRCage/ribcage-agent-services. Verification and research desk for agents: packet validation, token screens, settlement checks. This page covers its npm package (ribcage-agent-services-mcp).

Is the io.github.JRCage/ribcage-agent-services MCP server safe to use?

io.github.JRCage/ribcage-agent-services scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 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.JRCage/ribcage-agent-services MCP server expose?

io.github.JRCage/ribcage-agent-services exposes 8 tools: validate_packet, research_memo, token_screen, verify_settlement, edit_text, and 3 more. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.

Is the io.github.JRCage/ribcage-agent-services MCP server still maintained?

io.github.JRCage/ribcage-agent-services is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.