Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vibe Manufacturing

REMOTE · VIBE-MANUFACTURING.COM

Find manufacturers worldwide, match a part spec to suppliers, estimate cost, request quotes.

+2 this week 77 Trust /100

Last scanned (21 hours ago)

Scores higher than 69% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Recent critical change

Authorization (7 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security66
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3271 tokens (~121/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1
    • Schema quality: 2847 → 3271 ▼ functional
    • New tool “create_project” functional
    • New tool “get_project” functional
    • New tool “plan_prototype” functional
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://vibe-manufacturing.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vibe-manufacturing.com CN=YE2,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA384 637cab88dec91aa3b20eda67e8e41afa4de
SANs: vibe-manufacturing.com, www.vibe-manufacturing.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of vibe-manufacturing.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
vibe-manufacturing.com. DS published 41433 13 Verified
vibe-manufacturing.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vibe-manufacturing.com/api/mcp Verified 200
http (plaintext) http://vibe-manufacturing.com/api/mcp HTTPS enforced 301 https://vibe-manufacturing.com/api/mcp
MCP tools · 27 exposed · ~3,180 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_design ~152

Check a design against typical manufacturing rules before you request quotes. Returns pass, warn or fail per check with the limit and the reason. Supported processes: sheet-metal, laser-cutting, cnc-machining, 3d-printing, injection-molding, die-casting, casting, metal-stamping, pcb-assembly. Parameters are in millimetres/degrees, for example thickness_mm, bend_radius_mm, flange_length_mm, hole_diameter_mm, hole_to_edge_mm, hole_to_bend_mm, wall_thickness_mm, pocket_depth_mm, inside_corner_radius_mm, draft_deg, material.

NameTypeReqDescription
paramsobjectyesNumeric design parameters, see the tool description
processstringyes–

No output schema declared.

No examples provided.

create_project ~194

Start a prototype project for the human you act for: we make the sourcing plan (as plan_prototype) and, once the person confirms by a click in their own mailbox, send one quote request per make-part to the matching manufacturers. Needs the requester e-mail and user_consent; nothing is sent before the confirmation click. Returns the project id, a token to read it and the plan.

NameTypeReqDescription
budget_notestring––
descriptionstringyesThe product, what it does, size, existing prototypes or files (at least 20 characters)
quantityinteger–Target quantity for the first batch (default 10)
requester_emailstringyesThe person's e-mail: confirmation link and quotes go there
ship_to_countrystring–ISO country code
user_consentbooleanyestrue only after the user agreed that the part requests are shared with matched manufacturers

No output schema declared.

No examples provided.

create_rfq ~364

Create a structured request for quotation for the human you act for. Call get_rfq_requirements for the process first and upload files with upload_rfq_file; use dry_run to check completeness before sending. The answer contains quote_readiness, missing and recommended items. We match manufacturers, email the ones that opted in, and return direct contact, quote-form and agent links for all matches plus an RFQ id and a token to read quotes later. Only call after the user agreed that the request is shared with matched manufacturers.

NameTypeReqDescription
budget_notestring––
cad_filesarray––
callback_urlstring–Optional https URL that receives a signed event when a factory answers
certificationsarray––
descriptionstringyesPart, size, material, use
dry_runboolean–true = check completeness only; nothing is stored or sent
file_formatsarray––
file_idsarray–file_id values returned by upload_rfq_file
finishstring––
industriesarray––
materialsarray––
needed_bystring––
processstringyes–
quantityintegeryes–
requester_emailstring–Reply address of the human requester; required unless dry_run
ship_to_countrystring–ISO 3166-1 alpha-2
strictboolean–true = refuse to send when required items are missing
thickness_mmnumber–Material thickness for sheet, plate and cut parts
tolerance_mmnumber––
user_consentboolean–true only if the user agreed to share the request with matched manufacturers; required unless dry_run

No output schema declared.

No examples provided.

estimate_product_cost ~114

Estimate landed cost per unit and the price needed for a target margin for a custom product. All money values in USD per unit.

NameTypeReqDescription
assembly_minutesnumber––
finishingnumber––
hardwarenumber––
labor_rate_per_hournumber––
packagingnumber––
partnumber––
payment_fee_percentnumber––
returns_percentnumber––
shippingnumber––
target_margin_percentnumber––

No output schema declared.

No examples provided.

fetch ~45

Fetch the full text of a document or manufacturer profile by the id returned from search.

NameTypeReqDescription
idstringyesA page URL or supplier:<CC>:<domain> from search results

No output schema declared.

No examples provided.

find_registered_businesses ~135

Find manufacturing businesses you can contact directly, including official-registry establishments without a website (Mexico: INEGI DENUE). Returns how to reach each one: contact form, phone and email (published only for legal entities), website. Filter by ISO country code (MX, US, ...), process and city. Use next_after to page.

NameTypeReqDescription
afterinteger–next_after value from the previous page
citystring––
countrystring–ISO 3166-1 alpha-2, e.g. MX
limitinteger––
processstring––

No output schema declared.

No examples provided.

find_suppliers ~156

Find contract manufacturers in the directory by country and process. Processes: laser-cutting, cnc-machining, sheet-metal, 3d-printing, injection-molding, pcb-assembly, die-casting, welding, waterjet-cutting, metal-stamping, forging, heat-treatment, grinding-polishing, casting, wire-forming, steel-construction, surface-finishing. Country as ISO code (DE) or slug (germany).

NameTypeReqDescription
citystring––
countrystring–ISO 3166-1 alpha-2 code or country slug
limitinteger–Max results, 1 to 100
processstring–Process id, e.g. laser-cutting

No output schema declared.

No examples provided.

get_design_rules ~91

Design-for-manufacturing rules for one process (sheet metal, CNC machining, injection molding, 3D printing, casting, welding, PCB assembly and more): typical tolerances, file formats, the rules with their reasons, a pre-RFQ checklist and common mistakes. Typical rules of thumb; the manufacturer's own guidelines override them. Omit process to list all.

NameTypeReqDescription
processstring––

No output schema declared.

No examples provided.

get_my_profile ~55

For a manufacturer's agent (needs the supplier token): what the directory stores about your company, and the allowed values for each field.

NameTypeReqDescription
supplier_tokenstring–Only if your client cannot send the Authorization: Bearer header

No output schema declared.

No examples provided.

get_playbook_step ~43

Get one of the 13 playbook steps (summary, explanation, checklist, related tools).

NameTypeReqDescription
stepintegeryesStep number 1 to 13

No output schema declared.

No examples provided.

get_project ~60

Read a prototype project you created: the plan and, per part request, how many manufacturers were reached and how many quotes arrived. Needs the project_id and the token from create_project.

NameTypeReqDescription
project_idstringyes–
tokenstringyes–

No output schema declared.

No examples provided.

get_request ~75

For a manufacturer's agent (needs the supplier token): one request in full — spec, what is missing, why you matched, file download links for your company, and the conversation so far.

NameTypeReqDescription
rfq_idstringyes–
supplier_tokenstring–Only if your client cannot send the Authorization: Bearer header

No output schema declared.

No examples provided.

get_rfq ~55

Read the matches and the quotes received so far for an RFQ you created. Needs the rfq_id and the token returned by create_rfq.

NameTypeReqDescription
rfq_idstringyes–
tokenstringyes–

No output schema declared.

No examples provided.

get_rfq_requirements ~48

What a factory needs to quote a given process (required and recommended items with accepted values). Read this before create_rfq so the request is complete.

NameTypeReqDescription
processstringyes–

No output schema declared.

No examples provided.

get_rfq_thread ~88

Read the conversation of a request: messages from factories (answers, quotes, files) and your own. Pass since=<last message_id> to get only new ones.

NameTypeReqDescription
rfq_idstringyes–
sinceinteger––
tokenstring–rfq token (buyer) or supplier token (factory); may be sent as Authorization: Bearer instead

No output schema declared.

No examples provided.

list_manufacturing_tools ~52

List tools and factories with pros and cons. Optional category: Fabrication, Electronics, Sourcing, Prototyping, Measuring, Design, Review.

NameTypeReqDescription
categorystring–Optional category filter

No output schema declared.

No examples provided.

list_my_requests ~84

For a manufacturer's agent (needs the supplier token): the open quote requests your company was matched to, newest first, with readiness, whether you answered, your quote and unread buyer messages.

NameTypeReqDescription
include_answeredboolean–Default true
limitinteger––
supplier_tokenstring–Only if your client cannot send the Authorization: Bearer header

No output schema declared.

No examples provided.

match_manufacturers ~137

Rank manufacturers for a structured part spec. Returns scored matches with the reasons, so an agent can explain the choice to its user.

NameTypeReqDescription
certificationsarray––
countrystring–Preferred country, ISO code or slug
file_formatsarray–CAD formats you can supply
industriesarray––
limitinteger––
materialsarray––
processstringyes–
quantityinteger–Units wanted; favors prototype-friendly shops for small numbers and series producers for large ones
tolerance_mmnumber–Tightest tolerance you need, in mm

No output schema declared.

No examples provided.

plan_prototype ~170

Turn a product description into a sourcing plan for a prototype or first batch: parts split into make (process, material, what a factory needs, matched manufacturers) and buy (module class, where such parts come from), integration steps, gaps and assumptions. Read-only, needs no e-mail; use it before create_rfq when the user has a product rather than a single part. States no prices or lead times.

NameTypeReqDescription
budget_notestring–Optional budget or constraints
descriptionstringyesWhat the product is, what it does, its size, which parts or prototypes already exist (at least 20 characters)
quantityinteger–Target quantity for the first batch (default 10)
ship_to_countrystring–ISO country code, e.g. US

No output schema declared.

No examples provided.

search ~77

Search the Vibe Manufacturing playbook, guides, tool reviews and the manufacturer directory. Mention a process (for example CNC machining) or a country to get matching manufacturers. Returns result ids for fetch.

NameTypeReqDescription
querystringyesWhat to look for, e.g. "laser cutting manufacturers in Germany" or "how to check manufacturability"

No output schema declared.

No examples provided.

search_site ~52

Search the playbook, guides, tool reviews and comparisons on vibe-manufacturing.com.

NameTypeReqDescription
limitinteger–Max results, 1 to 20
querystringyesFree-text search term

No output schema declared.

No examples provided.

send_message ~112

For a manufacturer's agent (needs the supplier token): write to the buyer of a request you were matched to — a question, an answer or an update, optionally with file_ids from upload_rfq_file. Draft it for the manufacturer and send only after they confirm.

NameTypeReqDescription
bodystringyes–
file_idsarray––
kindstring––
rfq_idstringyes–
supplier_tokenstring–Only if your client cannot send the Authorization: Bearer header

No output schema declared.

No examples provided.

send_rfq_message ~133

Write to the matched factories about a request (buyer token) or to the buyer (supplier token): a question, an answer or an update, optionally with file_ids. We relay it by email or API and keep the thread.

NameTypeReqDescription
bodystringyes–
company_idinteger–Buyer only: address one matched manufacturer instead of all
file_idsarray––
kindstring––
rfq_idstringyes–
tokenstring–rfq token (buyer) or supplier token (factory); may be sent as Authorization: Bearer instead

No output schema declared.

No examples provided.

submit_quote ~162

For a manufacturer's agent: answer an RFQ the company was matched to. Needs the supplier token issued when the company registered. Replaces any existing quote from this supplier for this RFQ, adds a thread entry and notifies the buyer by email and an optional callback; repeating the call sends notifications again. Only call with the supplier's authorization.

NameTypeReqDescription
currencystring–3-letter code, default EUR
lead_time_daysinteger––
notesstring––
quantityinteger––
rfq_idstringyes–
supplier_tokenstring–Only if your client cannot send the Authorization: Bearer header
unit_pricenumberyes–
valid_untilstring–YYYY-MM-DD

No output schema declared.

No examples provided.

submit_quote_request ~120

Send a quote request for the human you act for. Only call after the user agreed that the request and email may be shared with suitable manufacturers. A person reviews it and replies by email.

NameTypeReqDescription
countrystring––
descriptionstringyesPart, material, size, tolerances, file formats
emailstringyesReply address of the human requester
processstring––
quantitystring––
user_consentbooleanyestrue only if the user agreed to share the request with manufacturers

No output schema declared.

No examples provided.

update_my_profile ~216

For a manufacturer's agent (needs the supplier token): change processes, materials, certs, formats, industries, signals, machines, lead_time_days, min_order_qty, notes or notify_email. Fields you leave out keep their value; a field you send replaces it whole (a processes list replaces the stored list, so send the complete list, not only additions). Name, domain, country and address cannot be changed here. Set authorised: true only after the manufacturer confirmed the change.

NameTypeReqDescription
authorisedbooleanyes–
certsarray––
formatsarray––
industriesarray––
lead_time_daysinteger––
machinesarray––
materialsarray––
min_order_qtyinteger––
notesstring––
notify_emailstring––
processesarray––
signalsarray––
supplier_tokenstring–Only if your client cannot send the Authorization: Bearer header

No output schema declared.

No examples provided.

upload_rfq_file ~190

Upload a design file (STEP/STP, IGES/IGS, STL, 3MF, OBJ, DXF, DWG, PDF, ZIP (Gerber files go in a ZIP); up to 6 MB as base64 here, up to 100 MB with POST /api/v1/rfq/files?name=...). Returns a file_id to pass in create_rfq file_ids. Unused files expire after 24 hours. Only upload files the user agreed to share with manufacturers.

NameTypeReqDescription
content_base64stringyes–
namestringyesFile name with extension, e.g. bracket.step
rfq_idstring–Optional: attach to an existing request (needs token)
tokenstring–The rfq token, or a supplier token, when rfq_id is given; may be sent as Authorization: Bearer instead

No output schema declared.

No examples provided.

Install

How do I install the Vibe Manufacturing MCP server?

Vibe Manufacturing is a hosted endpoint at https://vibe-manufacturing.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · vibe-manufacturing.com

# add to Claude Code
claude mcp add --transport http com-vibe-manufacturing-manufacturer-finder 'https://vibe-manufacturing.com/api/mcp'
Common questions

What is the Vibe Manufacturing MCP server?

Vibe Manufacturing is an MCP server listed in the public MCP registry as com.vibe-manufacturing/manufacturer-finder. Find manufacturers worldwide, match a part spec to suppliers, estimate cost, request quotes. This page covers its hosted endpoint (https://vibe-manufacturing.com/api/mcp).

Is the Vibe Manufacturing MCP server safe to use?

Vibe Manufacturing scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Vibe Manufacturing MCP server expose?

Vibe Manufacturing exposes 27 tools: search, fetch, search_site, get_playbook_step, list_manufacturing_tools, and 22 more. Their descriptions and schemas cost roughly 3,180 tokens of context every time the server is loaded.

Does the Vibe Manufacturing MCP server require authentication?

No. We connected to Vibe Manufacturing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Vibe Manufacturing MCP server still maintained?

Vibe Manufacturing is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Vibe Manufacturing MCP server?

VerifyMCP ran 13 checks on Vibe Manufacturing, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.