Orbilyn
REMOTE · APP.ORBILYN.COM
Product data control center MCP — catalog consistency across marketplaces.
Available components
Last scanned (17 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1425 tokens (~67/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% 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
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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 →
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.
- 5 Nov 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.
- 3 Nov 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.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 +36
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 53 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 24 Oct 26 38
First indexed and scored.
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://app.orbilyn.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=*.orbilyn.com | CN=YR1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | RSA 2048 | SHA256-RSA | 51363855ed4322f029a52eef9457c120b56 |
| SANs: *.orbilyn.com, orbilyn.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.orbilyn.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| orbilyn.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="orbilyn-mcp", resource_metadata="https://orbilyn.com/.well-known/oauth-protected-resource", scope="read"
Bearer realm="orbilyn-mcp", resource_metadata="https://orbilyn.com/.well-known/oauth-protected-resource", scope="read"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-410eXPIxtS2f+fO5za/fsw==' 'sha256-c8BjZT9ENCBk4L/UK9pOoFmsBtiQvp7a4CoOA2H8Frg=' https://cdn.paddle.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.paddle.com https://checkout.paddle.com; frame-src 'self' https://buy.paddle.com https://checkout.paddle.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self), usb=() |
Protected resource metadata
| Document | https://orbilyn.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://app.orbilyn.com/api/mcp |
| Authorisation server | https://orbilyn.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.orbilyn.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.orbilyn.com/api/mcp | HTTPS enforced | 308 | https://app.orbilyn.com/api/mcp |
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 →
ai_readiness_report ~124
Shopping-agent readiness: catalog products agents would reject (missing GTIN/EAN, photos, description, attributes, price/stock) plus what to fill in. Shared CatalogIssue format. Every result includes rules_version, audit_date, checked_fields, profile (google_merchant). Example: {"profile":"google_merchant","limit":50}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Page size (default 50, max 100) |
| offset | number | – | Offset (default 0) |
| profile | string | – | Audit profile (google_merchant now; others later) |
No output schema declared.
No examples provided.
catalog_health_score ~75
Catalog health score 0–100 with breakdown: photos, descriptions, prices, stock, duplicates, channel_consistency. Uses the latest comparison run (or setId) plus Overview media signals. Example: {"setId":"<uuid>"}.
| Name | Type | Req | Description |
|---|---|---|---|
| setId | string | – | Optional comparison run UUID (default: latest) |
No output schema declared.
No examples provided.
configure_webhook ~70
Configure outbound webhook URL/secret (requires write scope). Events: catalog.duplicate.new, catalog.drift.status, sync.failure, monitoring.*.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | – |
| rotateSecret | boolean | – | – |
| secret | string | – | – |
| url | string | – | https:// endpoint |
No output schema declared.
No examples provided.
create_monitor ~123
Create a Scale Monitoring pair (Alerty/Automatyzacja). Params: sources, thresholds, issueTypes, actions (webhook|email|fix_list). Write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | – | webhook|email|fix_list |
| enabled | boolean | – | – |
| issueTypes | array | – | price|stock|status|missing |
| name | string | – | – |
| sourceIntegrationId | string | yes | – |
| targetIntegrationId | string | yes | – |
| thresholds | object | – | mismatchCount, healthScoreDrop, ignorePriceBelowPercent, … |
No output schema declared.
No examples provided.
explain_issue ~82
Per SKU: what shopping-agent readiness checks failed and why. Same meta envelope (rules_version, audit_date, checked_fields, profile) + CatalogIssue list + explanations. Example: {"sku":"SKU-100"}.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | – | Audit profile (default google_merchant) |
| sku | string | yes | Product SKU / id / GTIN to explain |
No output schema declared.
No examples provided.
find_product ~39
Find a product by SKU and/or EAN with stock and price per channel.
| Name | Type | Req | Description |
|---|---|---|---|
| ean | string | – | – |
| sku | string | – | – |
No output schema declared.
No examples provided.
get_audit_result ~60
Fetch catalog audit result (CatalogIssue list + health). Paginate with limit/offset. Fails if audit is still pending/running.
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | – |
| limit | number | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
get_audit_status ~43
Poll async catalog audit status by auditId (pending|running|succeeded|failed).
| Name | Type | Req | Description |
|---|---|---|---|
| auditId | string | yes | Audit UUID from start_catalog_audit |
No output schema declared.
No examples provided.
get_comparison_summary ~36
Summaries of recent comparison / history runs (counts, labels).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max runs (default 5) |
No output schema declared.
No examples provided.
get_monitor_history ~49
Monitoring run history with deltas vs previous run (new / fixed / open) and CatalogIssue samples.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| monitorId | string | – | Optional pair UUID filter |
No output schema declared.
No examples provided.
get_monitoring_alerts ~30
Get unread Monitoring alerts (new mismatches from scheduled runs).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
get_webhook_config ~55
Read Scale webhook subscription (URL, enabled, event catalog). Signing: X-Orbilyn-Signature HMAC-SHA256. Webhook sample items use the CatalogIssue schema (sku + type preserved; additive fields).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_critical_issues ~135
List CatalogIssue rows sorted by impact (severity then type). Default severity=critical. Supports limit + offset pagination. Example: {"limit":20,"offset":0,"severity":"critical"}. Issue shape: sku, channel, type, severity, current, expected, suggested_action, detected_at, source_id, set_id.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Page size (default 50, max 100) |
| offset | number | – | Offset (default 0) |
| setId | string | – | Optional comparison run UUID |
| severity | string | – | critical | important | minor | all (default critical) |
No output schema declared.
No examples provided.
list_integrations ~22
List Orbilyn channel integrations (metadata only, no secrets).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_mismatches ~49
List mismatches from a comparison run (latest if runId omitted).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max mismatches (default 50) |
| runId | string | – | Comparison run UUID |
No output schema declared.
No examples provided.
list_monitors ~18
List Scale Monitoring pairs configured for this account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pause_monitor ~27
Pause (disable) a Monitoring pair. Write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
prepare_fix_list ~128
Prepare a CatalogIssue fix list as JSON (default) or CSV. Same schema as list_critical_issues. Example JSON: {"format":"json","limit":50}. Example CSV: {"format":"csv","severity":"all"}.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | json (default) or csv |
| limit | number | – | Page size (default 50, max 100) |
| offset | number | – | Offset (default 0) |
| setId | string | – | Optional comparison run UUID |
| severity | string | – | critical | important | minor | all (default all) |
No output schema declared.
No examples provided.
run_monitoring ~31
Trigger a Monitoring compare run now (requires action scope).
| Name | Type | Req | Description |
|---|---|---|---|
| pairId | string | – | Optional pair UUID |
No output schema declared.
No examples provided.
start_catalog_audit ~70
Start a catalog audit over persisted comparison/Overview data (no live re-import; safe for large catalogs). Returns auditId + status. Result uses shared CatalogIssue format. Webhook: audit.completed. Requires action scope.
| Name | Type | Req | Description |
|---|---|---|---|
| setId | string | – | Optional comparison run UUID (default: latest) |
No output schema declared.
No examples provided.
update_monitor ~88
Update an existing Monitoring pair (thresholds, sources, actions, enabled). Write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | – | – |
| enabled | boolean | – | – |
| issueTypes | array | – | – |
| monitorId | string | yes | – |
| name | string | – | – |
| sourceIntegrationId | string | – | – |
| targetIntegrationId | string | – | – |
| thresholds | object | – | – |
No output schema declared.
No examples provided.
How do I install the Orbilyn MCP server?
Orbilyn is a hosted endpoint at https://app.orbilyn.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 · app.orbilyn.com
claude mcp add --transport http com-orbilyn-mcp 'https://app.orbilyn.com/api/mcp'
What is the Orbilyn MCP server?
Orbilyn is an MCP server listed in the public MCP registry as com.orbilyn/mcp. Product data control center MCP, catalog consistency across marketplaces. This page covers its hosted endpoint (https://app.orbilyn.com/api/mcp).
Is the Orbilyn MCP server safe to use?
Orbilyn scores 78 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 Orbilyn MCP server expose?
Orbilyn exposes 21 tools: list_integrations, list_mismatches, get_monitoring_alerts, find_product, get_comparison_summary, and 16 more. Their descriptions and schemas cost roughly 1,354 tokens of context every time the server is loaded.
Does the Orbilyn MCP server require authentication?
Yes. Orbilyn asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Orbilyn MCP server still maintained?
Orbilyn 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 Orbilyn MCP server?
VerifyMCP ran 13 checks on Orbilyn, 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.