Publishorder runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Nov 2026.
Monorepo publish order from the dependency graph: levels, changed-set plans, and cycle detection.
Today is the operative word: we check Publishorder every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add publishorder -- npx -y @reneturcios/publishorder
{
"mcpServers": {
"publishorder": {
"command": "npx",
"args": [
"-y",
"@reneturcios/publishorder"
]
}
}
}
[mcp_servers.publishorder]
command = "npx"
args = ["-y", "@reneturcios/publishorder"]
{
"mcpServers": {
"publishorder": {
"command": "npx",
"args": [
"-y",
"@reneturcios/publishorder"
]
}
}
}
{
"servers": {
"publishorder": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/publishorder"
]
}
}
}
Internal dependency map for monorepo packages, as structured data and a Mermaid graph.
Changeset and changelog entries from PR commits, grouped by type in the repo's own convention.
Code intelligence MCP server: impact analysis, dependency graphs, dead code detection.
Architecture docs from a repo: overview, modules, API surface, routes, dependency graph, diffs.
Local dependency graph: callers, entry points and file:line evidence for what a change affects.
AI code impact analysis — dependency graphs, cascade detection, and build gates for AI agents
Search indexed code, trace dependencies, assess change impact, and recall repository memory.
MCP server that scans your repo's dependencies for security vulnerabilities based on published CVEs.
Answers built from our own checks of this server.