satmarin-catalog
Registry code: fdc833a0ed4547f6
Maritime VSAT spares: part search, fitment, supersession and quote requests for satmarin.com
from a public catalogue that lists it, not from the operator
- endpoint
- https://satmarin.com/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 satmarin-catalog live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
- Is satmarin-catalog free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does satmarin-catalog have?
- 4 tools: get_quote, resolve_supersession, check_compatibility, search_parts.
- Is satmarin-catalog 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.
90 days 99.7%· all time 99.7%
last good check
of 4 tools
- down → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- search maritime vsat spare parts
- check if a part fits an antenna
- find the replacement for a discontinued part
- request a quote for parts
- takes → gives
- text, data → data
- tools
- 3 reads1 changes data
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.
through this hub
successful
what callers paid
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
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_quote changes data unknown never probed
Request a formal quotation for catalog parts. Creates a quote request and returns its reference; Satmarin replies within one working day. This call emails nothing to the requester.
{ "type": "object", "required": [ "items", "contact" ], "properties": { "items": { "type": "array", "items": { "type": "object", "required": [ "sku", "qty" ], "properties": { "qty": { "type": "integer", "minimum": 1, "description": "Whole number, 1 or more." }, "sku": { "type": "string", "description": "Catalog part number." } } }, "maxItems": 20, "minItems": 1, "description": "1 to 20 lines. Every part number must be a live, quotable catalog product." }, "notes": { "type": "string", "description": "Optional free text, up to 1000 characters." }, "contact": { "type": "object", "required": [ "company", "name", "email" ], "properties": { "vat": { "type": [ "string", "null" ], "description": "Optional VAT or tax registration number, e.g. BE0479944518. Letters and digits only, up to 32 characters; spaces, dots and dashes are removed. Not validated against any tax register." }, "name": { "type": "string" }, "email": { "type": "string" }, "phone": { "type": [ "string", "null" ] }, "vessel": { "type": [ "string", "null" ] }, "company": { "type": "string" }, "country": { "type": [ "string", "null" ], "description": "Optional ISO 3166-1 alpha-2 country code of the customer, e.g. BE. Case-insensitive. Used for shipping and VAT treatment on the quotation." }, "billing_address": { "type": [ "string", "null" ], "description": "Optional postal billing address, used only if a proforma invoice is later issued. Free text, newline separated, at most 6 lines and 300 characters. Markup is removed. The country comes from contact.country, not from this field." } } } } }arguments 89 linesresolve_supersession reads unknown 14h ago
Is a part discontinued, and what replaces it? Give sku or product_id. Follows the replacement chain to the latest live product: successors lists the live replacements, supersedes lists the parts this one replaced.
{ "type": "object", "properties": { "sku": { "type": "string", "description": "Part number. Give this or product_id." }, "product_id": { "type": "integer", "description": "Catalog product id. Give this or sku." } } }arguments 13 linescheck_compatibility reads unknown 14h ago
Does a part fit a given antenna model? Give sku or product_id, plus antenna_model. Answers from catalog fitment data only: true or false when the part has model-level fitment data, "unknown" when it has none or is fitted only at series level. An unrecognised model, or a brand or series name, returns an error instead of an answer.
{ "type": "object", "required": [ "antenna_model" ], "properties": { "sku": { "type": "string", "description": "Part number. Give this or product_id." }, "product_id": { "type": "integer", "description": "Catalog product id. Give this or sku." }, "antenna_model": { "type": "string", "description": "One antenna model, name or slug, e.g. v100NX or v60E. Case and spacing are ignored." } } }arguments 20 linessearch_parts reads unknown 14h ago
Search the Satmarin catalog by part number, model or free text. Order: exact SKU (case and separators ignored), SKU prefix, then words found in the title or description in any order. A word that names an antenna model, such as v100NX, also matches parts fitted to that model. Use the model filter to restrict results to one model or series.
{ "type": "object", "required": [ "query" ], "properties": { "brand": { "type": "string", "description": "Exact brand slug, e.g. intellian." }, "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "Default 10, maximum 25." }, "model": { "type": "string", "description": "Antenna model or series, name or slug, e.g. v100NX or v-Series. Case and spacing are ignored; an unrecognised model returns an error." }, "query": { "type": "string", "description": "Part number, model or free text." }, "part_type": { "type": "string", "description": "Part type slug." } } }arguments 30 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idfdc833a0ed4547f6.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fdc833a0ed4547f6/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fdc833a0ed4547f6?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.