io.github.CloudCorpRecords/publishorder
NPM · @RENETURCIOS/PUBLISHORDER · 2 COMPONENTS
Monorepo publish order from the dependency graph: levels, changed-set plans, and cycle detection.
Available components
Last scanned (6 hours ago)
Scores higher than 37% of npm servers
Category Developer Tools
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
- 30 of 92 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 105 tokens (~105/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 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "plan_publish_order" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 54
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 5 Nov 2026 · Analysed npm/@reneturcios/publishorder@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 | 30 |
| 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 →
plan_publish_order ~105
Plan a monorepo publish order from the dependency graph: a deterministic topological order and depth levels for all packages, or for a changed set plus everything that transitively depends on it, reporting the exact cycle when the graph cannot be ordered.
| Name | Type | Req | Description |
|---|---|---|---|
| changed | array | – | Names of changed packages; when given, the plan covers exactly these plus everything that transitively depends on them (optional) |
| packages | array | yes | Packages in the monorepo (at least one) |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/publishorder MCP server?
io.github.CloudCorpRecords/publishorder runs locally as an npm package, launched with npx -y @reneturcios/publishorder. 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/publishorder
claude mcp add cloudcorprecords-publishorder -- npx -y @reneturcios/publishorder
What is the io.github.CloudCorpRecords/publishorder MCP server?
io.github.CloudCorpRecords/publishorder is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/publishorder. Monorepo publish order from the dependency graph: levels, changed-set plans, and cycle detection. This page covers its npm package (@reneturcios/publishorder).
Is the io.github.CloudCorpRecords/publishorder MCP server safe to use?
io.github.CloudCorpRecords/publishorder scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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/publishorder MCP server expose?
io.github.CloudCorpRecords/publishorder exposes 1 tool: plan_publish_order. Their descriptions and schemas cost roughly 105 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/publishorder MCP server still maintained?
io.github.CloudCorpRecords/publishorder is still listed as active in the MCP registry. We last reached this channel on 5 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/publishorder MCP server under?
io.github.CloudCorpRecords/publishorder declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.