Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
Orbilyn is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
21
tools declared
remote
at its publisher
—
calls last 7d
What it does
Product data control center MCP — catalog consistency across marketplaces.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http orbilyn-mcp https://app.orbilyn.com/api/mcp
# 2 — ask your agent for something these tools do
# list_integrations, list_mismatches, get_monitoring_alerts and 18 more
Its address takes AUTHORIZATION (Scale API key (orb_live_…) or OAuth access token (orb_at_…) as Bearer) in the Authorization header: add it to the entry your client keeps for it.
Orbilyn costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ORAll 1 server
orbilyn1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --transport http orbilyn-mcp https://app.orbilyn.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — the only sign-in is its publisher’s own, with OAuth.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Scale API key (orb_live_…) or OAuth access token (orb_at_…) as Bearer. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List Orbilyn channel integrations (metadata only, no secrets).
No parameter schema on file.
List mismatches from a comparison run (latest if runId omitted).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | no | Comparison run UUID |
| limit | number | no | Max mismatches (default 50) |
Get unread Monitoring alerts (new mismatches from scheduled runs).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | — |
Find a product by SKU and/or EAN with stock and price per channel.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sku | string | no | — |
| ean | string | no | — |
Summaries of recent comparison / history runs (counts, labels).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Max runs (default 5) |
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>"}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setId | string | no | Optional comparison run UUID (default: latest) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setId | string | no | Optional comparison run UUID |
| limit | number | no | Page size (default 50, max 100) |
| offset | number | no | Offset (default 0) |
| severity | string | no | critical | important | minor | all (default critical) |
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"}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setId | string | no | Optional comparison run UUID |
| limit | number | no | Page size (default 50, max 100) |
| offset | number | no | Offset (default 0) |
| format | string | no | json (default) or csv |
| severity | string | no | critical | important | minor | all (default all) |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile | string | no | Audit profile (google_merchant now; others later) |
| limit | number | no | Page size (default 50, max 100) |
| offset | number | no | Offset (default 0) |
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"}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sku | string | yes | Product SKU / id / GTIN to explain |
| profile | string | no | Audit profile (default google_merchant) |
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).
No parameter schema on file.
Configure outbound webhook URL/secret (requires write scope). Events: catalog.duplicate.new, catalog.drift.status, sync.failure, monitoring.*.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | https:// endpoint |
| enabled | boolean | no | — |
| secret | string | no | — |
| rotateSecret | boolean | no | — |
Trigger a Monitoring compare run now (requires action scope).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pairId | string | no | Optional pair UUID |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setId | string | no | Optional comparison run UUID (default: latest) |
Poll async catalog audit status by auditId (pending|running|succeeded|failed).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| auditId | string | yes | Audit UUID from start_catalog_audit |
Fetch catalog audit result (CatalogIssue list + health). Paginate with limit/offset. Fails if audit is still pending/running.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| auditId | string | yes | — |
| limit | number | no | — |
| offset | number | no | — |
Create a Scale Monitoring pair (Alerty/Automatyzacja). Params: sources, thresholds, issueTypes, actions (webhook|email|fix_list). Write scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | — |
| sourceIntegrationId | string | yes | — |
| targetIntegrationId | string | yes | — |
| thresholds | object | no | mismatchCount, healthScoreDrop, ignorePriceBelowPercent, … |
| issueTypes | array | no | price|stock|status|missing |
| actions | array | no | webhook|email|fix_list |
| enabled | boolean | no | — |
Update an existing Monitoring pair (thresholds, sources, actions, enabled). Write scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monitorId | string | yes | — |
| name | string | no | — |
| sourceIntegrationId | string | no | — |
| targetIntegrationId | string | no | — |
| thresholds | object | no | — |
| issueTypes | array | no | — |
| actions | array | no | — |
| enabled | boolean | no | — |
Pause (disable) a Monitoring pair. Write scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monitorId | string | yes | — |
List Scale Monitoring pairs configured for this account.
No parameter schema on file.
Monitoring run history with deltas vs previous run (new / fixed / open) and CatalogIssue samples.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monitorId | string | no | Optional pair UUID filter |
| limit | number | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Orbilyn or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.4.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest17630e203b9962860d06483b26e966e2b7eba51fd1f799daf8674843a97a1c7c
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_integrations | no tags | |
| list_mismatches | no tags | |
| get_monitoring_alerts | no tags | |
| find_product | no tags | |
| get_comparison_summary | no tags | |
| catalog_health_score | no tags | |
| list_critical_issues | no tags | |
| prepare_fix_list | no tags | |
| ai_readiness_report | no tags | |
| explain_issue | no tags | |
| get_webhook_config | no tags | |
| configure_webhook | external-sink | external-sink: keyword "webhook" |
| run_monitoring | no tags | |
| start_catalog_audit | no tags | |
| get_audit_status | no tags | |
| get_audit_result | untrusted-input | untrusted-input: keyword "fetch" |
| create_monitor | no tags | |
| update_monitor | no tags | |
| pause_monitor | no tags | |
| list_monitors | no tags | |
| get_monitor_history | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest17630e203b996286
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.4.0.
1.4.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Orbilyn can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.