Orrery
MCPB · ORRERY-0.12.2.MCPB · 2 COMPONENTS
Architecture diagrams with official AWS, Azure, GCP and Kubernetes icons, to SVG, PNG and draw.io
Available components
Last scanned (8 hours ago)
Scores higher than 78% of MCPB servers
Category Design and Media
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1808 tokens (~164/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
- Supports UI / widget rendering.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 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- Stability: unverified → 0.10 ▲ functional
- 21 Oct 26 41
First indexed and scored.
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 mcpb/https://github.com/Sagargupta16/orrery/releases/download/v0.12.2/orrery-0.12.2.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
describe Describe a diagram ~193
Lay the spec out and tell what the picture shows in plain text: the title, each group and the nodes in it, each node's place in reading order (row from the top, then from the left) and its edges with their labels, and the numbered steps. Use it to check the drawing says what you meant without looking at an image, or as alt text. format json returns the same as data. A spec with errors returns its diagnostics instead.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Default: text. |
| name | string | – | File name stem for outputs: lowercase letters, digits and -. Default: the spec file's name, else diagram. |
| spec | string | – | The diagram spec as YAML (or JSON) text. Pass this or spec_path, not both. |
| spec_path | string | – | Absolute path of a spec file on this machine (stdio only). Its folder resolves relative icons: paths. |
No output schema declared.
No examples provided.
drawio_link Open in diagrams.net ~169
A link that opens the diagram in diagrams.net, loaded and editable. Nothing is uploaded: the draw.io file travels in the link's fragment, which the browser never sends to a server.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | File name stem for outputs: lowercase letters, digits and -. Default: the spec file's name, else diagram. |
| skin | string | – | classic (vendor deck look) or stage (dark product look). Default: the spec's skin. |
| spec | string | – | The diagram spec as YAML (or JSON) text. Pass this or spec_path, not both. |
| spec_path | string | – | Absolute path of a spec file on this machine (stdio only). Its folder resolves relative icons: paths. |
| theme | string | – | Default: the spec's theme. |
No output schema declared.
No examples provided.
get_authoring_guide Authoring guide ~67
Read this before writing a spec. topic diagram (default) returns the orrery skill (fast path, authoring rules, outputs) and the full spec reference; topic review returns the review loop and the patch ops try_patches takes.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | – |
No output schema declared.
No examples provided.
get_template Get a template ~52
One bundled template's spec YAML (names from list_templates; starter is the general one). Edit it and pass it to validate, render or review as spec.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A name from list_templates. |
No output schema declared.
No examples provided.
icons_search Search icons ~116
Find icon ids for a spec's icon: field across the official AWS, Azure, Google Cloud, Kubernetes, GitHub and IBM packs, 5,500 tech logos and the generic symbol sets, ranked best first. Returns JSON: id, name, category, type.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 15. |
| pack | string | – | Only this pack. |
| type | string | – | Only this kind of icon. |
| words | string | yes | What to draw, for example 'load balancer' or 'redis'. |
No output schema declared.
No examples provided.
list_templates List templates ~53
The bundled reference diagrams (AWS, Azure, Google Cloud, Kubernetes, C4, system design, flowcharts, BPMN, state machines, journeys), each with its title. Start from the closest one with get_template.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
render Render a diagram ~313
Render a spec to SVG, PNG, draw.io, editable draw.io SVG, a React TSX component or a standalone HTML page. Nothing renders while the spec has errors (see the diagnostics). With out_dir (stdio only) the files are written there and their paths returned; otherwise the result carries a JSON receipt, then each output in order: PNGs as images, the others as text.
| Name | Type | Req | Description |
|---|---|---|---|
| animate | string | – | SVG motion: packets, flow, relay or none. Default: the skin's (packets for classic, relay for stage). PNG is always still. |
| formats | array | – | Default: svg and png. |
| name | string | – | File name stem for outputs: lowercase letters, digits and -. Default: the spec file's name, else diagram. |
| out_dir | string | – | Absolute folder to write the files to (stdio only). Existing files are replaced. |
| scale | number | – | PNG pixels per diagram unit. Default 3 with out_dir, 2 inline. |
| skin | string | – | classic (vendor deck look) or stage (dark product look). Default: the spec's skin. |
| spec | string | – | The diagram spec as YAML (or JSON) text. Pass this or spec_path, not both. |
| spec_path | string | – | Absolute path of a spec file on this machine (stdio only). Its folder resolves relative icons: paths. |
| theme | string | – | both renders a light and a dark file. Default: the spec's theme. |
No output schema declared.
No examples provided.
review Review a diagram ~237
Measure the diagram at the width readers see it (a README column is 880 px): six scored dimensions (conventions, layout, grid, flow, overlap, quality), hard counts, findings with evidence and spec fixes, and pass (no blocker or major and score >= 85). Returns the report JSON and the PNG exactly as the reader sees it. A failing review is a normal result: fix the spec, or try fixes with try_patches.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | File name stem for outputs: lowercase letters, digits and -. Default: the spec file's name, else diagram. |
| skin | string | – | classic (vendor deck look) or stage (dark product look). Default: the spec's skin. |
| spec | string | – | The diagram spec as YAML (or JSON) text. Pass this or spec_path, not both. |
| spec_path | string | – | Absolute path of a spec file on this machine (stdio only). Its folder resolves relative icons: paths. |
| theme | string | – | Default: the spec's theme. |
| width | integer | – | Display width in CSS px. Default 880. |
No output schema declared.
No examples provided.
try_patches Try spec patches ~297
Review each candidate (a list of patch ops) on its own copy of the spec and keep only those that raise the score without raising any hard count or adding a blocker or major finding. Ops: {op: set, path, value}, {op: unset, path}, {op: add, path, value}, {op: move, path, after|before}, {op: edge, match: a spec edge line or null to append, value: the new line or null to remove}; paths are dotted, for example nodes.db.note. Returns each candidate's score and verdict, then the best patched spec text when one was kept.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | Candidate fixes, each a list of patch ops applied in order. |
| name | string | – | File name stem for outputs: lowercase letters, digits and -. Default: the spec file's name, else diagram. |
| skin | string | – | classic (vendor deck look) or stage (dark product look). Default: the spec's skin. |
| spec | string | – | The diagram spec as YAML (or JSON) text. Pass this or spec_path, not both. |
| spec_path | string | – | Absolute path of a spec file on this machine (stdio only). Its folder resolves relative icons: paths. |
| theme | string | – | Default: the spec's theme. |
| width | integer | – | Display width in CSS px. Default 880. |
No output schema declared.
No examples provided.
validate Validate a spec ~140
Check a spec without rendering: parse errors, unknown icons (with the closest ids), bad references and layout warnings, each with a code, a message and concrete fixes. Returns JSON with ok, the counts, the diagnostics and the diagram's size.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | File name stem for outputs: lowercase letters, digits and -. Default: the spec file's name, else diagram. |
| spec | string | – | The diagram spec as YAML (or JSON) text. Pass this or spec_path, not both. |
| spec_path | string | – | Absolute path of a spec file on this machine (stdio only). Its folder resolves relative icons: paths. |
No output schema declared.
No examples provided.
How do I install the Orrery MCP server?
Orrery ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, bbc4e4e69112ee934cfeb39d4880426eef055b9e0b0f9269d092782f060695ed; the commands to do that are on this page. If it does not match, do not open it.
mcpb · orrery-0.12.2.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
bbc4e4e69112ee934cfeb39d4880426eef055b9e0b0f9269d092782f060695ed
macOS / Linux
echo "bbc4e4e69112ee934cfeb39d4880426eef055b9e0b0f9269d092782f060695ed orrery-0.12.2.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\orrery-0.12.2.mcpb).Hash -eq "bbc4e4e69112ee934cfeb39d4880426eef055b9e0b0f9269d092782f060695ed"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Orrery MCP server?
Orrery is an MCP server listed in the public MCP registry as io.github.Sagargupta16/orrery. Architecture diagrams with official AWS, Azure, GCP and Kubernetes icons, to SVG, PNG and draw.io. This page covers its MCPB bundle (https://github.com/Sagargupta16/orrery/releases/download/v0.12.2/orrery-0.12.2.mcpb).
Is the Orrery MCP server safe to use?
Orrery scores 48 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 Orrery MCP server expose?
Orrery exposes 10 tools: get_authoring_guide, validate, render, review, describe, and 5 more. Their descriptions and schemas cost roughly 1,637 tokens of context every time the server is loaded.
What licence is the Orrery MCP server under?
Orrery declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.