Is IMAGIN.studio API Docs MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
How IMAGIN.studio API Docs compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 50% of 1,299 Productivity servers
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 1 read
Public scan report
scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it
1 medium
- Code scan18 source files scanned; 2 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 19 days ago15/15
- Maintainer identitynamespace and repository owner differ4/10
Findings (1)
- mediumGoogle API key in source (often public by design; check its restrictions)
secret.googleimagin_studio_api_docs_mcp-0.1.17/src/config.py: …= os.getenv("IMAGIN_DOCS_GCP_API_KEY", "AIza****") TELEMETRY_DRY_RUN: bool = os.getenv("…
Overall 78/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 IMAGIN.studio API Docs does
- classifier.dev docsclassifier.dev documentation as tools: list, read and search the reference, benchmark and guides.not reviewedEstablishedA
- Qiskit Documentation MCP ServerMCP server for querying and retrieving Qiskit documentation, guides, and API referencesnot reviewedGrowingA
- DocsSearch and read Empryo's documentation. Read-only, no auth, no local access.not reviewedEstablishedA