io.github.CloudCorpRecords/claimcheck
NPM · @RENETURCIOS/CLAIMCHECK
Track stale claims and parked fixes so open-source work does not silently die.
Available components
Last scanned (23 hours ago)
Scores higher than 40% of npm servers
Category Version Control
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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- 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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 289 tokens (~96/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 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 16 Oct 26 71
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 16 Oct 2026 · Analysed npm/@reneturcios/claimcheck@0.1.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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
issue_claim_status ~76
Claim status of one GitHub issue: every claimant found in the comments, their age bucket, and whether a linked PR exists (work in flight). Call this before commenting on or claiming an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full GitHub issue URL, e.g. https://github.com/owner/repo/issues/123 |
No output schema declared.
No examples provided.
parked_branches ~92
List parked fixes on a fork: branches ahead of the upstream default branch with no open PR. Age from the last commit: PARKED_RECENT (<7d), PARKED_STALE (7-30d), PARKED_DEAD (30d+). Call this to find finished work that never shipped.
| Name | Type | Req | Description |
|---|---|---|---|
| fork | string | yes | owner/fork-repo, e.g. CloudCorpRecords/pdfcn |
No output schema declared.
No examples provided.
stale_claims ~121
Scan a repo's open issues for stale claims: comments where someone said they would take an issue but never opened a PR. Buckets are FRESH (<14d), WATCH (14-44d), STALE (45-89d, contestable), DEAD (90d+). Call this to find issues you can legitimately claim because the last claimant walked away.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | owner/repo, e.g. modelcontextprotocol/python-sdk |
| stale_days | number | – | Age in days that counts as stale (default 45) |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/claimcheck MCP server?
io.github.CloudCorpRecords/claimcheck runs locally as an npm package, launched with npx -y @reneturcios/claimcheck. 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/claimcheck
claude mcp add cloudcorprecords-claimcheck -- npx -y @reneturcios/claimcheck
What is the io.github.CloudCorpRecords/claimcheck MCP server?
io.github.CloudCorpRecords/claimcheck is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/claimcheck. Track stale claims and parked fixes so open-source work does not silently die. This page covers its npm package (@reneturcios/claimcheck).
Is the io.github.CloudCorpRecords/claimcheck MCP server safe to use?
io.github.CloudCorpRecords/claimcheck scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 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.CloudCorpRecords/claimcheck MCP server expose?
io.github.CloudCorpRecords/claimcheck exposes 3 tools: stale_claims, parked_branches, issue_claim_status. Their descriptions and schemas cost roughly 289 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/claimcheck MCP server still maintained?
io.github.CloudCorpRecords/claimcheck is still listed as active in the MCP registry. We last reached this channel on 16 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 io.github.CloudCorpRecords/claimcheck MCP server under?
io.github.CloudCorpRecords/claimcheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.