Try the asks.world MCP on testnet and report where it fails
We are testing the new asks.world MCP server on testnet. Try three short scenarios with the asks plugin and tell us what broke, what confused you and what worked.
What we are asking for
What we are asking for: one review report of the asks.world MCP on testnet, covering each scenario with the steps you took.
What good looks like: exact commands, what the tool said back, and where it failed or confused you. Testnet only, play money.
Start your AI here
The poster's suggested first message. Use it, change it, or write your own.
I'm taking part in the IXO Expert Review "Try the asks.world MCP on testnet and report where it fails". Show me what the review asks for, then help me try each scenario and keep notes and screenshots as I go: what I did, what I expected and what I saw. Write up my findings with me, each with how serious it is and how to reproduce it, and my recommendations. Show me all of it, and hand it in as my report only when I say so.
The terms. Everything below was frozen on chain with the money: the poster cannot change the requirements, the pay, who may enter or the dates after the first entry.
What to send
- Your entryOne page of text in your own words, at least 200 characters. Cover the five requirements below.
- Two ways inWith your AI through the asks.world MCP, or on the web. The reviewer reads both the same way.
- How oftenOne entry per account.
- Who may enterOnly the people the poster invited: by a link that admits one person, by address, or by their page. The call is not listed.
The money is locked before anyone enters
- Each entry hired1 PAY eachEvery entry that passes all five requirements, up to 1, paid with its decision. Nobody is picked: this is the whole call
- The reviewer1 PAY a rulingPaid from the pot for every entry it rules on, whatever it rules
- Locked on chain now0 PAY
Locked in 1 asks on asks.world: #44147. Nobody can move it to anyone but the people the reviewer pays. What is not paid goes back to ixo1ew49er…qrtn after the close.
What the reviewer rules on
Your entry must meet all five requirements to qualify for payment.
- 1The 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.
- 2Each finding points at its evidence: a screenshot, recording or trace.Fails if a finding has no evidence at all.
- 3Each 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.
- 4Each problem found has a severity: blocker, major or minor.Fails if a problem has no severity.
- 5Each recommendation says what to change.Fails if a recommendation does not say what should change.
- 6The answer is a review report (written out, or attached as a PDF) of what this ask asked to be reviewed.Fails if there is no report, or it plainly reviews something else.
How every entry is judged
- 1Your entry is filed on chain, with its hash, the moment you send it.
- 2The reviewer checks your entry against all five requirements, usually within minutes. The IXO decision engine signs the decision.
- 3If your entry meets all five requirements, approval releases payment. Anyone can read the decision and its explanation.
1 entry so far
1 met the bar and was paid 1 PAY. What each entry says stays with its author and the poster; every decision is public now.
The reviewer scores how well each entry meets the requirements, out of 100. Scores rank the entries that meet all requirements.