io.github.zyntx-lab/periphery-mcp-server
Periphery Code Audit
Is the Periphery Code Audit MCP server down? It gave no valid answer in the probe of 2026-11-11: install failed. One failed probe is not an outage.
Swift code analysis with Periphery - detect unused code and improve code quality
install failed no valid answer since 2026-11-11 · probed 2026-11-15 · unchanged since 2026-11-11
the bundle does not match the SHA-256 in the registry entry
- Bundle
- https://github.com/zyntx-lab/periphery-mcp-server/releases/download/v1.0.0/periphery-mcp-server (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/zyntx-lab/periphery-mcp-server
- Website
- https://github.com/zyntx-lab/periphery-mcp-server
- Registry
- active, updated 2025-11-17 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- GuardMarket io.github.zma-petterzhang/guardmarket · crashed on start
- Knowledge Forest io.github.znecho9/knowledge-forest-mcp · alive
- MCP File Tools io.github.zoster81/mcp-file-tools · install failed
- Scripthold io.github.zoster81/scripthold · crashed on start
- Ghost Networks net.gh-o/ghost-mcp · crashed on start
- agent haven org.agenthaven/agent-haven · alive
- DexSQL org.lsposed/dexsql · alive
- Covenant Guard org.opencovenant/guard · crashed on start
Servers that mention audit or code.
- AI-Advisors ai.ai-advisors/mcp · needs auth
- ai.beket/audit · needs auth
- Bring Your AI ai.bringyour/bringyour · alive
- ai.cdbx/mcp-server · needs auth
- Can I Vibe? — AI coding provider status ai.canivibe/status · alive
- ai.byteask/embedded-docs · alive
- DarkFunnels ai.darkfunnels/whatsapp-sales-agent · needs auth
- DABYTE AI Visibility Index ai.dabyte/visibility-index · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package did not start as an MCP server at its probe on 2026-11-11. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.