IMAGIN.studio API Docs
PYPI · IMAGIN-STUDIO-API-DOCS-MCP · 2 COMPONENTS
Semantic search over IMAGIN.studio API documentation — CDN, API, integration guides, and more.
Available components
Last scanned (54 minutes ago)
Scores higher than 0% of PyPI servers
Category Code Search and Documentation
Recent critical change
CVE-2026-112398 affects this package (24 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security74
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 66 of 69 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to IMAGIN-studio/api-docs-mcp). View diagnostics → Pass
- License check failed: the license (LicenseRef-Proprietary) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 180 tokens (~180/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: pass → unverified ▼ security
- 30 Oct 26 0
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 0
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 0
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 0
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 0
- CVE-2026-112398 affects this package: high ▼ critical
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 0
- CVE-2026-96639 affects this package: high ▼ critical
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 22 Oct 26 0
- CVE-2026-112900 affects this package: high ▼ critical
- CVE-2026-112393 affects this package: high ▼ critical
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/imagin-studio-api-docs-mcp@0.1.17
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | IMAGIN-studio/api-docs-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/IMAGIN-studio/api-docs-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 1175207625 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:0cc7ce3008e953f25c6be1ccf2082af8fd44d49d2296f56f7ee0e391291c123b |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 59 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22hg-r758-rrw9 | CVE-2026-112390 | high | yes | |
| GHSA-24rc-8hj2-v98c | CVE-2026-96638 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | yes |
| GHSA-254f-3936-288h | CVE-2026-112391 | medium | yes | |
| GHSA-27h8-gf7j-v5hc | CVE-2026-112392 | high | yes | |
| GHSA-332p-7hrc-92wf | CVE-2026-112393 | critical | yes | |
| GHSA-3j72-p6qg-6xp7 | CVE-2026-96642 | high | yes | |
| GHSA-4558-3h8r-v8xp | CVE-2026-112394 | medium | yes | |
| GHSA-462x-pgg6-55fp | CVE-2026-112395 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L | yes |
| GHSA-4rm8-3hmm-39fg | CVE-2026-96641 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | yes |
| GHSA-4rr5-89j8-mwwm | CVE-2026-112396 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-58r4-6rv3-gfh8 | CVE-2026-112397 | high | yes | |
| GHSA-5x8w-8jj5-q52h | CVE-2026-112398 | critical | yes | |
| GHSA-5xm2-6676-qcp9 | CVE-2026-112399 | high | yes | |
| GHSA-654x-cwwv-5j9c | CVE-2026-114501 | medium | yes | |
| GHSA-65qm-jvmh-6pqg | CVE-2026-112400 | high | yes | |
| GHSA-74r2-7ff9-mjj2 | CVE-2026-112401 | medium | yes | |
| GHSA-78g4-xqwv-q3g8 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes | |
| GHSA-7mwm-ghpf-9vrm | CVE-2026-112402 | high | yes | |
| GHSA-8g5g-8vmr-9782 | CVE-2026-112403 | critical | yes | |
| GHSA-9v9v-9qvf-h2hj | CVE-2026-96644 | high | yes | |
| GHSA-c6hw-5grf-ff96 | CVE-2026-112404 | high | yes | |
| GHSA-cp9v-662q-vvx9 | CVE-2026-112405 | high | yes | |
| GHSA-f2g6-542v-9j58 | CVE-2026-112406 | high | yes | |
| GHSA-fc9g-5qg7-mf45 | CVE-2026-112891 | medium | yes | |
| GHSA-g4qv-2jxx-769h | CVE-2026-96643 | high | yes | |
| GHSA-g7cr-3p24-7wf7 | CVE-2026-96778 | high | yes | |
| GHSA-g842-9rc4-69pw | CVE-2026-96637 | high | yes | |
| GHSA-gg2r-wvfm-q9rx | CVE-2026-112892 | high | yes | |
| GHSA-j4m9-6w36-pw47 | CVE-2026-112893 | high | yes | |
| GHSA-jg86-v3jv-hrpm | CVE-2026-112894 | high | yes | |
| GHSA-mrfp-p49p-3hf2 | CVE-2026-96640 | high | yes | |
| GHSA-p4wg-p73j-c528 | CVE-2026-112895 | high | yes | |
| GHSA-p8hx-v2p6-rp84 | CVE-2026-96636 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | yes |
| GHSA-pchr-8j38-3x4p | CVE-2026-112896 | high | yes | |
| GHSA-q45j-58j2-45rg | CVE-2026-112897 | high | yes | |
| GHSA-rfgq-q3w2-pmv2 | CVE-2026-112898 | medium | yes | |
| GHSA-v9pv-5gc8-w2m6 | CVE-2026-96639 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-vx6w-vv9f-6gvg | CVE-2026-112899 | medium | yes | |
| GHSA-w889-685w-c8fh | CVE-2026-112900 | critical | yes | |
| GHSA-xgh8-jp6q-p5x8 | CVE-2026-112901 | medium | yes | |
| GHSA-xvh5-g6gv-559v | CVE-2026-112902 | high | yes | |
| PYSEC-2026-4326 | CVE-2026-112392 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-4327 | CVE-2026-112394 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H | yes |
| PYSEC-2026-4328 | CVE-2026-112396 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-4329 | CVE-2026-112397 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-4330 | CVE-2026-112398 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-4331 | CVE-2026-112402 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-4332 | CVE-2026-112403 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-4333 | CVE-2026-112405 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-4334 | CVE-2026-112896 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H | yes |
Showing 50 of 59 vulnerabilities.
Background: What a vulnerability scan can and cannot prove →
Dependencies 66 packages
| Packages resolved | 66 |
|---|---|
| Stale | 11 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
search_docs Search IMAGIN.studio Documentation ~164
Search the official IMAGIN.studio technical documentation, integration guides, and knowledge base. Use this tool when the user asks 'How do I...' questions, needs explanation on API concepts (CDN, referrers, caching, 360 spinner), or needs to debug integration issues. Rewrite vague queries into specific technical search terms before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural language search query. Use specific technical terms rather than vague descriptions. Good: "CDN cache invalidation headers". Bad: "caching stuff". |
| top_k | integer | – | Number of results to return (1-20, default 5). Use 1-3 for focused lookups, 5 for general questions, 10-20 for broad research. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the IMAGIN.studio API Docs MCP server?
IMAGIN.studio API Docs runs locally as a PyPI package, launched with uvx imagin-studio-api-docs-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · imagin-studio-api-docs-mcp
claude mcp add imaginstudio-api-docs-mcp -- uvx imagin-studio-api-docs-mcp
What is the IMAGIN.studio API Docs MCP server?
IMAGIN.studio API Docs is an MCP server listed in the public MCP registry as io.github.IMAGINstudio/api-docs-mcp. Semantic search over IMAGIN.studio API documentation, CDN, API, integration guides, and more. This page covers its PyPI package (imagin-studio-api-docs-mcp).
What tools does the IMAGIN.studio API Docs MCP server expose?
IMAGIN.studio API Docs exposes 1 tool: search_docs. Their descriptions and schemas cost roughly 164 tokens of context every time the server is loaded.
Is the IMAGIN.studio API Docs MCP server still maintained?
IMAGIN.studio API Docs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the IMAGIN.studio API Docs MCP server under?
IMAGIN.studio API Docs declares the LicenseRef-Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.