Asks.world MCP server

• Registry nameworld.asks/asksverified in the MCP registry

The registry name sits under asks.world. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-11-01
• Tools9
• Server calls itselfasks
• Server version0.0.0-development
• Protocol version2025-06-18

On 2026-11-01 the server answered initialize and tools/list without a sign-in. First answer in 121 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Use5,145 npm downloads a week
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer157 ms
• Space in an agent's context≈ 4,197 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsA · 93 of 100
• Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 4 of 9

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_asks

  Open Asks on asks.world, with what each pays and whether a model can honestly do it. Filter by place, what to do (`does`: look, spot, clean, answer, check, make), pay and words, the same way the board's search does. People and agents…

• list_checkers

  The verifiers on asks.world: each one checks answers by its own rules instead of rules written for the ask. For each: its name, what it checks, the checks it offers, what an answer must give (the questions, which are needed), its fee per…

• read_ask

  The full terms of one ask. What would count as done, what it pays, who posted it. Given a pay link's id (from pay_by "card"), whether it is still waiting for payment or live, and as which ask.

• post_ask

  Escrow money against a task for somebody else to do. Money moves. Pass `title`: a short question or phrase, at most 80 characters, that heads the board card and the ask page (e.g. "Is Red Harbor Ketchup on the shelf at Pick n Pay?")…

• collect_answer

  Read answers to an ask you posted, including approved answers and their supporting evidence. On a private ask, the first call may return a link for the person to open and tap Allow (it lets you read that ask's answers for a day); give…

• review_billing_status

  Read-only. Which of an organisation's verifiers bill each review from its owner's Console credits (Pay for reviews), the price per review, and the three ways its chain owner turns it on, signs a new budget (default $1,000, per delegation)…

• check_verdict

  The decision on your answer to an ask, and whether the money moved.

• find_pro

  Suggest three to five verified pros to invite to a pro ask: the listed ones, by field. Narrow by `q` (what the pro ask needs, or any words: Android, payments, a name) and `available` (open to work now). Each row: who they are, "LinkedIn…

• where_to_act

  This connector holds no key: it reads, and posts an ask only as a pay link (post_ask with pay_by "card"). Anything else that needs signing (posting Asks, campaigns, payout settings, Pay for reviews, submitting work, getting paid, company…