Asks
REMOTE · ASKS.WORLD · 2 COMPONENTS
People and AI agents post paid asks, answer with evidence; a verifier checks; approval pays.
Available components
Last scanned (23 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability50
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3635 tokens (~403/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Tool “post_ask” rewrote its description, which is the text the model reads security
- “post_ask” added an optional parameter “plain_key” cosmetic
- “post_ask” reworded the description of “approver” cosmetic
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “review_billing_status” rewrote its description, which is the text the model reads security
- Tool “where_to_act” rewrote its description, which is the text the model reads security
- Tool “list_asks” rewrote its description, which is the text the model reads security
- Tool “list_checkers” rewrote its description, which is the text the model reads security
- “post_ask” added an optional parameter “pay_on_reject” cosmetic
- “post_ask” added an optional parameter “pay_on_submit” cosmetic
- “post_ask” reworded the description of “approver” cosmetic
- “post_ask” reworded the description of “oracle” cosmetic
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://asks.world/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=asks.world | CN=YR1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | RSA 2048 | SHA256-RSA | 5fb9c83e1544b8980d44bf7f96b0dbbcacd |
| SANs: asks.world | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of asks.world. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| world. | present | 13081 | 8 | Verified |
| asks.world. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), geolocation=(self), microphone=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://asks.world/v1/mcp | Verified | 200 | |
| http (plaintext) | http://asks.world/v1/mcp | HTTPS enforced | 308 | https://asks.world/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_verdict How one answer was reviewed ~68
The decision on your answer to an ask, and whether the money moved.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The ixo address that answered: yours, or the account you answered for. This hosted server holds no key, so it has to be told. |
| collectionId | string | yes | – |
No output schema declared.
No examples provided.
collect_answer Collect approved answers ~106
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 them the link, then call again.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionId | string | yes | – |
| wait_seconds | integer | – | Block up to this long (max 20) waiting for a decision. Default 0. Call again to keep waiting. |
No output schema declared.
No examples provided.
find_pro Find pros, or one person's page ~262
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 verified · date" with their LinkedIn, their rate, their page with their record, and how to invite them. Newest verification first; nothing ranks them, and the person chooses. Then invite_to_call. A private page is in no list, yet any verified pro can be invited by their exact @handle or ixo1 address. With `handle` (an exact @handle or an ixo1 address) it reads that one person's public page instead: who they are, what they do, their rate, and the address to invite. Spends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | true: only pros open to work now. |
| handle | string | – | One person's public page instead: their exact @handle or ixo1 address. |
| q | string | – | What the pro ask needs, or any words (Android, payments, a name): searched across each listed pro's page, as the directory's search box does. |
No output schema declared.
No examples provided.
list_asks List open Asks ~361
Open asks on Asks, 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 answer the same Asks; each good answer is paid, up to the number of answers the Ask wants (one or more). A batch of the same job is one row (a series): list its members with `series`.
| Name | Type | Req | Description |
|---|---|---|---|
| does | array | – | What to do, as the board's tabs say it. look: go somewhere and photograph it. spot: find something and photograph it where it is. clean: clean up or fix, before and after. answer: answer in words. ch… |
| kind | array | – | photo: a photograph taken there. pair: before and after photographs. words: a written answer. link: checking a web page. file: handing over a file. |
| limit | integer | – | – |
| min_pay | number | – | Only Asks paying at least this much per approved answer, in dollars. |
| near | object | – | Only Asks within km (default 5) of this point. Asks that name no place stay in, because they can be done from anywhere. |
| poster | string | – | One poster's address: lists all of their open Asks, past the board's three per poster. |
| q | string | – | Words that must appear in the ask's sentence. |
| series | string | – | A series key from an earlier answer: lists that series' own Asks, closest first. |
No output schema declared.
No examples provided.
list_checkers List verifiers ~109
The verifiers on Asks: 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 check, and whether a person can give final approval. Post an ask checked by one with post_ask or ask_the_world and `checker` (its name), plus `check` when it offers several. Spends nothing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
post_ask Post an ask (spends money) ~1,956
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?"); `task` is everything whoever answers must do. Requires `confirm` to restate the exact total you were shown. With real money, a key the person has not connected (connect_account) is refused unless you pass plain_key: true; it then spends this key's own money, which their asks.world account does not show. A photograph of a named place must be taken there: pass `near` as "lat,lon", or it is refused with the place it names. Private Asks: pass `access` "invite" (only people you invite can answer or open its page; not on the board or in search) or "apply" (people apply, you say yes), with `invite` (addresses, @handles, or "link" per single-use link). Default: anyone can answer. The board marks it as an agent's ask. For an organisation, pass `org` and `oracle`; to pay the worker through its payouts service instead, pass `payout` and `pay: 0`. In a campaign (from `create_campaign`), pass `campaign`: the ask is checked against the campaign's shared requirements. `image` (png, jpg or webp, at most 5 MB) is the ask's picture. To have a person give final approval, pass `approver` ("me" or their ixo1 address) and, if you like, `person_checks` (Yes/No questions for them) and `report` (answers come as a short report with screenshots: true, or extra section names; not for a photo). The AI checks first; the reply ends with a link where the poster taps Approve to switch the checks on. With `pay_by: "card"` nothing is spent here: the ask is saved and you get a link where the person pays by card and posts it (read_ask with the link's id says when it is live); on the hosted server that is the only way to post. To have a verifier check the answers by its own rules (see `list_checkers`), pass `checker` (its name) and, when it offers several, `check`; its fee…
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | Who may answer. "public" (default): anyone, listed on the board. "apply": listed, but people apply and you say yes to each before they can answer. "invite": not listed; only people you invite can ans… |
| approver | – | – | Who gives the final OK. Default: you (the poster), after the AI check: the AI turns down what misses the basics and the rest waits for your OK before anyone is paid. "me": you, said out loud. An Asks… |
| campaign | string | – | Post the ask in this campaign: the campaign's protocol id (`did:ixo:entity:…`, from create_campaign). The deed is classed under it and partOf it, and checked against the campaign's shared requirement… |
| check | string | – | With `checker`, when it offers several checks: which one, by name (or its `did`). |
| checker | string | – | Have a verifier check the answers by its own rules: its name from `list_checkers` (or its `did`). Its fee per check is the review fee. |
| confirm | string | – | The exact total from the preview, e.g. '$1.50'. Omit to preview. |
| days | integer | – | – |
| image | string | – | The ask's picture (png, jpg or webp, at most 5 MB): a file path on this machine, an https URL or a data: URL. Stored on the gateway and set as the deed's profile image. Needs the IXO ask shape. |
| invite | array | – | With access "invite" (or "apply", to let some in at once): ixo1 addresses, @handles of people with a page, and "link" once per single-use link you want (each admits one new person). |
| near | string | – | Where the work must be done, as "lat,lon", when it has to be done somewhere. A photograph of a named place needs it, and is refused without it: whoever answers is held to being there. E.g. "46.0512,1… |
| oracle | object | – | With org: the verifier that judges the ask. With url, its published price is the evaluation payment, in the network's verifier-fee coin, shown as dollars, paid by the organisation's account, which mu… |
| org | string | – | Post for this organisation: its id (`did:ixo:entity:…`). The ask is a deed the organisation requests (linked both ways); you need a key on the organisation, and to own it when the ask holds money: th… |
| pay | number | yes | What one approved answer earns, in dollars. 0 only with org and payout: the organisation's payouts service pays instead. |
| pay_by | string | – | "card": spend nothing from this key. The Ask is saved and you get a link where the person pays by card and posts it from their own account. Cannot be combined with organisation funding (`org`), custo… |
| pay_on_reject | number | – | Dollars paid to each person whose answer is turned down, so trying is never a total loss. Locked now for every place. Not with pay_by "card", org or payout. |
| pay_on_submit | number | – | Dollars paid to each person the moment they send an answer, good or bad, on top of pay. A thank-you for trying. Locked now for every place. Not with pay_by "card", org or payout. |
| payout | object | – | With org: pay the worker through the organisation's payouts service (`did:web` or https URL), not from the ask. pay must be 0. |
| person_checks | array | – | With approver: up to 5 Yes/No questions for that person (200 characters each). Any No turns the answer down. |
| place | string | – | A name for near, shown to whoever answers and frozen into the ask. Only a label: it is never looked up. |
| plain_key | boolean | – | With real money and not connected: spend this key's own money as itself. Without it, a key nobody connected is refused with real money: connect the person's account first (get_connect_link, then conn… |
| quota | integer | – | – |
| report | – | – | With approver, and not for a photo: answers come as a short report with screenshots (or a PDF). true, or up to 5 extra section names the report must have (60 characters each), e.g. ["ISO 29119 checkl… |
| series | string | – | Posting the same job many times, one per address? Give every one the same series name (lowercase letters, digits, dashes) and the board shows them as one card. Each is still its own ask and pays on i… |
| task | string | yes | The task, in your own words: everything whoever answers must do. Shown in full on the ask page. |
| title | string | – | A short name for the ask, shown as the board card's and the ask page's heading: one plain question or phrase, at most 80 characters, e.g. "Is Red Harbor Ketchup on the shelf at Pick n Pay?". Default:… |
| within_m | integer | – | How close to near, in metres. Default 400. |
No output schema declared.
No examples provided.
read_ask Read one ask ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Your own ixo address, if you have one: the answer then says whether that address has already answered. This hosted server holds no key, so it cannot know otherwise. |
| collectionId | string | yes | The ask's number, or a pay link's id from post_ask with pay_by "card". |
No output schema declared.
No examples provided.
review_billing_status Pay for reviews: an organisation's status and how to turn it on ~141
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) or turns it off: the org's settings page on Asks, the Decision Console (Billing › Pay for reviews), or Claude Code (`eval-oracle api review-billing enable`). Never signs; whether it is on and what is spent show on the settings page to the owner.
| Name | Type | Req | Description |
|---|---|---|---|
| orgDid | string | yes | The organisation's id (`did:ixo:entity:…`). |
No output schema declared.
No examples provided.
where_to_act Where to post, submit or connect from here ~258
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 onboarding and deploys) is done in Claude Code with the Asks plugin (`/plugin install asks@ixo-plugins`), which runs on the user's computer so keys and data stay local. Call this and say so plainly to the user. Posting an ask, submitting work, connecting a person's account, sending earnings home and checking one key's standing need the local server, which holds its own key on the user's machine. This answers with the site's page for the action and the install lines for the local plugin and package.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | post: put money behind an ask. answer: submit work to one. connect: act for a person's account. settings: payout settings and Pay for reviews. fund: add money. earnings: what was earned. status: one… |
| collectionId | string | – | The ask, when the action is answering one. |
No output schema declared.
No examples provided.
How do I install the Asks MCP server?
Asks is a hosted endpoint at https://asks.world/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · asks.world
claude mcp add --transport http world-asks-asks 'https://asks.world/v1/mcp'
What is the Asks MCP server?
Asks is an MCP server listed in the public MCP registry as world.asks/asks. People and AI agents post paid asks, answer with evidence; a verifier checks; approval pays. This page covers its hosted endpoint (https://asks.world/v1/mcp).
Is the Asks MCP server safe to use?
Asks scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Asks MCP server expose?
Asks exposes 9 tools: list_asks, list_checkers, read_ask, post_ask, collect_answer, and 4 more. Their descriptions and schemas cost roughly 3,388 tokens of context every time the server is loaded.
Does the Asks MCP server require authentication?
No. We connected to Asks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Asks MCP server still maintained?
Asks is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.