# Aspicio (remote · aspicio-api.frontsail.app)

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

- Trust score: 77/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `aspicio-api.frontsail.app`: 77/100 (this document), [markdown](https://verifymcp.io/servers/frontsail-ai-aspicio/aspicio-api.md), [page](https://verifymcp.io/servers/frontsail-ai-aspicio/aspicio-api)
- npm · `@aspicio/mcp`: 70/100, [markdown](https://verifymcp.io/servers/frontsail-ai-aspicio/aspicio-mcp.md), [page](https://verifymcp.io/servers/frontsail-ai-aspicio/aspicio-mcp)

## Channel facts

- Endpoint: `https://aspicio-api.frontsail.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.12.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (63% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

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

### Hermes

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

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 77, +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.

### 2026-08-02 (score 76, 0)

- [functional] Server version: 0.11.1 → 0.12.0

### 2026-08-01 (score 76, +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.

### 2026-07-31 (score 75, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 72, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 73, +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.

### 2026-07-28 (score 72, +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.

### 2026-07-27 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (8)

### `describe_dxf` (~202 tokens)

Describe a DXF drawing

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 parameters:

- `source` (string, required): 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 @…

Output parameters:

- `bounds`: World-space extents, null for an empty drawing
- `entityCount` (integer)
- `entityTypes` (object): Top-level entities per DXF type
- `format` (string): Which format was read ("dxf", "pdf")
- `layers` (array)
- `segmentCount` (integer)
- `size`: Bounding-box size in drawing units, null when empty
- `texts` (array): Unique TEXT/MTEXT strings, blocks included
- `units` (string): Drawing-unit label (e.g. "mm"), "" when unitless
- `unsupported` (object): Per-kind counts of what was skipped

### `render_dxf` (~254 tokens)

Render a DXF to an image

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 parameters:

- `source` (string, required): 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)

### `describe_pdf` (~193 tokens)

Describe a PDF drawing

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 parameters:

- `source` (string, required): 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 @…

Output parameters:

- `bounds`: World-space extents, null for an empty drawing
- `entityCount` (integer)
- `entityTypes` (object): Top-level entities per DXF type
- `format` (string): Which format was read ("dxf", "pdf")
- `layers` (array)
- `segmentCount` (integer)
- `size`: Bounding-box size in drawing units, null when empty
- `texts` (array): Unique TEXT/MTEXT strings, blocks included
- `units` (string): Drawing-unit label (e.g. "mm"), "" when unitless
- `unsupported` (object): Per-kind counts of what was skipped

### `render_pdf` (~249 tokens)

Render a PDF to an image

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 parameters:

- `source` (string, required): 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)

### `describe_doc` (~166 tokens)

Describe a drawing of any supported format

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 parameters:

- `source` (string, required): 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 @…

Output parameters:

- `bounds`: World-space extents, null for an empty drawing
- `entityCount` (integer)
- `entityTypes` (object): Top-level entities per DXF type
- `format` (string): Which format was read ("dxf", "pdf")
- `layers` (array)
- `segmentCount` (integer)
- `size`: Bounding-box size in drawing units, null when empty
- `texts` (array): Unique TEXT/MTEXT strings, blocks included
- `units` (string): Drawing-unit label (e.g. "mm"), "" when unitless
- `unsupported` (object): Per-kind counts of what was skipped

### `render_doc` (~221 tokens)

Render a drawing of any supported format

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 parameters:

- `source` (string, required): 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)

### `view_dxf` (~281 tokens)

Open a drawing in the interactive viewer

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 parameters:

- `allow_file_open` (boolean): Show open-file controls in the viewer (default false: viewer is locked to this drawing)
- `source` (string, required): 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 @…

Output parameters:

- `bounds`: World-space extents, null for an empty drawing
- `entityCount` (integer)
- `entityTypes` (object): Top-level entities per DXF type
- `format` (string): Which format was read ("dxf", "pdf")
- `layers` (array)
- `segmentCount` (integer)
- `size`: Bounding-box size in drawing units, null when empty
- `texts` (array): Unique TEXT/MTEXT strings, blocks included
- `units` (string): Drawing-unit label (e.g. "mm"), "" when unitless
- `unsupported` (object): Per-kind counts of what was skipped

### `load_dxf_for_viewer` (~84 tokens)

Load a DXF for the viewer widget

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

Input parameters:

- `length` (integer): Byte length of the requested range
- `offset` (integer): Byte offset of the requested range
- `source` (string, required): http(s) URL of the drawing (same guards as the other tools)

Output parameters:

- `byteLength` (integer): Total size of the whole file
- `bytesBase64` (string): The requested bytes, base64
- `offset` (integer): Byte offset this slice starts at

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/frontsail-ai-aspicio/aspicio-api#diagnostics

## Score history

- 2026-08-03: 77
- 2026-08-02: 76
- 2026-08-01: 76
- 2026-07-31: 75
- 2026-07-30: 72
- 2026-07-29: 73
- 2026-07-28: 72
- 2026-07-27: 71
- 2026-07-26: 71

## Links

- Remote endpoint: https://aspicio-api.frontsail.app/mcp
- Repository: https://github.com/frontsail-ai/aspicio
- Website: https://aspicio.frontsail.app/
- Changelog RSS feed: https://verifymcp.io/servers/frontsail-ai-aspicio/aspicio-api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/frontsail-ai-aspicio/aspicio-api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/frontsail-ai-aspicio/aspicio-api