io.github.frontsail-ai/aspicio

Est-ce que io.github.frontsail-ai/aspicio est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.frontsail-ai/aspicio » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• describe_doc≈ 1250 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • space · string · optionnel
    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 first space.
  • source · string · requis
    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 @aspicio/mcp local server for files on disk.)

  Exemple d'appel

  {"name": "describe_doc", "arguments": {"source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"size": "texte", "space": "texte", "texts": [], "units": "texte", "bounds": "texte", "format": "texte", "layers": [], "spaces": [], "entityCount": 1, "entityTypes": {}, "unsupported": {}, "segmentCount": 1}}

• describe_dxf≈ 1284 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • space · string · optionnel
    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 first space.
  • source · string · requis
    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 @aspicio/mcp local server for files on disk.)

  Exemple d'appel

  {"name": "describe_dxf", "arguments": {"source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"size": "texte", "space": "texte", "texts": [], "units": "texte", "bounds": "texte", "format": "texte", "layers": [], "spaces": [], "entityCount": 1, "entityTypes": {}, "unsupported": {}, "segmentCount": 1}}

• describe_pdf≈ 1273 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • space · string · optionnel
    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 first space.
  • source · string · requis
    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 @aspicio/mcp local server for files on disk.)

  Exemple d'appel

  {"name": "describe_pdf", "arguments": {"source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"size": "texte", "space": "texte", "texts": [], "units": "texte", "bounds": "texte", "format": "texte", "layers": [], "spaces": [], "entityCount": 1, "entityTypes": {}, "unsupported": {}, "segmentCount": 1}}

• load_dxf_for_viewer≈ 329 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • length · integer · optionnel
    Byte length of the requested range
  • offset · integer · optionnel
    Byte offset of the requested range
  • source · string · requis
    http(s) URL of the drawing (same guards as the other tools)

  Exemple d'appel

  {"name": "load_dxf_for_viewer", "arguments": {"source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"offset": 1, "byteLength": 1, "bytesBase64": "texte"}}

• render_doc≈ 420 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • space · string · optionnel
    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 first space.
  • width · integer · optionnel
    PNG width in pixels (default 1200)
  • source · string · requis
    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 @aspicio/mcp local server for files on disk.)

  Exemple d'appel

  {"name": "render_doc", "arguments": {"source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• render_dxf≈ 446 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • space · string · optionnel
    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 first space.
  • width · integer · optionnel
    PNG width in pixels (default 1200)
  • source · string · requis
    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 @aspicio/mcp local server for files on disk.)

  Exemple d'appel

  {"name": "render_dxf", "arguments": {"source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• render_pdf≈ 441 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • space · string · optionnel
    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 first space.
  • width · integer · optionnel
    PNG width in pixels (default 1200)
  • source · string · requis
    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 @aspicio/mcp local server for files on disk.)

  Exemple d'appel

  {"name": "render_pdf", "arguments": {"source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• view_dxf≈ 1278 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • source · string · requis
    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 @aspicio/mcp local server for files on disk.)
  • allow_file_open · boolean · optionnel
    Show open-file controls in the viewer (default false: viewer is locked to this drawing)

  Exemple d'appel

  {"name": "view_dxf", "arguments": {"source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"size": "texte", "space": "texte", "texts": [], "units": "texte", "bounds": "texte", "format": "texte", "layers": [], "spaces": [], "entityCount": 1, "entityTypes": {}, "unsupported": {}, "segmentCount": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://aspicio-api.frontsail.app/mcp