# Orbilyn (remote · app.orbilyn.com)

Product data control center MCP — catalog consistency across marketplaces.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `app.orbilyn.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-orbilyn-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-orbilyn-mcp/api-mcp)

## Channel facts

- Endpoint: `https://app.orbilyn.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1425 tokens (~67/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 53% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-orbilyn-mcp 'https://app.orbilyn.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-orbilyn-mcp": {
      "url": "https://app.orbilyn.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-orbilyn-mcp": {
      "type": "http",
      "url": "https://app.orbilyn.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-orbilyn-mcp]
url = "https://app.orbilyn.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-orbilyn-mcp": {
      "type": "remote",
      "url": "https://app.orbilyn.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-orbilyn-mcp --url 'https://app.orbilyn.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-orbilyn-mcp:
    url: "https://app.orbilyn.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-orbilyn-mcp": {
      "Transport": "http",
      "Url": "https://app.orbilyn.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-orbilyn-mcp -t streamable-http -u 'https://app.orbilyn.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-orbilyn-mcp": {
      "type": "http",
      "url": "https://app.orbilyn.com/api/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78, +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.

### 2026-11-03 (score 77, +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.

### 2026-11-01 (score 76, +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.

### 2026-10-29 (score 75, +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.

### 2026-10-28 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 74, +36)

- [security improvement] Transport: unverified → pass
- [security improvement] 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.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] 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

### 2026-10-24 (score 38)

First indexed and scored.

## MCP tools (21)

### `list_integrations` (~22 tokens)

List Orbilyn channel integrations (metadata only, no secrets).

### `list_mismatches` (~49 tokens)

List mismatches from a comparison run (latest if runId omitted).

Input parameters:

- `limit` (number): Max mismatches (default 50)
- `runId` (string): Comparison run UUID

### `get_monitoring_alerts` (~30 tokens)

Get unread Monitoring alerts (new mismatches from scheduled runs).

Input parameters:

- `limit` (number)

### `find_product` (~39 tokens)

Find a product by SKU and/or EAN with stock and price per channel.

Input parameters:

- `ean` (string)
- `sku` (string)

### `get_comparison_summary` (~36 tokens)

Summaries of recent comparison / history runs (counts, labels).

Input parameters:

- `limit` (number): Max runs (default 5)

### `catalog_health_score` (~75 tokens)

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

Input parameters:

- `setId` (string): Optional comparison run UUID (default: latest)

### `list_critical_issues` (~135 tokens)

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.

Input parameters:

- `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)

### `prepare_fix_list` (~128 tokens)

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

Input parameters:

- `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)

### `ai_readiness_report` (~124 tokens)

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

Input parameters:

- `limit` (number): Page size (default 50, max 100)
- `offset` (number): Offset (default 0)
- `profile` (string): Audit profile (google_merchant now; others later)

### `explain_issue` (~82 tokens)

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

Input parameters:

- `profile` (string): Audit profile (default google_merchant)
- `sku` (string, required): Product SKU / id / GTIN to explain

### `get_webhook_config` (~55 tokens)

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).

### `configure_webhook` (~70 tokens)

Configure outbound webhook URL/secret (requires write scope). Events: catalog.duplicate.new, catalog.drift.status, sync.failure, monitoring.*.

Input parameters:

- `enabled` (boolean)
- `rotateSecret` (boolean)
- `secret` (string)
- `url` (string): https:// endpoint

### `run_monitoring` (~31 tokens)

Trigger a Monitoring compare run now (requires action scope).

Input parameters:

- `pairId` (string): Optional pair UUID

### `start_catalog_audit` (~70 tokens)

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.

Input parameters:

- `setId` (string): Optional comparison run UUID (default: latest)

### `get_audit_status` (~43 tokens)

Poll async catalog audit status by auditId (pending|running|succeeded|failed).

Input parameters:

- `auditId` (string, required): Audit UUID from start_catalog_audit

### `get_audit_result` (~60 tokens)

Fetch catalog audit result (CatalogIssue list + health). Paginate with limit/offset. Fails if audit is still pending/running.

Input parameters:

- `auditId` (string, required)
- `limit` (number)
- `offset` (number)

### `create_monitor` (~123 tokens)

Create a Scale Monitoring pair (Alerty/Automatyzacja). Params: sources, thresholds, issueTypes, actions (webhook|email|fix_list). Write scope.

Input parameters:

- `actions` (array): webhook|email|fix_list
- `enabled` (boolean)
- `issueTypes` (array): price|stock|status|missing
- `name` (string)
- `sourceIntegrationId` (string, required)
- `targetIntegrationId` (string, required)
- `thresholds` (object): mismatchCount, healthScoreDrop, ignorePriceBelowPercent, …

### `update_monitor` (~88 tokens)

Update an existing Monitoring pair (thresholds, sources, actions, enabled). Write scope.

Input parameters:

- `actions` (array)
- `enabled` (boolean)
- `issueTypes` (array)
- `monitorId` (string, required)
- `name` (string)
- `sourceIntegrationId` (string)
- `targetIntegrationId` (string)
- `thresholds` (object)

### `pause_monitor` (~27 tokens)

Pause (disable) a Monitoring pair. Write scope.

Input parameters:

- `monitorId` (string, required)

### `list_monitors` (~18 tokens)

List Scale Monitoring pairs configured for this account.

### `get_monitor_history` (~49 tokens)

Monitoring run history with deltas vs previous run (new / fixed / open) and CatalogIssue samples.

Input parameters:

- `limit` (number)
- `monitorId` (string): Optional pair UUID filter

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-orbilyn-mcp/api-mcp#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 74
- 2026-10-27: 74
- 2026-10-26: 38
- 2026-10-25: 38
- 2026-10-24: 38

## Common questions

### 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.

## Links

- Remote endpoint: https://app.orbilyn.com/api/mcp
- Authorisation metadata: https://app.orbilyn.com/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/general-remigius/orbilyn
- Website: https://orbilyn.com/developers/connect-ai
- Changelog RSS feed: https://verifymcp.io/servers/com-orbilyn-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-orbilyn-mcp/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-orbilyn-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-orbilyn-mcp/api-mcp