_ registry / mcp streamable-http · checked 1h ago

compatsy-compare

https://compatsy.com

Registry code: 87bf4d094e4eedd6

api record

Look up printer, nozzle, hotend, build plate, filament, enclosure products: search, specs with sources, side-by-side comparison, fit checks and live stock with verified prices. Fit verdicts cite the rule id and rules version that decided them; unknown means a needed spec is missing. Links are affiliate links; we may earn a commission. The default link is the lowest in-stock price regardless of commission.

endpoint
https://compatsy.com/3d-printing/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is compatsy-compare live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is compatsy-compare free to use?
Yes — the hub reached it with no key and no payment.
What tools does compatsy-compare have?
6 tools: get_product, check_stock, report_issue, compare, search_products, check_fit.
Is compatsy-compare safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
590ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_product unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_id"
      ],
      "properties": {
        "product_id": {
          "type": "string",
          "description": "Product id or slug"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • check_stock unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_id"
      ],
      "properties": {
        "product_id": {
          "type": "string"
        },
        "merchant_id": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • report_issue unknown never probed

    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"}

    mcp-tool

    {
      "type": "object",
      "required": [
        "entity_type",
        "entity_id",
        "claim"
      ],
      "properties": {
        "claim": {
          "type": "string",
          "maxLength": 500
        },
        "field": {
          "type": "string"
        },
        "entity_id": {
          "type": "string"
        },
        "entity_type": {
          "enum": [
            "product",
            "offer",
            "fit"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • compare unknown 1h ago

    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"]}

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1
        },
        "filters": {
          "type": "object",
          "description": "Spec field -> exact value, e.g. {\"material\":\"brass\"}",
          "additionalProperties": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "number"
              },
              {
                "type": "boolean"
              }
            ]
          }
        },
        "category": {
          "type": "string"
        },
        "product_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 10,
          "minItems": 2
        }
      },
      "additionalProperties": false
    }
    arguments 40 lines
  • search_products unknown 1h ago

    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}

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1
        },
        "query": {
          "type": "string"
        },
        "filters": {
          "type": "object",
          "description": "Spec field -> exact value, e.g. {\"material\":\"brass\"}",
          "additionalProperties": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "number"
              },
              {
                "type": "boolean"
              }
            ]
          }
        },
        "category": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • check_fit unknown 1h ago

    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"}

    mcp-tool

    {
      "type": "object",
      "required": [
        "subject_id",
        "target_id"
      ],
      "properties": {
        "target_id": {
          "type": "string",
          "description": "Printer or hotend id or slug"
        },
        "subject_id": {
          "type": "string",
          "description": "Part id or slug"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 87bf4d094e4eedd6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/87bf4d094e4eedd6/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/87bf4d094e4eedd6/badge.svg)](https://brick.blue/agent/87bf4d094e4eedd6?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.