Aspicio

REMOTE · ASPICIO-API.FRONTSAIL.APP · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · aspicio-api.frontsail.app 77 npm · @aspicio/mcp 70

+6 this week 77 77 Trust /100

Trust breakdown (6 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 →

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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability78

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1774 tokens (~197/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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Supports UI / widget rendering.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · aspicio-api.frontsail.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http frontsail-ai-aspicio https://aspicio-api.frontsail.app/mcp

# ~/.codex/config.toml

[mcp_servers.frontsail-ai-aspicio]
url = "https://aspicio-api.frontsail.app/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "frontsail-ai-aspicio": {
      "type": "remote",
      "url": "https://aspicio-api.frontsail.app/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add frontsail-ai-aspicio --url https://aspicio-api.frontsail.app/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  frontsail-ai-aspicio:
    url: "https://aspicio-api.frontsail.app/mcp"

// mcp.json

{
  "mcpServers": {
    "frontsail-ai-aspicio": {
      "type": "http",
      "url": "https://aspicio-api.frontsail.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

3 Aug 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.
2 Aug 26 0
- Server version: 0.11.1 → 0.12.0 functional
1 Aug 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.
31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 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
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 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

Show 7 earlier entries Hide earlier entries

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 3 Aug 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 Jul 2026	19 Oct 2026	RSA 2048	SHA256-RSA	54e46597990e514273aa5f6824385758d0a
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

DNSSEC insecure

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

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
app.	present	23684	8	Verified
frontsail.app.	absent			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

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 · ~1,650 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.

Tool Tokens

describe_doc Describe a drawing of any supported format ~166

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

Input Output Examples

Name	Type	Req	Description
source	string	yes	A 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 @…

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
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 ~202

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

Input Output Examples

Name	Type	Req	Description
source	string	yes	A 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 @…

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
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 ~193

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

Input Output Examples

Name	Type	Req	Description
source	string	yes	A 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 @…

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

load_dxf_for_viewer Load a DXF for the viewer widget ~84

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

Input Output Examples

Name	Type	Req	Description
length	integer	—	Byte length of the requested range
offset	integer	—	Byte offset of the requested range
source	string	yes	http(s) URL of the drawing (same guards as the other tools)

Name	Type	Req	Description
byteLength	integer	yes	Total size of the whole file
bytesBase64	string	yes	The requested bytes, base64
offset	integer	yes	Byte offset this slice starts at

No examples provided.

render_doc Render a drawing of any supported format ~221

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

Input Output Examples

Name	Type	Req	Description
source	string	yes	A 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 @…
width	integer	—	PNG width in pixels (default 1200)

No output schema declared.

No examples provided.

render_dxf Render a DXF to an image ~254

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

Input Output Examples

Name	Type	Req	Description
source	string	yes	A 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 @…
width	integer	—	PNG width in pixels (default 1200)

No output schema declared.

No examples provided.

render_pdf Render a PDF to an image ~249

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

Input Output Examples

Name	Type	Req	Description
source	string	yes	A 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 @…
width	integer	—	PNG width in pixels (default 1200)

No output schema declared.

No examples provided.

view_dxf Open a drawing in the interactive viewer ~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).

Input Output Examples

Name	Type	Req	Description
allow_file_open	boolean	—	Show open-file controls in the viewer (default false: viewer is locked to this drawing)
source	string	yes	A 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 @…

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

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	71
27 Jul	71
28 Jul	72
29 Jul	73
30 Jul	72
31 Jul	75
1 Aug	76
2 Aug	76
3 Aug	77