GitHub repo analytics: stars, trending, code search, contributor maps for project research.
Free
Nothing to run from here
Shipeasy 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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Feature flags, A/B experiments, kill switches, dynamic config & i18n — Shipeasy MCP server.
Quickstart
# 1 — run it from where its publisher ships it
npx -y @shipeasy/mcp
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> Feature flags, A/B experiments, kill switches, dynamic config & i18n — Shipeasy MCP server.
Publishernot claimed
SHAll 1 server
shipeasy-ai1 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. This one runs on your machine: your client starts Shipeasy as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add shipeasy-mcp -- npx -y @shipeasy/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
84 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.
Get a tracked error. Returns a single tracked error by its id, including the latest occurrence
Takes no parameters.
Example callreturns →
List tracked errors. Returns a single page of tracked production errors as a **bare JSON array** (no pagination envelope), ordered by
Takes no parameters.
Example callreturns →
Resolve a tracked error. Marks one tracked error
Takes no parameters.
Example callreturns →
Get an error
Takes no parameters.
Example callreturns →
Create a translation draft. Stage a new translation draft against a target profile, optionally seeding its keys from a source profile.
Takes no parameters.
Example callreturns →
List translation drafts. List staged translation drafts awaiting review/publish.
Takes no parameters.
Example callreturns →
Update a translation draft. Transition a draft
Takes no parameters.
Example callreturns →
List i18n keys. List keys for a profile, optionally filtered to a name
Takes no parameters.
Example callreturns →
Push i18n keys (insert-only, or
Takes no parameters.
Example callreturns →
Set a key
Takes no parameters.
Example callreturns →
Update one i18n key. Overwrite a single existing key
Takes no parameters.
Example callreturns →
Create an i18n profile. Create a locale profile.
Takes no parameters.
Example callreturns →
List i18n profiles. Returns every locale profile in the project (e.g.
Takes no parameters.
Example callreturns →
Publish a profile live. Publish a profile to the CDN — rebuild its KV snapshot + purge the edge. Publishing is PROFILE-WIDE: the whole profile is snapshotted into one KV blob, so the body takes no options.
Takes no parameters.
Example callreturns →
Archive a metric. Soft-deletes (archives) the metric. Returns
Takes no parameters.
Example callreturns →
Create a metric. Creates an event-backed metric. Pass the query as the DSL string (
Takes no parameters.
Example callreturns →
Approve a pending event. Promotes a pending (auto-discovered) event to usable so metrics can query it (
Takes no parameters.
Example callreturns →
Archive an event. Soft-deletes (archives) the event. Returns
Takes no parameters.
Example callreturns →
Register an event. Registers a new event name and (optionally) its typed properties. Only
Takes no parameters.
Example callreturns →
Get an event. Returns one event
Takes no parameters.
Example callreturns →
List events. Returns every catalogued event in the project, including pending auto-discovered names. Each row carries its own
Takes no parameters.
Example callreturns →
Update an event. Partial update of an event
Takes no parameters.
Example callreturns →
List experiments using a metric. Returns every experiment that attaches this metric — as
Takes no parameters.
Example callreturns →
List metrics. Returns every metric in the project (not paginated) — name, folder, source event, the typed
Takes no parameters.
Example callreturns →
Get a metric
Takes no parameters.
Example callreturns →
Get a metric. Fetch one metric by its id or name, including the rendered DSL query and the typed IR.
Takes no parameters.
Example callreturns →
Unarchive a metric. Reverses a soft-delete (archive), making the metric live again. Idempotent — unarchiving a metric that is already live succeeds with no effect.
Takes no parameters.
Example callreturns →
Update a metric. Update a metric
Takes no parameters.
Example callreturns →
Ack an item (start a run). Acknowledge a queue item — a person or an AI agent declaring \
Takes no parameters.
Example callreturns →
List connected AI agents. The project
Takes no parameters.
Example callreturns →
Delete an alert rule. Deletes the alert rule. The cron stops evaluating it immediately. Use this (then create a new rule) to repoint alerting at a different metric, since
Takes no parameters.
Example callreturns →
List Slack channels. List the project
Takes no parameters.
Example callreturns →
Create an alert rule. Creates a metric-threshold alert rule.
Takes no parameters.
Example callreturns →
List alert rules. Returns every alert rule in the project (not paginated). Each rule carries its bound
Takes no parameters.
Example callreturns →
Update an alert rule. Partial update of a rule
Takes no parameters.
Example callreturns →
File a bug report.. Files one queue item — a bug report or a feature request — and fires the project
Takes no parameters.
Example callreturns →
Comment on an item. Append a comment to a queue item
Takes no parameters.
Example callreturns →
List an item
Takes no parameters.
Example callreturns →
File a queue item (bug or feature request) — pass --type.. Files one queue item — a bug report or a feature request — and fires the project
Takes no parameters.
Example callreturns →
File a feature request.. Files one queue item — a bug report or a feature request — and fires the project
Takes no parameters.
Example callreturns →
List fired alerts. Returns the project
Takes no parameters.
Example callreturns →
Update a fired alert. Triage writes on one fired alert — the only mutations this surface allows. All body fields are optional (at least one required); only the fields present are changed.
Takes no parameters.
Example callreturns →
Get one queue item. Fetch a single queue item by its per-project
Takes no parameters.
Example callreturns →
Record an investigation. Append one structured investigation record to a queue item — the AI-write seam the cockpit
Takes no parameters.
Example callreturns →
List an item
Takes no parameters.
Example callreturns →
Update an investigation record. Update one existing investigation record in place — the write-back seam for the
Takes no parameters.
Example callreturns →
Link a fixing PR. Record the pull request that fixes a queue item (and clears the link with
Takes no parameters.
Example callreturns →
List the operational queue. Returns the unified ops queue (bugs, feature requests, errors, alerts) in work order — highest priority first, oldest first within a priority — so consumers work it top-down. Filter by
Takes no parameters.
Example callreturns →
Raise an attention notification. Raise a
Takes no parameters.
Example callreturns →
Register a Claude Code scheduled routine as the trigger connector. Creates (or idempotently updates) a coding-agent **trigger** connector — the recurring, unattended run that burns down the ops queue in
Takes no parameters.
Example callreturns →
Register a GitHub Copilot cloud-agent trigger. Creates (or idempotently updates) a coding-agent **trigger** connector — the recurring, unattended run that burns down the ops queue in
Takes no parameters.
Example callreturns →
Register a Cursor cloud-agent trigger (cold-fire; Shipeasy launches the run). Creates (or idempotently updates) a coding-agent **trigger** connector — the recurring, unattended run that burns down the ops queue in
Takes no parameters.
Example callreturns →
Register a Google Jules (Gemini) trigger. Creates (or idempotently updates) a coding-agent **trigger** connector — the recurring, unattended run that burns down the ops queue in
Takes no parameters.
Example callreturns →
Update a queue item. Update a queue item. The body is validated against the item
Takes no parameters.
Example callreturns →
Show the current project. Returns the project the caller
Takes no parameters.
Example callreturns →
Update the current project. Update the current project
Takes no parameters.
Example callreturns →
Delete a dynamic config. Soft-deletes the config and rebuilds the project
Takes no parameters.
Example callreturns →
Create a dynamic config. Creates a new config with the given
Takes no parameters.
Example callreturns →
Get one config. Returns config metadata plus the latest published values per env and any active draft values. Use this to fetch the JSON the editor renders.
Takes no parameters.
Example callreturns →
List dynamic configs. Returns a single page of configs ordered by
Takes no parameters.
Example callreturns →
Update a dynamic config. Partial update. When
Takes no parameters.
Example callreturns →
Update a config schema. Replaces a config
Takes no parameters.
Example callreturns →
Delete an experiment. Archives the experiment (soft-delete via status transition). Returns
Takes no parameters.
Example callreturns →
Create an experiment. Creates a new experiment in
Takes no parameters.
Example callreturns →
Get one experiment. Returns the full experiment row including groups, params, allocation, and lifecycle timestamps.
Takes no parameters.
Example callreturns →
List experiments. Returns a single page of non-archived experiments ordered by
Takes no parameters.
Example callreturns →
Mint a readout snapshot. Freezes the current results view into an immutable, dated readout snapshot — verdict, headline, per-metric numbers, the caveat list with its acknowledgment state, enrollment, and a hash of the assignment-relevant config. Ship/stop flows mint one automatically; \
Takes no parameters.
Example callreturns →
Get a readout snapshot. Returns one immutable readout snapshot — the frozen results view (verdict, headline, per-metric numbers, caveats, enrollment) captured when it was minted, plus the
Takes no parameters.
Example callreturns →
Re-queue analysis. Requeues the daily analysis pass for this experiment outside the normal cron cadence. Useful after attaching a new metric or correcting an event taxonomy. The job runs asynchronously.
Takes no parameters.
Example callreturns →
Restore an archived experiment (→ draft). Drives the experiment lifecycle. Allowed transitions:
Takes no parameters.
Example callreturns →
Get analysis results. Returns the latest analysis output for the experiment — one row per metric/group/day, including sample size, mean, % delta vs. control, p-value, and a sample-ratio mismatch flag.
Takes no parameters.
Example callreturns →
Attach metrics. Replaces the experiment
Takes no parameters.
Example callreturns →
Start an experiment (draft → running). Drives the experiment lifecycle. Allowed transitions:
Takes no parameters.
Example callreturns →
Stop a running experiment. Drives the experiment lifecycle. Allowed transitions:
Takes no parameters.
Example callreturns →
Get analysis timeseries. Same row shape as
Takes no parameters.
Example callreturns →
Delete a universe. Soft-deletes the universe. Returns
Takes no parameters.
Example callreturns →
Create a universe. Creates a new universe. Only
Takes no parameters.
Example callreturns →
List universes. Returns a single page of universes ordered by
Takes no parameters.
Example callreturns →
Update a universe. Partial update. Only
Takes no parameters.
Example callreturns →
Update an experiment. Partial update.
Takes no parameters.
Example callreturns →
Find-or-create a Shipeasy project by domain (idempotent) and bind the cwd to it via .shipeasy. Use this on fresh installs BEFORE any other write tool — every other write tool refuses to run until .shipeasy exists. Re-running with the same domain returns the existing project unchanged.
Takes no parameters.
Example callreturns →
Report whether ~/.config/shipeasy/config.json holds a valid CLI token. Returns { authenticated, project_id, base_url, user_email }.
Takes no parameters.
Example callreturns →
Launch the PKCE device-auth flow via
Takes no parameters.
Example callreturns →
Delete ~/.config/shipeasy/config.json — the ONE session shared by the
Takes no parameters.
Example callreturns →
Startermost installed
$19 / month
- 15,000 calls a month, included
- 180 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Growth
$49 / month
- 75,000 calls a month, included
- 900 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Scale
$99 / month
- 300,000 calls a month, included
- 3,600 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $19 a month covers every tool 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: $8.42
$16.58 left
ATrust score 97 / 100
Release 2.8.0 · scanned 25 Aug 2026
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 score97
Findings1 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest2b77de9c271fc9553ea828f0cbfc54721817d518c673beea85240d954d4be0a2
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can send data / act on an external service
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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest2b77de9c271fc955
Scanned2026-08-25
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
Pinned to 2.8.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
2.8.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Shipeasy in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.