asks.world MCP mainnet smoke test
The brief chain
A tiny mainnet smoke test of the asks.world MCP. One invited reviewer reads this ask and reports what it asks for.
What we are asking for
What we are asking for: read this review ask and report, in your own words, what it asks for.
What good looks like: one short finding with a screenshot, how to reproduce it, a severity with its reason, and one recommendation.
What happens to the pick: Asky Checker checks the report and the reward of 1 PAY is paid if it passes.
What is reviewed chain
- Name
- asks.world MCP mainnet smoke test
- Version
- test
- Where
- https://github.com/ixoworld/ixo-plugins
Access details for the specialists travel in their invitations, never here.
Scenarios chain
- S1Read the review ask and report what it asks for
What a report must contain chain
Requirements assessed by automated checks. A report passes all of them or is not paid.
- 01The report covers the scenarios this ask lists, each with what was done and whether it passed, failed, was blocked or was not tested.Fails if a scenario the ask lists is missing from the report altogether.
- 02Each finding points at its evidence: a screenshot, recording or trace.Fails if a finding has no evidence at all.
- 03Each problem found says how to reproduce it, or for a blocker what is missing to reproduce it.Fails if a problem gives no way to reproduce it.
- 04Each problem found has a severity: blocker, major or minor.Fails if a problem has no severity.
- 05Each recommendation says what to change.Fails if a recommendation does not say what should change.
- 06The answer is a review report, either written out or attached as a PDF.It says what was checked, when, where and what was in scope, and the outcome; lists the steps taken, each with what was expected and what was seen, passed, failed, blocked, not tested or left out; lists the findings, each with i…
Who may enter board
Only people on the list. Each invitation carries its access note privately.
Sign in to see where you stand: the builder sees and manages the list; an invited specialist sees their invitation and how to send a report. The builder's agent can invite too: give it this.
Sign in with Google to manage invitations on this page.
Reports index
0 of 1 sent. Reports go through automated checks as they arrive, until Wed 28 Oct, 12:05; the ones that pass wait for your approval. Only the builder, the specialist who wrote it and the automated checks can open a report and its screenshots; anyone can see that it was sent and how the automated checks went.
Money chain
- Per report (the specialist receives)
- 1 PAY
- Network's share
- 0.25 PAY per report, on top · 20 % as posted (10 % to the network, 10 % to the relayer node)
- Check fee
- 1 PAY per check to Asky Checker, held with the reward
- Reports
- up to 1
- Still held
- 2.25 PAY
- Paid so far
- 0 PAY
What no report earns comes back to you when the review closes.
What a specialist pastes into their agent
What this page cannot see: what the specialists are doing in your app. Their reports arrive only when they hand them in.