# io.github.CloudCorpRecords/claimcheck (npm · @reneturcios/claimcheck)

Track stale claims and parked fixes so open-source work does not silently die.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- npm · `@reneturcios/claimcheck`: 71/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-claimcheck/reneturcios-claimcheck.md), [page](https://verifymcp.io/servers/cloudcorprecords-claimcheck/reneturcios-claimcheck)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/claimcheck`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 289 tokens (~96/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add cloudcorprecords-claimcheck -- npx -y @reneturcios/claimcheck
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-claimcheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/claimcheck"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-claimcheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/claimcheck"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-claimcheck -- npx -y @reneturcios/claimcheck
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-claimcheck": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/claimcheck"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-claimcheck --command npx --arg -y --arg @reneturcios/claimcheck
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-claimcheck:
    command: "npx"
    args: ["-y", "@reneturcios/claimcheck"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-claimcheck": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/claimcheck"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-claimcheck -t stdio -c npx -a -y @reneturcios/claimcheck
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-claimcheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/claimcheck"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 71)

First indexed and scored.

## MCP tools (3)

### `stale_claims` (~121 tokens)

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.

Input parameters:

- `repo` (string, required): owner/repo, e.g. modelcontextprotocol/python-sdk
- `stale_days` (number): Age in days that counts as stale (default 45)

### `parked_branches` (~92 tokens)

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.

Input parameters:

- `fork` (string, required): owner/fork-repo, e.g. CloudCorpRecords/pdfcn

### `issue_claim_status` (~76 tokens)

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.

Input parameters:

- `url` (string, required): Full GitHub issue URL, e.g. https://github.com/owner/repo/issues/123

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-claimcheck/reneturcios-claimcheck#diagnostics

## Score history

- 2026-10-16: 71

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/claimcheck
- Socket report: https://socket.dev/npm/package/@reneturcios/claimcheck
- Repository: https://github.com/CloudCorpRecords/claimcheck
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-claimcheck/reneturcios-claimcheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-claimcheck/reneturcios-claimcheck.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-claimcheck/reneturcios-claimcheck