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.

com.satmarin/catalog

REMOTE · SATMARIN.COM · SCANNED SEP 27

Maritime VSAT spares: part search, fitment, supersession and quote requests for satmarin.com

Available components

+4 this week 72 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 504 tokens (~126/item across 4 items; 4 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 Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the com.satmarin/catalog MCP server?

com.satmarin/catalog is a hosted endpoint at https://satmarin.com/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 · satmarin.com

# add to Claude Code
claude mcp add --transport http com-satmarin-catalog 'https://satmarin.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-satmarin-catalog": {
      "url": "https://satmarin.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-satmarin-catalog": {
      "type": "http",
      "url": "https://satmarin.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-satmarin-catalog]
url = "https://satmarin.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-satmarin-catalog": {
      "type": "remote",
      "url": "https://satmarin.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-satmarin-catalog --url 'https://satmarin.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-satmarin-catalog:
    url: "https://satmarin.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-satmarin-catalog": {
      "Transport": "http",
      "Url": "https://satmarin.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-satmarin-catalog -t streamable-http -u 'https://satmarin.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-satmarin-catalog": {
      "type": "http",
      "url": "https://satmarin.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 27 Sept 26 +1

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

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +3
    • Tool “check_compatibility” rewrote its description, which is the text the model reads security
    • Tool “resolve_supersession” rewrote its description, which is the text the model reads security
    • Tool “search_parts” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 62% → 92% ▲ functional
    • Tool “check_compatibility” now declares an output schema ▲ functional
    • Tool “get_quote” now declares an output schema ▲ functional
    • Tool “resolve_supersession” now declares an output schema ▲ functional
    • Tool “search_parts” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Schema quality: good → excellent functional
    • “check_compatibility” reworded the description of “antenna_model” cosmetic
    • “check_compatibility” reworded the description of “product_id” cosmetic
    • “check_compatibility” reworded the description of “sku” cosmetic
    • “resolve_supersession” reworded the description of “product_id” cosmetic
    • “resolve_supersession” reworded the description of “sku” cosmetic
    • “search_parts” reworded the description of “brand” cosmetic
    • “search_parts” reworded the description of “model” cosmetic
    • Tool “check_compatibility” changed its title: Check compatibility cosmetic
    • Tool “get_quote” changed its title: Request a quotation cosmetic
    • Tool “resolve_supersession” changed its title: Resolve supersession cosmetic
    • Tool “search_parts” changed its title: Search parts cosmetic
  • 13 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
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 27 Sept 2026 · Probed https://satmarin.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=satmarin.com CN=WE1,O=Google Trust Services,C=US 4 Sept 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA256 6651300a5c44dfeb13c859c0b9f54247
SANs: satmarin.com, *.satmarin.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of satmarin.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
satmarin.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://satmarin.com/mcp Verified 200
http (plaintext) http://satmarin.com/mcp HTTPS enforced 301 https://satmarin.com/mcp
MCP tools · 4 exposed · ~504 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_compatibility ~149

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.

NameTypeReqDescription
antenna_modelstringyesOne antenna model, name or slug, e.g. v100NX or v60E. Case and spacing are ignored.
product_idinteger–Catalog product id. Give this or sku.
skustring–Part number. Give this or product_id.
NameTypeReqDescription
antenna_modelstringyesThe resolved model slug.
basisstringyes–
compatible–yes–
skustring|nullyes–
urlstringyes–

No examples provided.

get_quote ~92

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.

NameTypeReqDescription
contactobjectyes–
itemsarrayyes1 to 20 lines. Every part number must be a live, quotable catalog product.
notesstring–Optional free text, up to 1000 characters.
NameTypeReqDescription
messagestringyes–
referencestringyes–
statusstringyes–

No examples provided.

resolve_supersession ~83

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.

NameTypeReqDescription
product_idinteger–Catalog product id. Give this or sku.
skustring–Part number. Give this or product_id.
NameTypeReqDescription
eolbooleanyes–
no_replacementbooleanyes–
skustring|nullyes–
successorsarrayyes–
supersedesarrayyes–

No examples provided.

search_parts ~180

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.

NameTypeReqDescription
brandstring–Exact brand slug, e.g. intellian.
limitinteger–Default 10, maximum 25.
modelstring–Antenna model or series, name or slug, e.g. v100NX or v-Series. Case and spacing are ignored; an unrecognised model returns an error.
part_typestring–Part type slug.
querystringyesPart number, model or free text.
NameTypeReqDescription
matchstringyes–
resultsarrayyes–
totalintegeryes–

No examples provided.

Common questions

What is the com.satmarin/catalog MCP server?

com.satmarin/catalog is an MCP server listed in the public MCP registry as com.satmarin/catalog. Maritime VSAT spares: part search, fitment, supersession and quote requests for satmarin.com. This page covers its hosted endpoint (https://satmarin.com/mcp).

Is the com.satmarin/catalog MCP server safe to use?

com.satmarin/catalog scores 72 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 com.satmarin/catalog MCP server expose?

com.satmarin/catalog exposes 4 tools: search_parts, check_compatibility, resolve_supersession, get_quote. Their descriptions and schemas cost roughly 504 tokens of context every time the server is loaded.

Does the com.satmarin/catalog MCP server require authentication?

No. We connected to com.satmarin/catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.satmarin/catalog MCP server still maintained?

com.satmarin/catalog is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.