Is Sourced MCP server safe?
No. It is blocked at the gateway.
Blocked at the gateway. A critical finding or a dead endpoint.
What to know before installing
- highRemote endpoint did not respond — TypeError: fetch failed
How Sourced compares
Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 28/100
- higher than 4% of 3,443 Web search servers
- Uptime
- 0%
- of our recent checks; the typical remote Web search server answers 100%
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
1 high
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote unreachable: TypeError: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 240 days ago4/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
Overall 28/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Safer options for the same job
KodyYour agents' cloud for individuals and teams. Search, execute, packages, jobs, and credentials.not reviewedEstablishedA