Search / io.github.frontsail-ai/aspicio
protogridR0· no sign-inDXF and PDF/X-4 for AI agents: structured facts, PNG renders, an interactive in-chat viewer.
v0.13.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"aspicio": {
"type": "http",
"url": "https://aspicio-api.frontsail.app/mcp"
}
}
}claude mcp add --transport http aspicio https://aspicio-api.frontsail.app/mcp[mcp_servers.aspicio]
url = "https://aspicio-api.frontsail.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aspicio": {
"type": "remote",
"url": "https://aspicio-api.frontsail.app/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"aspicio": {
"type": "http",
"url": "https://aspicio-api.frontsail.app/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=aspicio&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXNwaWNpby1hcGkuZnJvbnRzYWlsLmFwcC9tY3AifQ%3D%3D"
}{
"servers": {
"aspicio": {
"type": "http",
"url": "https://aspicio-api.frontsail.app/mcp"
}
}
}{
"mcpServers": {
"aspicio": {
"httpUrl": "https://aspicio-api.frontsail.app/mcp"
}
}
}extensions:
"aspicio":
enabled: true
name: "aspicio"
type: streamable_http
uri: "https://aspicio-api.frontsail.app/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations8 of 8 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: describe_dxf (idempotentHint); render_dxf (idempotentHint); describe_pdf (idempotentHint); …tools.token_costabout 2,775 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulnsno known advisory in 115 resolved packagesdeps.mcp_sdk_version@modelcontextprotocol/sdk 1.30.1 has 1 known advisory (GHSA-6qxp-vccf-f47h); update @modelcontextprotocol/sdk to 1.31.0 or laterdeps.resolvable@aspicio/[email protected] resolved: 115 packagesNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +website +reachable +uptime-100% ~updated-70d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
@aspicio/[email protected] npm114 dependencies, resolved · MCP SDK @modelcontextprotocol/sdk 1.30.1 · advisories checked 2026-10-19
| advisory | severity | package | fixed in |
|---|---|---|---|
| GHSA-6qxp-vccf-f47hMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server | high | @modelcontextprotocol/[email protected]MCP SDK, direct | fixed in 1.31.0 |
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://aspicio-api.frontsail.app/mcp streamable-http | none | yes | 100% | 344 ms | 2025-11-25 | 2026-10-20 |
| package | registry | version | runtime | secrets |
|---|---|---|---|---|
@aspicio/mcp | npm | 0.13.0 | npx |
describe_docread-only | 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. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. |
describe_dxfread-only | 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. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. |
describe_pdfread-only | 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. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. |
load_dxf_for_viewerread-only | Internal: returns DXF bytes (base64) for the in-chat viewer. Called by the widget, not the model. |
render_docread-only | 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. Some chat UIs do not display the returned image to the user: for URL sources the result also includes a direct image link — show it (e.g. as a markdown image) when they need to see the render. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. |
render_dxfread-only | 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. Some chat UIs do not display the returned image to the user: for URL sources the result also includes a direct image link — show it (e.g. as a markdown image) when they need to see the render. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. |
render_pdfread-only | 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. Some chat UIs do not display the returned image to the user: for URL sources the result also includes a direct image link — show it (e.g. as a markdown image) when they need to see the render. When the user wants to see or explore the drawing themselves, prefer view_dxf (interactive viewer) — if your platform gates it behind user approval, offer it and ask rather than substituting a static render. |
view_dxfread-only | Open an interactive viewer the user can pan, zoom, and toggle layers in (renders in-chat on MCP Apps-capable hosts). Reads DXF and vector PDF; for a PDF it shows line work and text rather than a page facsimile, so images, shadings, and transparency are absent by design. Use this when the user wants to see or explore the drawing themselves; for your own analysis use a describe_* tool (facts) or a render_* tool (image). The viewer shows only the drawing from this call. Delivery is handled by the widget itself: small drawings are embedded in the result and larger URL-sourced drawings are fetched by the widget through its own tool call — never re-fetch or inline the file for the viewer's sake, and don't blind-retry if the user reports an empty viewer (the viewer posts its actual status back to the conversation context). |
Schemas: list_tools.
{
"name": "io.github.frontsail-ai/aspicio",
"icons": [
{
"src": "https://aspicio.frontsail.app/favicon.svg",
"mimeType": "image/svg+xml"
}
],
"title": "Aspicio",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://aspicio-api.frontsail.app/mcp",
"type": "streamable-http"
}
],
"version": "0.13.0",
"packages": [
{
"version": "0.13.0",
"transport": {
"type": "stdio"
},
"identifier": "@aspicio/mcp",
"runtimeHint": "npx",
"registryType": "npm"
}
],
"repository": {
"url": "https://github.com/frontsail-ai/aspicio",
"source": "github"
},
"websiteUrl": "https://aspicio.frontsail.app",
"description": "DXF and PDF/X-4 for AI agents: structured facts, PNG renders, an interactive in-chat viewer."
}