Is NDP — Music Rights & Track Identification 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 — HTTP 523
How NDP — Music Rights & Track Identification compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 66/100
- higher than 23% of 48,255 servers
- Uptime
- 39%
- of our recent checks; the typical remote server answers 100%
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
1 high
- Code scan11 source files scanned25/25
- Live reliabilityremote unreachable: HTTP 5230/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 7 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableHTTP 523
Overall 66/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
NDP — Music Rights & Track Identification reviews, tools and install