Smoke Run
com.getsmokerun/smoke-runVersion 1.0.0Free read-only teardown of a public site's money path, with the dollar at risk.
Status
Responds299 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:59 UTC
- Latency
- 299 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://getsmokerun.com/api/mcpResponds299 msNo sign-in
Claude Code
claude mcp add --transport http smoke-run https://getsmokerun.com/api/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: smoke-run
Remote MCP server URL: https://getsmokerun.com/api/mcpCursor
{
"mcpServers": {
"smoke-run": {
"url": "https://getsmokerun.com/api/mcp"
}
}
}VS Code
code --add-mcp '{"name":"smoke-run","type":"http","url":"https://getsmokerun.com/api/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
4 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
get_latest_findingsPurpose: 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. | No | Yes | Yes | No |
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 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. | No | Yes | Yes | Yes |
list_checksPurpose: 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. | No | Yes | Yes | No |
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 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. | No | Yes | Yes | Yes |
Details
- Registry status
- Active
- Published
- Nov 4, 2026
- Updated
- Nov 4, 2026
- Repository
- Not given
- Categories (suggested)
- Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared