Is Apibase MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
What to know before installing
- highWrite-action tools reachable without authentication
How Apibase compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 84/100
- higher than 68% of 48,255 servers
- Tools that change things
- 2%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
What its tools let an agent do: 1369 read · 8 create · 54 change · 6 delete · 5 send or post
Release history: 2 versions in the registry since 2026-03-26, latest 2026-09-23, typically one every 181 days.
Public scan report
scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it
1 high
- Code scan3 source files scanned25/25
- Live reliabilityremote reachable in 1857ms20/20
- Tool poisoning1400 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 33 write-action tools with no auth3/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Overall 84/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 Apibase does
- treg.toOpenRouter for tools and data. Compare catalog providers and call them from one hosted MCP endpoint.not reviewedEstablishedA
