Is Connectry Architect MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
How Connectry Architect compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 62/100
- higher than 17% of 48,255 servers
- Tools that change things
- 11%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 13 read · 2 change · 3 run or deploy
Public scan report
scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it
1 medium
- Code scan9 source files scanned20/25
- –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 192 days ago4/15
- Maintainer identitynamespace and repository owner differ4/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/data/questions/domain-2.json: …kages. The agent must find all uses of `eval()`, all `innerHTML` assignments, and all…
Overall 62/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON