IMAGIN.studio API Docs
PYPI · IMAGIN-STUDIO-API-DOCS-MCP · 2 COMPONENTS · SCANNED SEP 20
Semantic search over IMAGIN.studio API documentation — CDN, API, integration guides, and more.
Available components
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 Security99
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 63 of 64 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 63 of 64 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 10 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
{
"mcpServers": {
"imaginstudio-api-docs-mcp": {
"command": "uvx",
"args": [
"imagin-studio-api-docs-mcp"
]
}
}
} {
"servers": {
"imaginstudio-api-docs-mcp": {
"command": "uvx",
"args": [
"imagin-studio-api-docs-mcp"
]
}
}
} codex mcp add imaginstudio-api-docs-mcp -- uvx imagin-studio-api-docs-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"imaginstudio-api-docs-mcp": {
"type": "local",
"command": [
"uvx",
"imagin-studio-api-docs-mcp"
],
"enabled": true
}
}
} openclaw mcp add imaginstudio-api-docs-mcp --command uvx --arg imagin-studio-api-docs-mcp
mcp_servers:
imaginstudio-api-docs-mcp:
command: "uvx"
args: ["imagin-studio-api-docs-mcp"] {
"McpServers": {
"imaginstudio-api-docs-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"imagin-studio-api-docs-mcp"
]
}
}
} assistant mcp add imaginstudio-api-docs-mcp -t stdio -c uvx -a imagin-studio-api-docs-mcp
{
"mcpServers": {
"imaginstudio-api-docs-mcp": {
"command": "uvx",
"args": [
"imagin-studio-api-docs-mcp"
]
}
}
} 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed pypi/imagin-studio-api-docs-mcp@0.1.17
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 →
Dependencies 63 packages
| Packages resolved | 63 |
|---|---|
| Stale | 11 |
| No linked repository | 1 |
| 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.
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).
Is the IMAGIN.studio API Docs MCP server safe to use?
IMAGIN.studio API Docs scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.