Is Hiring Change Intelligence 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 — TypeError: fetch failed
How Hiring Change Intelligence compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 68/100
- higher than 30% of 48,273 servers
- Uptime
- 0%
- of our recent checks; the typical remote server answers 100%
Release history: 2 versions in the registry since 2026-09-30, latest 2026-10-01, typically one every 1 day.
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
1 high
- Code scan4 source files scanned25/25
- Live reliabilityremote unreachable: TypeError: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 11 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
Overall 68/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Hiring Change Intelligence does
- Contractor Licence ChangesDid this contractor's licence change? Observed lapses and reinstatements, not a snapshot.not reviewedEstablishedA
