compatsy MCP server

• Registry namecom.compatsy/3d-printingverified in the MCP registry

The registry name sits under compatsy.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-30
• Tools6
• Server calls itselfcompatsy-compare
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 228 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer501 ms
• Space in an agent's context≈ 880 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsB · 89 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 4 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_products

  Find products by name or by category and spec filters; returns key specs and the best in-stock offer. Example: {"query":"0.4 hardened nozzle","category":"nozzle","limit":5}

• get_product

  Full specs with per-field confidence and source, every offer with verified time, 30/90-day price range. Example: {"product_id":"prusa-mk4s"}

• compare

  Side-by-side spec table with offers and the fields that differ. Pass 2-10 product_ids, or a category with filters. Example: {"product_ids":["e3d-v6-brass-0-4","bondtech-cht-0-4"]}

• check_fit

  Does this part fit that machine? Returns a verdict with the rule id and version that decided it, or the missing fields. Example: {"subject_id":"e3d-v6-brass-0-4","target_id":"prusa-mk4s"}

• check_stock

  Availability and price per merchant, re-verified live when the data is over an hour old. Example: {"product_id":"prusa-mk4s","merchant_id":"prusa3d"}

• report_issue

  Flag a wrong spec, price or fit verdict. Reports never edit facts; two independent reports mark a fact disputed. Example: {"entity_type":"product","entity_id":"prusa-mk4s","field":"nozzle_thread","claim":"MK4S uses the Nextruder thread"}

• com.compatsy/home-espressoanswers, 6 toolsverified in the MCP registry