Periphery Code Audit MCP server

by zyntx-lab·io.github.zyntx-lab/periphery-mcp-server·v1.0.0·2 stars

Swift code analysis with Periphery - detect unused code and improve code quality

C63/100grade C

What users say

No reviews yet

Safety scan

C63/100

Adoption

New

2 stars

Reviews

Nobody has reviewed Periphery Code Audit yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings

–Code scanpackage could not be scannedn/a
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 313 days ago4/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Overall 63/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

The registry entry has no remote endpoint or installable package.

Is Periphery Code Audit MCP server safe?: With care: it is graded C, so read the findings first (63/100). Read the Periphery Code Audit safety report
Does Periphery Code Audit need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Periphery Code Audit maintained?: The last commit was 347 days ago (2025-11-22). The latest release is v1.0.0.
How does Periphery Code Audit compare with other MCP servers?: safety score 63/100 (higher than 18% of 48,255 servers); github stars 2 (more than 75% of 28,688 servers). Full comparison.