io.github.CloudCorpRecords/peerconflict

io.github.CloudCorpRecords/peerconflict

Explains peer-dependency conflicts as a graph and suggests the least-change resolution.

View repository →

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "peerconflict": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/peerconflict@0.1.0"
      ]
    }
  }
}

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
0.1.0
Registry
active
Published
11/2/2026

More Developer Tools servers

Browse all Developer Tools →

io.github.CloudCorpRecords/perpwatch

CloudCorpRecords

Cross-exchange crypto perps microstructure feed: funding, liquidations, footprint, big trades.

Developer ToolsAdded 1 week ago

io.github.CloudCorpRecords/pgcloud

CloudCorpRecords

Neon Postgres projects, branches, SQL, and migrations from your MCP client.

Developer ToolsAdded 1 week ago

io.github.CloudCorpRecords/pkgverdict

CloudCorpRecords

Pre-install verdicts for npm packages: GO, RISKY, FAKE, or MISSING. Built for humans and AI agents.

Developer ToolsAdded 2 weeks ago

io.github.CloudCorpRecords/planboard

CloudCorpRecords

Beck agent plan board: workspaces, documents, epics, tasks, decisions and progress over REST.

Developer ToolsAdded 1 week ago

io.github.CloudCorpRecords/policyrecall

CloudCorpRecords

Policy-verified recall and calibration for tool calls via signed operational memory.

Developer ToolsAdded 1 week ago

io.github.CloudCorpRecords/porefind

CloudCorpRecords

Search lab-filtration products by specification, with prices and lead times.

Developer ToolsAdded 6 days ago

Add the badge to your site

Show visitors that io.github.CloudCorpRecords/peerconflict is listed here — it’s also the link we check for a free listing.

io.github.CloudCorpRecords/peerconflict — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-cloudcorprecords-peerconflict?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="io.github.CloudCorpRecords/peerconflict — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![io.github.CloudCorpRecords/peerconflict — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-cloudcorprecords-peerconflict?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.