MCP.Market

Is deadends.dev MCP server safe?

Probably. Read the findings first.

C65/100grade C

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 bgcolor="white"> <center><h1>405 Not Allowed</h1></center> </body> </html>

How deadends.dev compares

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

Safety score
65/100
higher than 20% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%

Public scan report

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

1 high1 medium
  • Code scan1500 source files scanned20/25
  • Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> </body> </html>0/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (2)

  • highRemote endpoint did not respondreliability.unreachable

    Streamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> </body> </html>

  • mediumeval / new Function usedexec.eval
    deadends_dev-0.9.0/data/canons/data/json-trailing-comma-parse-error/json-parser-any.json: …": "" }, { "action": "Use eval() or Function() to parse JSON with trail…
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

deadends.dev reviews, tools and install