io.github.docdiagram/docdiagram-mcp
PYPI · DOCDIAGRAM-MCP · SCANNED SEP 20
DocDiagram MCP server - embedded diagrams in MDX docs
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 78 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1915 tokens (~100/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "embedded_diagram_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 19 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 io.github.docdiagram/docdiagram-mcp server?
io.github.docdiagram/docdiagram-mcp runs locally as a PyPI package, launched with uvx docdiagram-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 · docdiagram-mcp
claude mcp add docdiagram-docdiagram-mcp -- uvx docdiagram-mcp
{
"mcpServers": {
"docdiagram-docdiagram-mcp": {
"command": "uvx",
"args": [
"docdiagram-mcp"
]
}
}
} {
"servers": {
"docdiagram-docdiagram-mcp": {
"command": "uvx",
"args": [
"docdiagram-mcp"
]
}
}
} codex mcp add docdiagram-docdiagram-mcp -- uvx docdiagram-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"docdiagram-docdiagram-mcp": {
"type": "local",
"command": [
"uvx",
"docdiagram-mcp"
],
"enabled": true
}
}
} openclaw mcp add docdiagram-docdiagram-mcp --command uvx --arg docdiagram-mcp
mcp_servers:
docdiagram-docdiagram-mcp:
command: "uvx"
args: ["docdiagram-mcp"] {
"McpServers": {
"docdiagram-docdiagram-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"docdiagram-mcp"
]
}
}
} assistant mcp add docdiagram-docdiagram-mcp -t stdio -c uvx -a docdiagram-mcp
{
"mcpServers": {
"docdiagram-docdiagram-mcp": {
"command": "uvx",
"args": [
"docdiagram-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 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −2
- Stability: pass → 0.83 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −2
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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/docdiagram-mcp@0.3.1
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 | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
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 →
diagram_create ~237
Generate a standalone diagram from a prompt. No MDX file or repo binding required: this is the zero-setup path for a customer who has only run /docdiagram:auth. Creates a chat in the account's default project and polls briefly for the render. NON-BLOCKING on a slow render: if the render is not done within a few seconds it returns a pending handle (``render_status`` is the inflight value, ``image_urls`` empty) that you resolve later with ``diagram_get(chat_slug)`` rather than raising. Does NOT download bytes; the caller fetches the short-lived signed URLs (valid ~5 min) WITHOUT credentials. Prefer the ``light`` theme (``default_theme``). Output is watermarked while the account is on the free tier (``is_free_tier``). Returns {chat_slug, chat_url, render_status, default_theme, image_urls, is_free_tier}, or, if a generation is already in flight on the resolved chat, {status: "generation_in_flight", chat_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
diagram_get ~188
Resolve a standalone diagram by its handle (the chat ``slug`` that ``diagram_create`` and ``diagram_list`` return). This is how you pick up a diagram that ``diagram_create`` returned as pending, and the dereference half of the deterministic-handle round-trip. Reads the correctly-resolved revision (the pinned one if pinned, else the one referenced by the last chat message, NEVER ``revisions[0]`` by position) and returns its freshly signed ``image_urls``. Returns {chat_slug, chat_url, render_status, default_theme, image_urls, pinned}, where ``pinned`` is true when the resolved revision is the pinned one. A brand-new chat with no rendered revision yet returns ``render_status: "unknown"`` with empty ``image_urls`` rather than erroring.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_slug | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
diagram_list ~143
List the caller's standalone diagrams. Defaults to the account's default project (the zero-setup project); pass ``project_id`` to scope to another. Returns {items: [{chat_slug, title, thumbnail_url, updated_at}]}, the handle paired with the human label. Show ``title`` to the user, resolve their natural-language pick to the corresponding ``chat_slug``, then call ``diagram_get``/``diagram_revise`` with that ``chat_slug``. Titles are NOT unique and are never a key; always carry the ``chat_slug`` forward.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| project_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
diagram_revise ~187
Revise an existing standalone diagram with a follow-up prompt, addressed by its handle (the chat ``slug``). Resolve a human pick to a ``chat_slug`` first (via ``diagram_list``); never re-create, which would silently duplicate. Appends a turn to the chat and polls briefly for the new render, with the same non-blocking behavior as ``diagram_create``: a slow render returns a pending handle to resolve later with ``diagram_get``. If a generation is already in flight on the chat, returns {status: "generation_in_flight", chat_slug, chat_id} as a retry signal instead of erroring. On success returns {chat_slug, chat_url, render_status, default_theme, image_urls, message_id, job_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_slug | string | yes | – |
| prompt | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
embedded_diagram_by_sidecar ~79
Look up a binding by (repo, docs_path, slot). Returns None if no live binding exists. Soft-deleted rows are excluded so a re-create after delete works without surfacing the tombstone.
| Name | Type | Req | Description |
|---|---|---|---|
| docs_path | string | yes | – |
| repo_host_id | string | yes | – |
| slot | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
embedded_diagram_create ~134
Create a new embedded diagram bound to (repo, docs_path, slot). Errors with 409 if a binding already exists (use embedded_diagram_revise). Render runs as an arq job; blocks on the status URL until terminal (30s timeout) and returns the result. Returns {docdiagram_id, binding, sidecar, mdx_reference}; does NOT inline render bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | – | – | – |
| docs_path | string | yes | – |
| prompt | string | yes | – |
| repo_host | string | yes | – |
| repo_host_id | string | yes | – |
| slot | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
embedded_diagram_delete ~43
Soft-delete a binding. Does not delete the diagram itself; the canonical revision history remains addressable via the chat.
| Name | Type | Req | Description |
|---|---|---|---|
| docdiagram_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
embedded_diagram_get ~48
Fetch a binding (and its referenced diagram metadata) by id. Returns soft-deleted rows too so the orphan view in TECH-065 works.
| Name | Type | Req | Description |
|---|---|---|---|
| docdiagram_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
embedded_diagram_list_for_repo ~67
List bindings for a repo. Cursor-paginated per TECH-062's (created_at, id) base64-JSON convention. Returns {items, next_cursor}.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
| repo_host_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
embedded_diagram_regenerate ~93
Regenerate an existing embedded diagram by re-running the last prompt. Server resolves the current revision via diagram_revision_service.resolve_current and re-invokes the LLM with the most recent user message on the bound chat. Use when the diagram drifted or you want a fresh sample without retyping the prompt. Blocks until terminal (30s).
| Name | Type | Req | Description |
|---|---|---|---|
| docdiagram_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
embedded_diagram_render_png_url ~94
Return {full_png_url, expires_at}. full_png_url is a short-lived signed render URL (TECH-069) the caller fetches WITHOUT credentials, so it works off-origin where a bearer header can't be attached. Render is compute-on-demand via arq. Binary payloads in MCP tools are awkward; a URL is the right primitive.
| Name | Type | Req | Description |
|---|---|---|---|
| docdiagram_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
embedded_diagram_render_svg ~114
Return {full_svg_url, expires_at, byte_size}. full_svg_url is a short-lived signed render URL (TECH-069) the caller fetches WITHOUT credentials, so it works off-origin where a bearer header can't be attached. Render is compute-on-demand via arq (no cache table). The full SVG is NOT inlined: large diagrams blow out the model's context and SVG XML is rarely useful for the model to read directly.
| Name | Type | Req | Description |
|---|---|---|---|
| docdiagram_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
embedded_diagram_revise ~71
Revise an existing embedded diagram via a follow-up prompt. Addressed by docdiagram_id, not by repo/docs_path/slot. Render runs as an arq job; blocks until terminal (30s timeout).
| Name | Type | Req | Description |
|---|---|---|---|
| docdiagram_id | string | yes | – |
| prompt | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
repo_get ~40
Fetch a repo row by its DocDiagram UUID. Use repo_lookup if you only have the GitHub node id.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
repo_lookup ~58
Look up a repo by GitHub node id. Scoped to the caller's account (TECH-062 UNIQUE(account_id, host, host_id)). Returns the repo row or None if not registered.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_host_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
repo_upsert ~126
Register or update a repo. Idempotent on (account_id, host, host_id). Account scoping is implicit from the bearer token. Returns {id, account_id, host, host_id, repo_full_name, default_branch, docs_tool, docs_config_path, installation_id, sidecar_mode}.
| Name | Type | Req | Description |
|---|---|---|---|
| default_branch | string | – | – |
| docs_config_path | – | – | – |
| docs_tool | string | – | – |
| installation_id | – | – | – |
| repo_full_name | string | yes | – |
| repo_host | string | yes | – |
| repo_host_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sync_get_status ~53
Poll a sync run by id. Returns {status, pr_url, pr_number, bindings_updated, error_message, last_human_commit_sha, created_at, completed_at}.
| Name | Type | Req | Description |
|---|---|---|---|
| sync_run_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sync_list ~70
List recent sync runs for a repo, newest first. Cursor-paginated per TECH-062's (created_at, id) base64-JSON convention. Returns {items, next_cursor}.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
| repo_host_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
sync_start ~70
Trigger a sync run: pushes pending revisions to the customer's repo via PR. Idempotent in-flight dedup (partial unique index on pending/running/pr_opened states). Returns {sync_run_id, status, job_id, already_in_flight}.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_host_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.docdiagram/docdiagram-mcp server?
io.github.docdiagram/docdiagram-mcp is listed in the public MCP registry as io.github.docdiagram/docdiagram-mcp. DocDiagram MCP server - embedded diagrams in MDX docs. This page covers its PyPI package (docdiagram-mcp).
Is the io.github.docdiagram/docdiagram-mcp server safe to use?
io.github.docdiagram/docdiagram-mcp scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.docdiagram/docdiagram-mcp server expose?
io.github.docdiagram/docdiagram-mcp exposes 19 tools: embedded_diagram_create, embedded_diagram_revise, embedded_diagram_regenerate, embedded_diagram_get, embedded_diagram_by_sidecar, and 14 more. Their descriptions and schemas cost roughly 1,915 tokens of context every time the server is loaded.
Is the io.github.docdiagram/docdiagram-mcp server still maintained?
io.github.docdiagram/docdiagram-mcp 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.
What licence is the io.github.docdiagram/docdiagram-mcp server under?
io.github.docdiagram/docdiagram-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.