Is Console MCP server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highRemote endpoint did not respond — Streamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx</center> </body> </html>
How Console compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 67/100
- higher than 25% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
1 high
- Code scan38 source files scanned25/25
- Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx</center> </body> </html> 0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableStreamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx</center> </body> </html>
Overall 67/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON