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.

Aspicio

REMOTE · ASPICIO-API.FRONTSAIL.APP · 2 COMPONENTS

DXF and PDF/X-4 for AI agents: structured facts, PNG renders, an interactive in-chat viewer.

0 this week 81 Trust /100

Last scanned (7 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability38
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2333 tokens (~259/item across 9 items; 8 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 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 (63% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 23 Oct 26 0
    • Server version: 0.13.0 → 0.13.2 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 22 Nov 2026 · Probed https://aspicio-api.frontsail.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aspicio-api.frontsail.app CN=YR1,O=Let's Encrypt,C=US 21 Nov 2026 19 Feb 2027 RSA 2048 SHA256-RSA 6c36f8bdeeb862d4c1b644b360a08f906c5
SANs: aspicio-api.frontsail.app
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aspicio-api.frontsail.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
frontsail.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aspicio-api.frontsail.app/mcp Verified 200
http (plaintext) http://aspicio-api.frontsail.app/mcp HTTPS enforced 308 https://aspicio-api.frontsail.app/mcp
MCP tools · 8 exposed · ~2,223 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
describe_doc ~266

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.

NameTypeReqDescription
sourcestringyesA publicly reachable http(s) URL, or inline DXF text. A PDF is binary, so it must be a URL — inline PDF bytes are refused. (This is a hosted server — local file paths are not available; use the npx @…
spacestring–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…
NameTypeReqDescription
bounds–yesWorld-space extents, null for an empty drawing
entityCountintegeryes–
entityTypesobjectyesTop-level entities per DXF type
formatstringyesWhich format was read ("dxf", "pdf")
layersarrayyes–
segmentCountintegeryes–
size–yesBounding-box size in drawing units, null when empty
spacestring|nullyesWhich space this summary is scoped to, or null when it covers the whole drawing (bounds/size then describe spaces[0], the space render returns)
spacesarrayyesEvery 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…
textsarrayyesUnique TEXT/MTEXT strings, blocks included
unitsstringyesDrawing-unit label (e.g. "mm"), "" when unitless
unsupportedobjectyesPer-kind counts of what was skipped

No examples provided.

describe_dxf ~302

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.

NameTypeReqDescription
sourcestringyesA publicly reachable http(s) URL, or inline DXF text. A PDF is binary, so it must be a URL — inline PDF bytes are refused. (This is a hosted server — local file paths are not available; use the npx @…
spacestring–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…
NameTypeReqDescription
bounds–yesWorld-space extents, null for an empty drawing
entityCountintegeryes–
entityTypesobjectyesTop-level entities per DXF type
formatstringyesWhich format was read ("dxf", "pdf")
layersarrayyes–
segmentCountintegeryes–
size–yesBounding-box size in drawing units, null when empty
spacestring|nullyesWhich space this summary is scoped to, or null when it covers the whole drawing (bounds/size then describe spaces[0], the space render returns)
spacesarrayyesEvery 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…
textsarrayyesUnique TEXT/MTEXT strings, blocks included
unitsstringyesDrawing-unit label (e.g. "mm"), "" when unitless
unsupportedobjectyesPer-kind counts of what was skipped

No examples provided.

describe_pdf ~293

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.

NameTypeReqDescription
sourcestringyesA publicly reachable http(s) URL, or inline DXF text. A PDF is binary, so it must be a URL — inline PDF bytes are refused. (This is a hosted server — local file paths are not available; use the npx @…
spacestring–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…
NameTypeReqDescription
bounds–yesWorld-space extents, null for an empty drawing
entityCountintegeryes–
entityTypesobjectyesTop-level entities per DXF type
formatstringyesWhich format was read ("dxf", "pdf")
layersarrayyes–
segmentCountintegeryes–
size–yesBounding-box size in drawing units, null when empty
spacestring|nullyesWhich space this summary is scoped to, or null when it covers the whole drawing (bounds/size then describe spaces[0], the space render returns)
spacesarrayyesEvery 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…
textsarrayyesUnique TEXT/MTEXT strings, blocks included
unitsstringyesDrawing-unit label (e.g. "mm"), "" when unitless
unsupportedobjectyesPer-kind counts of what was skipped

No examples provided.

load_dxf_for_viewer ~84

Internal: returns DXF bytes (base64) for the in-chat viewer. Called by the widget, not the model.

NameTypeReqDescription
lengthinteger–Byte length of the requested range
offsetinteger–Byte offset of the requested range
sourcestringyeshttp(s) URL of the drawing (same guards as the other tools)
NameTypeReqDescription
byteLengthintegeryesTotal size of the whole file
bytesBase64stringyesThe requested bytes, base64
offsetintegeryesByte offset this slice starts at

No examples provided.

render_doc ~312

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.

NameTypeReqDescription
sourcestringyesA publicly reachable http(s) URL, or inline DXF text. A PDF is binary, so it must be a URL — inline PDF bytes are refused. (This is a hosted server — local file paths are not available; use the npx @…
spacestring–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…
widthinteger–PNG width in pixels (default 1200)

No output schema declared.

No examples provided.

render_dxf ~345

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.

NameTypeReqDescription
sourcestringyesA publicly reachable http(s) URL, or inline DXF text. A PDF is binary, so it must be a URL — inline PDF bytes are refused. (This is a hosted server — local file paths are not available; use the npx @…
spacestring–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…
widthinteger–PNG width in pixels (default 1200)

No output schema declared.

No examples provided.

render_pdf ~340

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.

NameTypeReqDescription
sourcestringyesA publicly reachable http(s) URL, or inline DXF text. A PDF is binary, so it must be a URL — inline PDF bytes are refused. (This is a hosted server — local file paths are not available; use the npx @…
spacestring–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…
widthinteger–PNG width in pixels (default 1200)

No output schema declared.

No examples provided.

view_dxf ~281

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).

NameTypeReqDescription
allow_file_openboolean–Show open-file controls in the viewer (default false: viewer is locked to this drawing)
sourcestringyesA publicly reachable http(s) URL, or inline DXF text. A PDF is binary, so it must be a URL — inline PDF bytes are refused. (This is a hosted server — local file paths are not available; use the npx @…
NameTypeReqDescription
bounds–yesWorld-space extents, null for an empty drawing
entityCountintegeryes–
entityTypesobjectyesTop-level entities per DXF type
formatstringyesWhich format was read ("dxf", "pdf")
layersarrayyes–
segmentCountintegeryes–
size–yesBounding-box size in drawing units, null when empty
spacestring|nullyesWhich space this summary is scoped to, or null when it covers the whole drawing (bounds/size then describe spaces[0], the space render returns)
spacesarrayyesEvery 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…
textsarrayyesUnique TEXT/MTEXT strings, blocks included
unitsstringyesDrawing-unit label (e.g. "mm"), "" when unitless
unsupportedobjectyesPer-kind counts of what was skipped

No examples provided.

Install

How do I install the Aspicio MCP server?

Aspicio is a hosted endpoint at https://aspicio-api.frontsail.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · aspicio-api.frontsail.app

# add to Claude Code
claude mcp add --transport http frontsail-ai-aspicio 'https://aspicio-api.frontsail.app/mcp'
Common questions

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 hosted endpoint (https://aspicio-api.frontsail.app/mcp).

Is the Aspicio MCP server safe to use?

Aspicio scores 81 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 Aspicio MCP server expose?

Aspicio exposes 8 tools: describe_dxf, render_dxf, describe_pdf, render_pdf, describe_doc, and 3 more. Their descriptions and schemas cost roughly 2,223 tokens of context every time the server is loaded.

Does the Aspicio MCP server require authentication?

No. We connected to Aspicio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 did VerifyMCP test on the Aspicio MCP server?

VerifyMCP ran 14 checks on Aspicio, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.