Model Context Protocol server for Rollbar
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.
100/100
trust score
6
downloads a day
local
runs on your machine
501
downloads in 30d
What it does
Feature flags, A/B experiments, kill switches, dynamic config & i18n — Shipeasy MCP server.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user shipeasy-mcp '--' npx -y @shipeasy/mcp
# 2 — ask your agent for something these tools do
# errors_get, errors_list, errors_resolve and 108 more
Shipeasy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SAAll 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. Its scan result is on the Security tab — 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. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user shipeasy-mcp '--' npx -y @shipeasy/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
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
111 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's stack, extras, and consequence, plus occurrences — the sampled per-instance detail rows behind the issue (newest first; exhaustive while the issue is small, thinned at volume, capped at 100). Returns…
No parameter schema on file.
List tracked errors. Returns a single page of tracked production errors as a bare JSON array (no pagination envelope), ordered by lastSeenAt desc. Filter with status, free-text-search with q, and cap the page with limit.
No parameter schema on file.
Resolve a tracked error. Marks one tracked error resolved — the single-purpose "close out" action. Takes no body; it is PATCH /api/admin/errors/{id} pinned to { "status": "resolved" }, exposed so tooling can close an error without being handed the full open/resolved/ignored status machine. A…
No parameter schema on file.
Get an error's occurrence series. Returns a bucketed occurrence timeseries for one tracked error (by its fingerprint), read from the shipeasy_errors Analytics Engine dataset (near-real-time; ingest lag is seconds). The window bounds are epoch seconds; to must be strictly greater than…
No parameter schema on file.
Create a translation draft. Stage a new translation draft against a target profile, optionally seeding its keys from a source profile.
No parameter schema on file.
List translation drafts. List staged translation drafts awaiting review/publish.
No parameter schema on file.
Update a translation draft. Transition a draft's lifecycle state (open / merged / abandoned).
No parameter schema on file.
List i18n keys. List keys for a profile, optionally filtered to a name prefix.
No parameter schema on file.
Push i18n keys (insert-only, or force to overwrite). Add NEW keys to a profile. Insert-only by default — existing keys are left untouched and reported back as skipped.
No parameter schema on file.
Set a key's value and publish it live. Upsert a single key's value into a profile and immediately publish the whole profile (KV rebuild + CDN purge) so the new value is live in one call. The key is inserted when new and overwritten when it already exists. profile is a profile name — omit it to…
No parameter schema on file.
Update one i18n key. Overwrite a single existing key's value — the only overwrite path.
No parameter schema on file.
Create an i18n profile. Create a locale profile. name is the stable handle (e.g. fr:prod).
No parameter schema on file.
List i18n profiles. Returns every locale profile in the project (e.g. en:prod, fr:prod).
No parameter schema on file.
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.
No parameter schema on file.
Archive a metric. Soft-deletes (archives) the metric. Returns 409 if it is attached to a running experiment — stop those experiments first.
No parameter schema on file.
Create a metric. Creates an event-backed metric. Pass the query as the DSL string (query) or the typed IR (query_ir) — exactly one. event_name must equal the event the query references.
No parameter schema on file.
Approve a pending event. Promotes a pending (auto-discovered) event to usable so metrics can query it (pending → 0).
No parameter schema on file.
Archive an event. Soft-deletes (archives) the event. Returns 409 if any metric still references it — delete those metrics first.
No parameter schema on file.
Register an event. Registers a new event name and (optionally) its typed properties. Only name is required.
No parameter schema on file.
Get an event. Returns one event's full detail. Resolves by exact id, unique id-prefix, or exact (unique) name.
No parameter schema on file.
List events. Returns every catalogued event in the project, including pending auto-discovered names. Each row carries its own pending flag, so the unapproved queue can be filtered client-side.
No parameter schema on file.
Update an event. Partial update of an event's folder, description, or properties. name is immutable.
No parameter schema on file.
List experiments using a metric. Returns every experiment that attaches this metric — as goal, guardrail, or secondary — ordered with running experiments first, then by role weight (goal > guardrail > secondary).
No parameter schema on file.
List metrics. Returns every metric in the project (not paginated) — name, folder, source event, the typed queryIr, and the rendered query.
No parameter schema on file.
Get a metric's time series. Compiles the metric's typed IR into Analytics Engine SQL and returns the bucketed series over the requested window (near-real-time; ingest lag is seconds). The window bounds are epoch seconds; to must be strictly greater than from. The response echoes the SQL…
No parameter schema on file.
Get a metric. Fetch one metric by its id or name, including the rendered DSL query and the typed IR.
No parameter schema on file.
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.
No parameter schema on file.
Update a metric. Update a metric's definition — folder, source event, query (query DSL or typed query_ir), winsorisation, minimum detectable effect, or direction. name is immutable. Provide at most one of query / query_ir.
No parameter schema on file.
Ack an item (start a run). Acknowledge a queue item — a person or an AI agent declaring "I'm on this now". Opens a run: stamps who picked the item up and when, assigns them as owner, and moves the item into the matching working status (investigating_by_ai for an AI ack, in_progress for a human…
No parameter schema on file.
List connected AI agents. The project's connected AI agents — one per authenticated trigger connector (Claude / Cursor / Copilot / Jules). These are the agent types ops ack accepts and the agents a queue item can be assigned to.
No parameter schema on file.
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 metricId is immutable.
No parameter schema on file.
List Slack channels. List the project's connected Slack channels — used to resolve an alert rule's notification target.
No parameter schema on file.
Create an alert rule. Creates a metric-threshold alert rule. name, metricId, comparator, and threshold are required; windowHours defaults to 24, severity to warn, and enabled to true.
No parameter schema on file.
List alert rules. Returns every alert rule in the project (not paginated). Each rule carries its bound metricId, the denormalised metricName (or null if the metric was removed), the comparator/threshold/window, severity, enabled flag, and delivery target.
No parameter schema on file.
Update an alert rule. Partial update of a rule's tunable knobs. metricId is immutable — the metric also pins the aggregation, so a body carrying metricId is rejected with 409 IMMUTABLE_FIELD; create a new rule bound to the other metric instead (rule deletion is dashboard-only).
No parameter schema on file.
File a bug report.. Files one queue item — a bug report or a feature request — and fires the project's connectors (GitHub issue / Slack). type selects which; only the two user-fileable types are accepted (error/alert tickets are auto-filed by the platform). Returns the new id and per-projec…
No parameter schema on file.
Comment on an item. Append a comment to a queue item's thread. The body is markdown (mentions like @teammate notify that person; @shipeasy asks Jarvis, the AI agent, to reply). Pass parentId to reply under an existing top-level comment (one level of threading — a reply to a reply attaches t…
No parameter schema on file.
List an item's comments. List the comment thread on a queue item, oldest first. Each comment carries its author (a teammate email, or system for a comment authored by Jarvis — the AI agent), its markdown body, and parentId for the single level of threaded replies. Removed comments are omitted.
No parameter schema on file.
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's connectors (GitHub issue / Slack). type selects which; only the two user-fileable types are accepted (error/alert tickets are auto-filed by the…
No parameter schema on file.
File a feature request.. Files one queue item — a bug report or a feature request — and fires the project's connectors (GitHub issue / Slack). type selects which; only the two user-fileable types are accepted (error/alert tickets are auto-filed by the platform). Returns the new id and…
No parameter schema on file.
List fired alerts. Returns the project's FIRED alerts as a bare JSON array (no pagination envelope), ordered by createdAt desc. Defaults to the currently-firing ones (status=active); pass a status to widen to resolved/dismissed history or all.
No parameter schema on file.
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.
No parameter schema on file.
Get one queue item. Fetch a single queue item by its per-project number or full id.
No parameter schema on file.
Record an investigation. Append one structured investigation record to a queue item — the AI-write seam the cockpit's detail panel renders read-only. Post your findings (kind: investigated), a blocking question for the team (kind: question), or how to verify the fix (kind: ready_for_qa with…
No parameter schema on file.
List an item's investigation records. The structured, read-only investigation records on a queue item — the findings / blocking questions / QA notes an AI agent posted while working it, plus its working run rows. Returns published records only, newest first (max 50).
No parameter schema on file.
Update an investigation record. Update one existing investigation record in place — the write-back seam for the working run record you were handed when a run was launched. Fill in the summary/findings, attach the fixing PR, record your confidence and the sources you inspected, or flip…
No parameter schema on file.
Link a fixing PR. Record the pull request that fixes a queue item (and clears the link with prNumber: null).
No parameter schema on file.
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 type and/or status, and cap with limit. Human-gated holding states (items…
No parameter schema on file.
Raise an attention notification. Raise a 'needs your attention' bell notification. Create-only and idempotent on dedupeKey — re-raising with the same key updates the one card instead of stacking duplicates. It never reads, marks read, or deletes the feed, so it is safe for restricted ops keys.
No parameter schema on file.
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 --pr mode. Discriminated on provider; only the four Shipeasy-fireable providers are…
No parameter schema on file.
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 --pr mode. Discriminated on provider; only the four Shipeasy-fireable providers are accepted (claude_trigger,…
No parameter schema on file.
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 --pr mode. Discriminated on provider; only the four Shipeasy-fireable providers…
No parameter schema on file.
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 --pr mode. Discriminated on provider; only the four Shipeasy-fireable providers are accepted (claude_trigger,…
No parameter schema on file.
Update a queue item. Update a queue item. The body is validated against the item's stored type: a bug accepts its content fields (title, steps-to-reproduce, actual/expected result) plus status/priority/notify and a GitHub PR link; a feature_request its content (title, description, use-ca…
No parameter schema on file.
Show the current project. Returns the project the caller's auth header resolves to — plan, status, billing, and which modules are enabled. The server reads the project from the credential, so there is no id parameter. Powers whoami.
No parameter schema on file.
Update the current project. Update the current project's settings — name, domain, slug, default environment, timezone, experiment-analysis knobs (statistical method, significance threshold, auto-rollback, minimum sample days), and the per-module enable flags. Partial: only the fields you send…
No parameter schema on file.
Delete a dynamic config. Soft-deletes the config and rebuilds the project's flags KV blob.
No parameter schema on file.
Create a dynamic config. Creates a new config with the given schema. The initial value (or an empty object) is published as version 1 on every env.
No parameter schema on file.
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.
No parameter schema on file.
List dynamic configs. Returns a single page of configs ordered by updated_at desc, id desc. Each row includes the latest published version per env and any active drafts.
No parameter schema on file.
Update a dynamic config. Partial update. When value is supplied it is republished on every env (new version per env). A per-env key (dev/staging/prod) publishes a new version to only that env, immediately, overriding value for it. When schema is supplied it replaces the current…
No parameter schema on file.
Update a config schema. Replaces a config's JSON Schema in place. Every existing published value is re-validated against the new schema before it lands; the update fails if any value no longer validates.
No parameter schema on file.
Delete an experiment. Archives the experiment (soft-delete via status transition). Returns 409 if the experiment is still running — stop it first.
No parameter schema on file.
Create an experiment. Creates a new experiment in draft status. name, universe, and groups are required; everything else has sensible defaults.
No parameter schema on file.
Get one experiment. Returns the full experiment row including groups, params, allocation, and lifecycle timestamps.
No parameter schema on file.
List experiments. Returns a single page of non-archived experiments ordered by updated_at desc, id desc. Use the cursor query parameter to paginate.
No parameter schema on file.
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; "Share…
No parameter schema on file.
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 configHash that tells you whether it is still comparable to the live view.
No parameter schema on file.
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.
No parameter schema on file.
Restore an archived experiment (→ draft). Drives the experiment lifecycle. Allowed transitions:
No parameter schema on file.
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.
No parameter schema on file.
Attach metrics. Replaces the experiment's metric attachments wholesale. Each entry pairs an existing metric_id with a role (goal / guardrail / secondary).
No parameter schema on file.
Start an experiment (draft → running). Drives the experiment lifecycle. Allowed transitions:
No parameter schema on file.
Stop a running experiment. Drives the experiment lifecycle. Allowed transitions:
No parameter schema on file.
Get analysis timeseries. Same row shape as /results, but returns every daily slice rather than the latest. Filter to a single metric with the metric query parameter.
No parameter schema on file.
Delete a universe. Soft-deletes the universe. Returns 409 if any non-archived experiment still references it — archive those experiments first.
No parameter schema on file.
Create a universe. Creates a new universe. Only name is required — unit_type defaults to user_id and holdout_range defaults to null (no holdout).
No parameter schema on file.
List universes. Returns a single page of universes ordered by created_at desc, id desc. The universes table has no updated_at, so this list is keyed on creation time.
No parameter schema on file.
Update a universe. Partial update. Only holdout_range is mutable — name and unit_type are immutable after create.
No parameter schema on file.
Update an experiment. Partial update. allocation_pct, groups, salt, universe, params are immutable while running — returns 409 if you try. Stop the experiment first.
No parameter schema on file.
List gate activity. Returns recent audit rows for one gate (create, update, enable, disable, delete) ordered newest first. Use the limit query parameter to cap the result (1–100, default 20).
No parameter schema on file.
Delete a feature gate. Soft-deletes the gate. Returns 409 if the gate is still referenced by a running experiment as a targeting gate — stop the experiment first.
No parameter schema on file.
Archive a targeting attribute. Soft-deletes (archives) a targeting attribute.
No parameter schema on file.
Declare a targeting attribute. Declare a targeting attribute the SDK reports and gates/experiments can target. type: enum requires enum_values.
No parameter schema on file.
Get a targeting attribute. Fetch one targeting attribute by id.
No parameter schema on file.
List targeting attributes. Returns every auto-inferred targeting attribute in the project — the name and (when known) the value type — for building gate/experiment targeting rules.
No parameter schema on file.
Update a targeting attribute. Update a targeting attribute's type, allowed values, required flag, description, or SDK path. name is immutable.
No parameter schema on file.
Create a feature gate. Creates a new gate. Default enabled: true at the supplied rollout_pct (0 = fully dark).
No parameter schema on file.
Disable a gate. Sets enabled: false so the gate evaluates to false for every caller, regardless of rollout_pct or rules. Use as a quick kill switch.
No parameter schema on file.
Enable a gate. Sets enabled: true. The current rollout_pct is preserved.
No parameter schema on file.
Get one gate. Returns the full gate row — including the gatekeeper stack, resolved creator/last-editor emails, and the edit version — for one gate, addressed by id or name.
No parameter schema on file.
List feature gates. Returns a single page of gates ordered by updated_at desc, id desc. Use the cursor query parameter to paginate.
No parameter schema on file.
Delete a gate template. Soft-deletes (archives) a customer template. Returns 409 if id names a read-only built-in template.
No parameter schema on file.
Create a gate template. Creates a per-project (customer) targeting-rule template. Built-ins are read-only and cannot be created here. Returns 409 if a template with this name already exists in the project.
No parameter schema on file.
Get one gate template. Returns a single template by its id — a built-in slug (country) or a customer gtpl_… id.
No parameter schema on file.
List gate templates. Returns the merged targeting-rule template catalog — read-only built-ins first (the @team/@owner audience aliases, country, email-domain, region presets, …), then this project's customer templates. Each item carries a rules: [{ attr, op, value }] definition; the …
No parameter schema on file.
Update a gate template. Partial update of a customer template. rules replaces the list wholesale. Returns 409 if id names a read-only built-in template.
No parameter schema on file.
Update a feature gate. Partial update — only supplied fields change. Array fields (rules, stack) replace wholesale; there is no merge or append.
No parameter schema on file.
Delete a killswitch. Soft-deletes the killswitch and rebuilds the project's flags KV blob so SDKs stop seeing it.
No parameter schema on file.
Create a killswitch. Creates a new killswitch with value (default false) applied to every env at version 1.
No parameter schema on file.
Get one killswitch. Returns the killswitch metadata plus the latest published value/switches/version per env.
No parameter schema on file.
List killswitches. Returns a single page of killswitches ordered by updated_at desc, id desc. Each row includes the latest published value/switches/version per env.
No parameter schema on file.
Set one switch entry. Sets or updates a single switchKey on a single env. Publishes one new version on that env only — other envs untouched.
No parameter schema on file.
Set the flat value on one env. Sets the flat value on a single env, publishing one new version on that env only. switches and other envs are untouched.
No parameter schema on file.
Remove one switch entry. Removes a single switchKey from the switches map on a single env. Publishes a new version on that env.
No parameter schema on file.
Update a killswitch. Partial update applied to every env. Setting value/switches publishes a new version per env. Description-only patches don't bump versions.
No parameter schema on file.
Show the current project. Returns the project the caller's auth header resolves to — plan, status, billing, and which modules are enabled. The server reads the project from the credential, so there is no id parameter. Powers whoami.
No parameter schema on file.
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.
No parameter schema on file.
Report whether ~/.config/shipeasy/config.json holds a valid CLI token. Returns { authenticated, project_id, base_url, user_email }.
No parameter schema on file.
Launch the PKCE device-auth flow via shipeasy login. Opens a browser; blocks up to 5 minutes. Caller should render a 'waiting for browser…' spinner.
No parameter schema on file.
Delete ~/.config/shipeasy/config.json — the ONE session shared by the shipeasy CLI and
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Shipeasy 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: —
ATrust score 100 / 100
Release 2.8.0 · scanned 15 Oct 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 score100
Findings2 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest2b77de9c271fc9553ea828f0cbfc54721817d518c673beea85240d954d4be0a2
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| 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. minimal 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. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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-10-15
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 2.8.0. Pin a release below and the command asks for exactly that one.
2.8.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 Shipeasy 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.