mcp server
Agent Fabrication Network (UFP)
Turn designs into shipped parts: quote 3D printing, CNC, and decals, then check out.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Registry entry last updated 2026-07-24.
What this server can do
The endpoint published in the registry did not answer (TimeoutError: request timed out). The listing points at a server that is not running. The functions below are the last successful declaration, not a fresh answer.
Endpoint status observed on . Source: https://agenticfabricationnetwork.ai/mcp.
10 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
create_checkout(zip, city, name, email, phone, state, street1, street2, offer_id, return_url, billing_zip, billing_city, billing_name, billing_state, billing_street1, billing_street2, shipping_option_id)- Create the order and get a hosted payment link for a chosen offer. Call this as soon as the user picks an offer + shipping speed — do NOT ask for their address first: the secure payment page collects the shipping address and email. Only pass address fields if the user already volunteered them. Returns checkout_url — give it to the user to pay; UFP places the vendor order automatically after payment. Required: offer_id, shipping_option_id.
finalize_quote(quote_id)- ONLY for the case where a quote response came back with an EMPTY board and told you to call this: waits for the vendors to answer (up to ~40s) and returns their offers, which you then present as text. Call with just quote_id. NEVER call it on a response that already listed offers — that board is final and this cannot add to it. Required: quote_id.
get_fabrication_quote(cut, size, color, paper, sides, units, finish, process, product, vendors, callouts, deadline, file_url, material, width_in, food_safe, height_in, high_temp, placement, processes, share_key, bend_count, quantities, ships_from, design_file, metal_alloy, part_number, ship_to_zip, submersible, metal_finish, requirements, thickness_in, outdoor_rated, powder_finish, max_budget_usd, attachment_urls, metal_technology, min_vendor_stars, powder_technology, min_vendor_reviews, proven_spec_orders)- Get ranked, purchasable offers (price, ETA, preview image) for fabricating a physical item from a design file. process=fdm_print for 3D printing a model (STL/OBJ/PLY/3MF/AMF/STEP/IGES), process=cnc or process=sheetmetal for machined/bent metal parts (STEP, IGES, DXF), process=decal for stickers/decals from artwork (any common image or design file — PNG/JPG/HEIC/TIFF/GIF/BMP/WEBP/AVIF/SVG/PDF/AI/EPS/PSD/CDR, auto-converted). A .ufp file (UFP part container: the design plus saved spec/constraints in one) is accepted anywhere a design file is — its saved intent applies automatically and anything the user states now wins. If the user just drops a file and asks for a price, omit process — UFP routes it. Provide the design either as design_file (an image/file the user attached or you generated — preferred) or file_url (a public URL). REORDERS: if the user has a UFP part number (from a receipt email or a previous session, looks like UFP-… or part_…), pass it as part_number INSTEAD of any file — the stored design and spec are reused and re-shopped across all current vendors. Locked parts additionally require share_key (from the owner's share link). Returns offers across vendors like Google Flights returns flights.
get_material_guide(process, material, question)- Honest, cited material intelligence for material-choice / strength / durability / heat / outdoor questions ("my PLA part broke, what's stronger?", "will this survive outdoors?"). Returns caveats-FIRST facts: published specs (tensile, heat-deflection, UV/outdoor, chemical) each tagged vendor-cited vs general engineering knowledge, "stronger/tougher/hotter than X" ladders (PLA→PETG→ABS/ASA→nylon/PC→metals), and finish/coating options. Call it BEFORE answering such a question, then relay the facts. It supplies FACTS ONLY — comparative specs and vendor-admitted caveats, never a fitness-for-purpose or safety guarantee (that stays your judgment boundary); name express vendor claims "advertised", not "certified".
get_order_status(order_id)- Check status, ETA and tracking for a UFP order. Required: order_id.
leave_review(stars, claims, facets, comment, order_id)- Record the user's verified-purchase review of how a UFP order turned out. YOUR JOB IS TO STRUCTURE THE FEEDBACK: turn what the user actually said into stars (1-5 overall) and facet scores — "the cut was sloppy" -> quality, "parts arrived 2 days late" -> timeliness, "wrong color" -> accuracy. Keep the optional comment to a short factual summary of their words; never embellish. ALWAYS draft the review (stars, facets, comment) and confirm it with the user BEFORE calling this tool — e.g. "I'll rate this 2 stars with timeliness 1 because it arrived 2 days late — send it?". One review per order: submitting again updates the existing review. Use list_orders first if you need to resolve which order they mean. Required: order_id, stars.
list_orders- List this agent's recent UFP orders (newest first): order id, what was made, vendor, status, total, ETA, created date. Use it to resolve vague references — "my sticker order", "that order from 6 days ago" — to a concrete order_id before calling get_order_status or leave_review.
poll_quote(quote_id)- INTERNAL — the offer board calls this to refresh itself while vendors finish pricing. Never call this yourself. The board you were given is already final for its turn; do not reach for refine_quote to look at it again either, that paints a duplicate board. Required: quote_id.
refine_quote(color, finish, sort_by, vendors, callouts, deadline, material, quote_id, scenario, food_safe, high_temp, processes, quantities, ships_from, sort_label, sort_order, ship_to_zip, submersible, requirements, outdoor_rated, max_budget_usd, sort_direction, min_vendor_stars, min_vendor_reviews, proven_spec_orders)- Narrow an existing quote with new constraints (destination ZIP the user just provided, deadline, outdoor/waterproof/heat/food-safety requirements, budget, vendor reliability, verbatim requirements terms, drawing callouts, a process filter — "no, I meant in sheet metal" → processes — a ship-from country filter — "only US vendors" → ships_from — or a vendor filter — "only show A3D Manufacturing" → vendors) — or CHANGE its spec: material, color, or quantities. Changing material/quantity is a spec change, not a narrowing — pass it via the material/color/quantities args, NOT as a requirements term; the affected lanes re-price with the new spec through warm vendor sessions. For side-by-side comparisons ("how does carbon steel compare?"), add a scenario label — labeled refines coexist instead of replacing each other (max 4). "Organize by" ("sort by cheapest", "soonest arrival on top", "most green first") is also this tool: sort_by for objective orders, sort_order + sort_label for orders you judged yourself from the previews — presentation only, instant, nothing re-prices. Call with ONLY quote_id to re-read the quote (e.g. to pick up preview images that finished rendering). Required: quote_id.
reply_to_maker(message, order_id)- Send the user's answer to a question the maker (vendor) asked about a UFP order — get_order_status surfaces an open question when one is waiting. Confirm the answer with the user before sending. The network relays it: the maker sees plain text from the network account with the user's contact details and links stripped, so never include emails, phone numbers, or URLs the answer depends on. Required: order_id, message.
Last successful function declaration observed on . Source: https://agenticfabricationnetwork.ai/mcp. We list what the server declared; we do not call any of these functions.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-24 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-24 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 10 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | agenticfabricationnetwork.ai | |
| mcp endpoint status | unreachable | The endpoint published in the registry did not answer (TimeoutError: request timed out). The listing points at a server that is not running. | as of probe | agenticfabricationnetwork.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json