Model Context Protocol server for Rollbar
Nothing to run from here
Relvato 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.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Website monitoring: add sites, configure and run monitors, read health, review results, apply fixes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http relvato-mcp https://app.relvato.com/api/mcp
# 2 — ask your agent for something these tools do
# list_sites, add_site, verify_site and 9 more
Relvato costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
REAll 1 server
relvato1 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.
claude mcp add --scope user --transport http relvato-mcp https://app.relvato.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 — but its publisher asks for a key of their own on every call.
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
12 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 the websites in this Relvato account, with whether each is ready to run checks.
No parameter schema on file.
Start monitoring a website. Returns the site and the setup step the owner must complete before any check runs: connect the WordPress plugin, or verify the domain (the only option for non-WordPress sites). If the account already has a site on the same domain, that site is returned instead of a duplicate.
No parameter schema on file.
Check whether the site's ownership is proven: probes the WordPress plugin connection and/or looks for the domain-verification DNS TXT record / meta tag. Returns the updated setup state.
No parameter schema on file.
Plain-language health verdict for a site: what needs attention (real issues vs likely false positives), each check with its latest run and schedule, setup state, recommended checks not yet added, and the account's run usage.
No parameter schema on file.
The checks that can be added to a site: key, what it catches, whether the current plan allows it, whether it's recommended for this site, and whether it's already added.
No parameter schema on file.
Add checks to a site by key (from list_checks). Each key reports added / exists / rejected with the reason (plan, active-check limit, needs the WordPress plugin). New checks run on their default triggers: a weekly (some daily) schedule, plus a re-run when the site changes (WordPress plugin updates, or pushes via the GitHub App).
No parameter schema on file.
Turn a check on or off, or change its schedule. Only the fields you pass change. Schedules faster than daily need a paid plan.
No parameter schema on file.
Run a site's enabled checks now — or one check with checkId, even if it's turned off. Each run counts toward the monthly run quota. Returns the runIds to follow with get_run.
No parameter schema on file.
Recent runs, newest first — optionally for one site. Each has the check (checkId, its key as journey, checkName), status, trigger, timing and its error / warning; get_run has the detail.
No parameter schema on file.
One run in detail: status, error and warnings (ignored ones marked), each step, visual comparisons, metrics, and the dashboard link where the user can review or accept changes. Large metrics are compacted, never the findings: daily series become summaries and what was left out is listed in metricsTrimmed.
No parameter schema on file.
For a run that failed or found a problem: the same brief Relvato's own AI answers when the user clicks "Suggest a fix" — the site's detected stack, what the check verifies, what changed on the site just before, the exact error and findings, whether it was already failing earlier, and for Google / Bing Search the evidence that rules causes out. Use it as context to explain the likely cause and fixe
No parameter schema on file.
Who is told about what: how often (instant, daily / weekly digest), the minimum severity, each channel (email, Slack, webhook — whether the plan includes it, whether it's set up, paused, and on = alerts actually go out on it), which sites are muted and which check types go to which channel (only channels that are on). Never includes webhook URLs or secrets. Changing them is done by the user in A
No parameter schema on file.
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 Relvato 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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 3.2.0.
3.2.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 Relvato 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.