Aspicio
NPM · @ASPICIO/MCP · 2 COMPONENTS
DXF and PDF/X-4 for AI agents: structured facts, PNG renders, an interactive in-chat viewer.
Available components
Last scanned (6 hours ago)
Scores higher than 95% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to frontsail-ai/aspicio). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 30 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1303 tokens (~217/item across 6 items; 6 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 (50% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 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.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- Package version: 0.11.1 → 0.13.2 functional
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 93
- Malware scan: unverified → pass ▲ security
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 22 Nov 2026 · Analysed npm/@aspicio/mcp@0.13.2
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | frontsail-ai/aspicio |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/frontsail-ai/aspicio/.github/workflows/publish.yml@refs/tags/v0.13.2 |
| Rekor log index | 3406969023 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f1e0366d99a4637b12b5a10474a0533b56a421b182a81d0c88053bc2d4a78a5cc1fabeeaf70b891f59c9dc07a1fd73ec4df92e873c4daa81a0b980e5a |
Background: How many MCP packages publish verified provenance →
Dependencies 110 packages
| Packages resolved | 110 |
|---|---|
| Stale | 32 |
| 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 →
describe_doc Describe a drawing of any supported format ~196
Return a structured JSON summary of a drawing in any supported format (DXF or PDF), detected from its bytes rather than its name. Use this when you do not know which format you have; the reply names the format that was read. Covers the whole drawing by default, including every page of a multi-page PDF; pass `space` (a name from the reply's `spaces`) to scope it to one page or sheet.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | An http(s) URL, a local file path, or inline DXF text. A PDF is binary: pass it as a URL or a path, never inline. |
| space | string | – | Which space to work on: "Model" (a PDF's page 1, a DXF's model space) or a page/layout name as listed in a describe reply's "spaces". Describe omits it for the whole drawing; render defaults to the f… |
| Name | Type | Req | Description |
|---|---|---|---|
| bounds | – | yes | World-space extents, null for an empty drawing |
| entityCount | integer | yes | – |
| entityTypes | object | yes | Top-level entities per DXF type |
| format | string | yes | Which format was read ("dxf", "pdf") |
| layers | array | yes | – |
| segmentCount | integer | yes | – |
| size | – | yes | Bounding-box size in drawing units, null when empty |
| space | string|null | yes | Which space this summary is scoped to, or null when it covers the whole drawing (bounds/size then describe spaces[0], the space render returns) |
| spaces | array | yes | Every space in the drawing (a PDF's pages, a DXF's model space and layouts), model space first. These do not sum to entityCount: a DXF sheet's viewports re-show model geometry, so an entity can be dr… |
| texts | array | yes | Unique TEXT/MTEXT strings, blocks included |
| units | string | yes | Drawing-unit label (e.g. "mm"), "" when unitless |
| unsupported | object | yes | Per-kind counts of what was skipped |
No examples provided.
describe_dxf Describe a DXF drawing ~232
Return a structured JSON summary of a DXF drawing — units, bounding box, layers (with the color actually drawn), per-type entity counts, and any skipped/unsupported types. Use this to answer structural questions (what layers exist, how many parts, what size, is it to scale) without rendering an image. For a PDF use describe_pdf; if you do not know the format, use describe_doc. Covers the whole drawing by default, including every page of a multi-page PDF; pass `space` (a name from the reply's `spaces`) to scope it to one page or sheet.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | An http(s) URL, a local file path, or inline DXF text. A PDF is binary: pass it as a URL or a path, never inline. |
| space | string | – | Which space to work on: "Model" (a PDF's page 1, a DXF's model space) or a page/layout name as listed in a describe reply's "spaces". Describe omits it for the whole drawing; render defaults to the f… |
| Name | Type | Req | Description |
|---|---|---|---|
| bounds | – | yes | World-space extents, null for an empty drawing |
| entityCount | integer | yes | – |
| entityTypes | object | yes | Top-level entities per DXF type |
| format | string | yes | Which format was read ("dxf", "pdf") |
| layers | array | yes | – |
| segmentCount | integer | yes | – |
| size | – | yes | Bounding-box size in drawing units, null when empty |
| space | string|null | yes | Which space this summary is scoped to, or null when it covers the whole drawing (bounds/size then describe spaces[0], the space render returns) |
| spaces | array | yes | Every space in the drawing (a PDF's pages, a DXF's model space and layouts), model space first. These do not sum to entityCount: a DXF sheet's viewports re-show model geometry, so an entity can be dr… |
| texts | array | yes | Unique TEXT/MTEXT strings, blocks included |
| units | string | yes | Drawing-unit label (e.g. "mm"), "" when unitless |
| unsupported | object | yes | Per-kind counts of what was skipped |
No examples provided.
describe_pdf Describe a PDF drawing ~223
Return a structured JSON summary of a PDF drawing — units (points), bounding box, layers, per-type entity counts, the text it contains, and what was skipped (images, shadings, transparency). Use this for structural questions about a PDF without rendering it. For a DXF use describe_dxf; if you do not know the format, use describe_doc. Covers the whole drawing by default, including every page of a multi-page PDF; pass `space` (a name from the reply's `spaces`) to scope it to one page or sheet.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | An http(s) URL, a local file path, or inline DXF text. A PDF is binary: pass it as a URL or a path, never inline. |
| space | string | – | Which space to work on: "Model" (a PDF's page 1, a DXF's model space) or a page/layout name as listed in a describe reply's "spaces". Describe omits it for the whole drawing; render defaults to the f… |
| Name | Type | Req | Description |
|---|---|---|---|
| bounds | – | yes | World-space extents, null for an empty drawing |
| entityCount | integer | yes | – |
| entityTypes | object | yes | Top-level entities per DXF type |
| format | string | yes | Which format was read ("dxf", "pdf") |
| layers | array | yes | – |
| segmentCount | integer | yes | – |
| size | – | yes | Bounding-box size in drawing units, null when empty |
| space | string|null | yes | Which space this summary is scoped to, or null when it covers the whole drawing (bounds/size then describe spaces[0], the space render returns) |
| spaces | array | yes | Every space in the drawing (a PDF's pages, a DXF's model space and layouts), model space first. These do not sum to entityCount: a DXF sheet's viewports re-show model geometry, so an entity can be dr… |
| texts | array | yes | Unique TEXT/MTEXT strings, blocks included |
| units | string | yes | Drawing-unit label (e.g. "mm"), "" when unitless |
| unsupported | object | yes | Per-kind counts of what was skipped |
No examples provided.
render_doc Render a drawing of any supported format ~197
Render a drawing in any supported format (DXF or PDF) to a PNG you can look at, detected from its bytes rather than its name. Use this when you do not know which format you have. Renders the first page/sheet by default; pass `space` (a name from a describe reply's `spaces`) to render another one.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | An http(s) URL, a local file path, or inline DXF text. A PDF is binary: pass it as a URL or a path, never inline. |
| space | string | – | Which space to work on: "Model" (a PDF's page 1, a DXF's model space) or a page/layout name as listed in a describe reply's "spaces". Describe omits it for the whole drawing; render defaults to the f… |
| width | integer | – | PNG width in pixels (default 1200) |
No output schema declared.
No examples provided.
render_dxf Render a DXF to an image ~230
Render a DXF drawing to a PNG image you can look at. Use this to answer visual questions (what does it look like, where is a feature, does it look right) — it returns an image, not text. For structural facts, prefer describe_dxf. For a PDF use render_pdf; if you do not know the format, use render_doc. Renders the first page/sheet by default; pass `space` (a name from a describe reply's `spaces`) to render another one.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | An http(s) URL, a local file path, or inline DXF text. A PDF is binary: pass it as a URL or a path, never inline. |
| space | string | – | Which space to work on: "Model" (a PDF's page 1, a DXF's model space) or a page/layout name as listed in a describe reply's "spaces". Describe omits it for the whole drawing; render defaults to the f… |
| width | integer | – | PNG width in pixels (default 1200) |
No output schema declared.
No examples provided.
render_pdf Render a PDF to an image ~225
Render a PDF drawing's vector content to a PNG you can look at. Images, shadings, and transparency are not drawn — they are reported by describe_pdf — so this shows line work and text, not a page facsimile. For a DXF use render_dxf; if you do not know the format, use render_doc. Renders the first page/sheet by default; pass `space` (a name from a describe reply's `spaces`) to render another one.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | An http(s) URL, a local file path, or inline DXF text. A PDF is binary: pass it as a URL or a path, never inline. |
| space | string | – | Which space to work on: "Model" (a PDF's page 1, a DXF's model space) or a page/layout name as listed in a describe reply's "spaces". Describe omits it for the whole drawing; render defaults to the f… |
| width | integer | – | PNG width in pixels (default 1200) |
No output schema declared.
No examples provided.
How do I install the Aspicio MCP server?
Aspicio runs locally as an npm package, launched with npx -y @aspicio/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @aspicio/mcp
claude mcp add frontsail-ai-aspicio -- npx -y @aspicio/mcp
What is the Aspicio MCP server?
Aspicio is an MCP server listed in the public MCP registry as io.github.frontsail-ai/aspicio. DXF and PDF/X-4 for AI agents: structured facts, PNG renders, an interactive in-chat viewer. This page covers its npm package (@aspicio/mcp).
Is the Aspicio MCP server safe to use?
Aspicio scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. 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 Aspicio MCP server expose?
Aspicio exposes 6 tools: describe_dxf, render_dxf, describe_pdf, render_pdf, describe_doc, render_doc. Their descriptions and schemas cost roughly 1,303 tokens of context every time the server is loaded.
Is the Aspicio MCP server still maintained?
Aspicio is still listed as active in the MCP registry. We last reached this channel on 22 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 Aspicio MCP server under?
Aspicio declares the MIT 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 Aspicio MCP server?
VerifyMCP ran 16 checks on Aspicio, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.