Home / MCP registry index / com.mechanofab/mechanofab
MechanoFab
com.mechanofab/mechanofab in the official MCP registry.
Endpoint https://mcp.mechanofab.com/mcp.
The registry describes it as: Manufacturing capability graph for AI agents: materials, processes, tolerances, and instant quotes.
We read its 20 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
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
calculate_part_mass check_equipment_capability check_material_environment_compatibility check_service_temperature compare_equipment compare_materials compare_processes filter_materials_by_constraint find_alternative_processes find_equipment_by_process find_equivalent_materials get_equipment_qc_specs get_industry_requirements get_iso2768_tolerances get_material_compliance get_material_process_compatibility get_process_specs match_industry_materials quote_calc search_materials
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-mechanofab-mechanofab)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.