Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

IMAGIN.studio API Docs

PYPI · IMAGIN-STUDIO-API-DOCS-MCP · 2 COMPONENTS

Give your AI coding assistant direct access to the IMAGIN.studio vehicle imagery API docs.

0 this week 67 Trust /100

Last scanned (18 hours ago)

Scores higher than 60% of PyPI servers

Category Code Search and Documentation

Trust breakdown (7 categories)

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 Security49
  • Malware scan not yet available for this package.Unverified
  • Known CVEs were checked across the 72 of 74 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 build step with no custom scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 72 of 74 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • 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
  • Clear OSI-approved license (Apache-2.0).Pass
  • 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 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 current MCP spec version (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.

What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 16 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 10 Nov 26 82

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed pypi/imagin-studio-api-docs-mcp@0.1.29

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 3789277694
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:b8cd3c6810d3371114df13338c929bb02cc308716cf0df84f35ad6aae41a2883

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 72 packages
Packages resolved 72
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 →

MCP tools · 1 exposed · ~164 tokens

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 →

Tool Tokens
search_docs ~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.

NameTypeReqDescription
querystringyesNatural language search query. Use specific technical terms rather than vague descriptions. Good: "CDN cache invalidation headers". Bad: "caching stuff".
top_kinteger–Number of results to return (1-20, default 5). Use 1-3 for focused lookups, 5 for general questions, 10-20 for broad research.
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

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

# add to Claude Code
claude mcp add imagin-studio-api-docs-mcp -- uvx imagin-studio-api-docs-mcp
Common questions

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.IMAGIN-studio/api-docs-mcp. Give your AI coding assistant direct access to the IMAGIN.studio vehicle imagery API docs. 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 67 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 21 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 Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the IMAGIN.studio API Docs MCP server?

VerifyMCP ran 14 checks on IMAGIN.studio API Docs, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about IMAGIN.studio API Docs: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.