Smoke Run MCP server
com.getsmokerun/smoke-rungetsmokerun.comstreamable-httpv1.0.0Scanned
Free read-only teardown of a public site's money path, with the dollar at risk.
4 tools: 1 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Smoke Run MCP server can do
The Smoke Run MCP server is published by getsmokerun.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: run_revenue_check), but cannot delete data. 3 tools only read.
1 tool reads private data (get_money_system); 2 tools bring in text other people can write (run_revenue_check and get_money_system); 2 tools can send data out of your system (run_revenue_check and get_money_system). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
run_revenue_checkPurpose: run a fresh, read-only teardown of a public website's money path (landing page, call to action, lead form, checkout reachability, analytics) and report where revenue is le…Reads text others writeCan send data out1 finding
Why it is in this group
- The name "run_revenue_check" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "run_revenue_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "run_revenue_check" says "run": a word for a change.
Description, as the server wrote it Purpose: run a fresh, read-only teardown of a public website's money path (landing page, call to action, lead form, checkout reachability, analytics) and report where revenue is leaking, with dollar proof. When to use: the user gives a website address and asks whether the site is losing leads or sales, why a form or checkout may be broken, or for a free revenue audit of a site; this is the entry point for any site not yet checked. Inputs: url (required, a public website address); api_key (optional, lifts the free daily limit). Outputs: runId and a proof object with findings, each labelled confirmed (reproduced from outside), likely (inferred from the public page) or unverifiable from outside, plus a conservative monthly dollar floor on confirmed or likely findings. Limits: free and needs no key for a single check; sees only what a visitor sees; never submits a form and never completes a charge; cannot see inside a private dashboard or a payment processor account.
Annotations the server declares
- title: Run a revenue check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 3Show 3 read-only tools
get_latest_findingsPurpose: fetch the stored result of the most recent revenue check already run for one site, without running a new check.No findings
Why it is in this group
- The name "get_latest_findings" says "get": a word for reading.
Description, as the server wrote it Purpose: fetch the stored result of the most recent revenue check already run for one site, without running a new check. When to use: the user asks what the last check of a site found, or wants to compare against earlier results; not for a site that has never been checked. Inputs: siteUrl (required, the site address as previously checked). Outputs: found (boolean), runId and the dollar-proof findings of that check, or found false with a null proof when no check exists. Limits: needs a Smoke Run API key because it reads account history; read-only; returns one check only; does not fetch the live site.
Annotations the server declares
- title: Get latest findings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_money_systemPurpose: identify which revenue tools a public website is built on (payment processor, CRM or lead destination, email provider, booking tool, analytics and ad pixels) and map the f…Reads private dataReads text others writeCan send data outNo findings
Why it is in this group
- The name "get_money_system" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it Purpose: identify which revenue tools a public website is built on (payment processor, CRM or lead destination, email provider, booking tool, analytics and ad pixels) and map the funnel. When to use: the user asks what stack, payment processor, CRM or tracking a site uses, or wants a funnel map; not for finding revenue leaks (that is a teardown). Inputs: url (required, a public website address); api_key (optional). Outputs: a funnel map of detected nodes, each noting what a connected check could verify end to end. Limits: free and needs no key; detects only from the public page, so server-side tools are invisible; reports no dollar findings and does not test whether anything works.
Annotations the server declares
- title: Get money system
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_checksPurpose: list the revenue checks previously run on the authenticated Smoke Run account, newest first.No findings
Why it is in this group
- The name "list_checks" says "list": a word for reading.
Description, as the server wrote it Purpose: list the revenue checks previously run on the authenticated Smoke Run account, newest first. When to use: the user asks for their check history, which sites were checked, or which runs are at risk; not for checking a new site. Inputs: siteUrl (optional, narrows to one site); limit (optional integer 1 to 100, default 50). Outputs: checks array, each with runId, siteUrl, status (healthy, at_risk, broken or inconclusive), dollarsAtRisk, mode, startedAt and finishedAt. Limits: needs a Smoke Run API key; read-only; summaries only, without full findings; does not run or fetch anything on the live site.
Annotations the server declares
- title: List checks
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__smoke-run__get_money_system"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:22 UTC, unchanged since Nov 5, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://getsmokerun.com/api/mcp: tools/list returned 4 tools to an anonymous client, including run_revenue_check (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "run_revenue_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "run_revenue_check" says "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:get_latest_findingsOnly readsdescriptionannotations
- Changed:get_money_systemOnly readsdescriptionannotations
- Changed:list_checksOnly readsdescriptionannotations
- Changed:run_revenue_checkChanges thingsdescriptionannotations
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http smoke-run https://getsmokerun.com/api/mcpclaude mcp add --transport http smoke-run https://getsmokerun.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__smoke-run__get_latest_findings",
"mcp__smoke-run__list_checks"
],
"ask": [
"mcp__smoke-run__run_revenue_check",
"mcp__smoke-run__get_money_system"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as smoke-run. Review it before you use it.
Capability tags behind 2 rules
- mcp__smoke-run__run_revenue_check untrusted-input, outbound
- mcp__smoke-run__get_money_system private-data, untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.getsmokerun/smoke-run/verify?hash=442c30485d4e8ba65324909200bebba10d38fac03c24533e73222741a2fffbdd" | jq -e '.changed == false'Pinned hash 442c30485d4e, from Nov 18, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.getsmokerun/smoke-run/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.getsmokerun/smoke-run)Source: MCP Registry. Synced Nov 4, 2026, 08:17 UTC.
Smoke Run MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Smoke Run MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Smoke Run MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Smoke Run MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Smoke Run MCP server have?
- 4 tools: 1 write, 3 read. run_revenue_check, get_latest_findings, get_money_system and list_checks.
Does the Smoke Run MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Smoke Run MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): run_revenue_check and get_money_system.
Has the Smoke Run MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.