io.github.CloudCorpRecords/approvepath
OCI · GHCR.IO/CLOUDCORPRECORDS/APPROVEPATH · 2 COMPONENTS
Map who must approve a PR: CODEOWNERS rules plus who actually reviews these files.
Available components
Last scanned (22 hours ago)
Scores higher than 47% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 100 tokens (~100/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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.
- 4 Nov 26 0
- Provenance: fail → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 40
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 4 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/approvepath@0.1.0
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | oci |
| Reason | Check deferred |
Background: How many MCP packages publish verified provenance →
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 →
map_approvals ~100
Map the approval path for a pull request: apply CODEOWNERS rules to each changed file (last matching rule wins) and report who actually reviews those files, from supplied review history.
| Name | Type | Req | Description |
|---|---|---|---|
| changed_files | array | yes | Paths of the files the PR changes |
| codeowners | array | yes | CODEOWNERS rules in file order: {pattern, owners} |
| reviews | array | – | Past review activity (optional): {reviewer, files} |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/approvepath MCP server?
io.github.CloudCorpRecords/approvepath runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/approvepath:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/approvepath
claude mcp add cloudcorprecords-approvepath -- docker run --rm -i ghcr.io/cloudcorprecords/approvepath:0.1.0
What is the io.github.CloudCorpRecords/approvepath MCP server?
io.github.CloudCorpRecords/approvepath is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/approvepath. Map who must approve a PR: CODEOWNERS rules plus who actually reviews these files. This page covers its container image (ghcr.io/cloudcorprecords/approvepath).
Is the io.github.CloudCorpRecords/approvepath MCP server safe to use?
io.github.CloudCorpRecords/approvepath scores 41 out of 100 on VerifyMCP. 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/approvepath MCP server expose?
io.github.CloudCorpRecords/approvepath exposes 1 tool: map_approvals. Their descriptions and schemas cost roughly 100 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/approvepath MCP server still maintained?
io.github.CloudCorpRecords/approvepath is still listed as active in the MCP registry. We last reached this channel on 4 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/approvepath MCP server under?
io.github.CloudCorpRecords/approvepath declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.