MCP server for web scraping, structured data extraction, and screenshots — give Claude, Cursor, Windsurf, and AI agents the ability to
Tools
explain_cron
Turns a five-field cron expression into a sentence, and shows what each field expanded to. Reads *, lists, ranges and steps, and the usual three-letter month and day names.
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
—
p95 latency
—
call success
—
uptime 90d
2
calls last 7d
What it does
This listing exists for one purchase and one payout. It answers cron questions like the free server beside it — what a line means, when it fires next, whether two schedules collide — and it is priced only so that a real subscription, a real platform fee and a real transfer can be watched end to end before the marketplace opens. It is removed as soon as that is done.
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add payout-qa-mcp
# 2 — ask your agent something
> A paid listing used once to prove money reaches a publisher.
PublisherVerified · since 2026
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 — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codenot declared — it may still work
Claude Code has its own MCP command, and the key rides on it as a header — the gateway refuses a call that carries none. Put your key from Access in $MCPRUSH_KEY, or let npx mcprush@latest add payout-qa-mcp write the same entry for you.
claude mcp add --transport http payout-qa-mcp https://mcprush.com/gw/payout-qa-mcp/mcp \
--header "Authorization: Bearer $MCPRUSH_KEY"Reconnect, 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 pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
What you approve
3 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.
Turns a five-field cron expression into a sentence, and shows what each field expanded to. Reads *, lists, ranges and steps, and the usual three-letter month and day names.
No parameter schema on file.
The next times a cron line fires, in UTC. A schedule that can never fire — 30 February and its friends — comes back as an empty list rather than as a hang.
No parameter schema on file.
Takes two cron lines and reports the first minute in the next year when both fire — the question behind "why did the backup and the report start together at 03:00 on the first".
No parameter schema on file.
Teammost installed
$19 / month
- 25,000 calls a month, included
- No rate limit
- 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
—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 a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
Pinned to 0.1.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.
0.1.0
2 Sep 2026
installed- The version this listing went live with, after review.
5.0
1 reviews
Reviews are earned
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.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Payout QA 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.
ILilliahaidarverified install
3 days ago
perfect mcp!perfect mcp, thanks!
mcpdevpropublisher
Thank you — the cron parser is the part I care most about, so that is good to hear. If a schedule ever comes back wrong, send me the line and I will fix it in the next version.