Home / MCP registry index / com.aiurion/agentic-3d-printing

AIURION Agentic 3D Printing — San Francisco

com.aiurion/agentic-3d-printing in the official MCP registry. Endpoint https://aiurion.com/api/agent/v1/mcp.

The registry describes it as: SF 3D printing + design workbenches (enclosures, grippers, fixtures, stamping). Quote and order.

We read its 17 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

prepare_workholding quote_workholding prepare_gripper quote_gripper prepare_stamping quote_stamping get_workbench_capabilities prepare_enclosure quote_enclosure printing.capabilities.get printing.sessions.start printing.quotes.create printing.quotes.get printing.quotes.update printing.checkout.create printing.orders.get printing.quotes.preview

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-aiurion-agentic-3d-printing/badge.svg)](https://lazaretto.dev/mcp-registry/com-aiurion-agentic-3d-printing)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.