Errand
REMOTE · ERRAND.BE
Dispatch nearby humans for on-site checks, photos, pickups and queues with verified evidence.
Available components
Last scanned (56 minutes ago)
Scores higher than 97% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1038 tokens (~148/item across 7 items; 7 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Tool “errand_get_result” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 70. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 63. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 53. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://errand.be/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=errand.be | CN=YR2,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | RSA 2048 | SHA256-RSA | 69eb4d8a50d981f0b09c05eb1348d643fdc |
| SANs: errand.be | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 errand.be. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| be. | present | 45588 | 13 | Verified |
| errand.be. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://errand.be/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://errand.be/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://errand.be/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://errand.be/api/mcp |
| Authorisation server | https://ekygxbccwbwcppkbpetc.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://errand.be/api/mcp | Verified | 200 | |
| http (plaintext) | http://errand.be/api/mcp | HTTPS enforced | 308 | https://errand.be/api/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 →
errand_cancel Cancel Human Dispatch ~54
Cancel a real-world human dispatch while it is still open and refund the escrow in full. Fails once a worker has accepted and may already be traveling.
| Name | Type | Req | Description |
|---|---|---|---|
| dispatch_id | string | yes | Id returned by errand_dispatch. |
No output schema declared.
No examples provided.
errand_check_coverage Check Local Human Coverage ~106
Check whether a nearby human can be dispatched to a physical location before spending. Returns reachable_workers (switched on, seen within 24h — these get the push) and online_workers (app open this minute). Use for on-site or store checks, photos, queues, pickups, and other real-world tasks when you need current human availability.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lng | number | yes | – |
| radius_m | integer | – | Default 3000. |
No output schema declared.
No examples provided.
errand_dispatch Dispatch Human to Physical Location ~355
Send a nearby real human to a physical location for on-site verification, store/shelf/price checks, photos, queue checks or holding, or a pickup. This spends money and creates a real-world action: call errand_quote first, present its exact total_charge_krw, and obtain explicit user confirmation. The worker travels to the site, completes the instructions, and submits GPS/time-verified in-app evidence. Completed tasks pay the worker; failed, expired, or pre-acceptance cancelled tasks refund escrow.
| Name | Type | Req | Description |
|---|---|---|---|
| address_hint | string | – | Human-readable place name/address shown to the worker. |
| expires_in_minutes | integer | yes | – |
| instructions | string | yes | Exactly what the worker should do on site, in the worker's language. |
| lat | number | yes | – |
| lng | number | yes | – |
| radius_m | integer | yes | Dispatch radius for worker matching. |
| report_fields | array | – | Structured values the worker must report from the site (e.g. how many people are waiting). Returned in the result and included in the webhook. |
| reward_krw | integer | yes | – |
| task_type | string | yes | – |
| title | string | yes | Short worker-facing title, e.g. "성수동 XYZ 팝업 대기줄 확인". |
| validation_criteria | string | yes | What the photos must show for the evidence to pass, e.g. "매장 입구와 대기줄 전체가 한 프레임에 보여야 함". |
| webhook_url | string | – | HTTPS URL that receives mission.completed / mission.failed / mission.cancelled / mission.expired events, so you do not have to poll. Payload is advisory — confirm via errand_get_result. |
No output schema declared.
No examples provided.
errand_get_result Get Verified On-Site Result ~96
Retrieve the verified on-site result from a human task: pass/fail verdict, score and feedback, signed photo URLs, structured answers, and evidence provenance including GPS distance, capture time, and server checks. Also returns share_url: a read-only result page (valid 30 days, no login) you can send to the person who asked for the check.
| Name | Type | Req | Description |
|---|---|---|---|
| dispatch_id | string | yes | Id returned by errand_dispatch. |
No output schema declared.
No examples provided.
errand_get_status Get Human Task Status ~68
Track a previously dispatched local human task: open · accepted · arrived · submitted · completed · failed · cancelled · expired, plus its event timeline. Use after errand_dispatch while the person is traveling or working on site.
| Name | Type | Req | Description |
|---|---|---|---|
| dispatch_id | string | yes | Id returned by errand_dispatch. |
No output schema declared.
No examples provided.
errand_list_capabilities Errand Capabilities ~63
Use before a local-human or physical-world task to see what Errand can do for this account: supported on-site task types (check, verify, photograph, queue, pickup), spend caps, allowed area, KRW balance, and pricing. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
errand_quote Quote Real-World Human Task ~129
Get the exact read-only quote for sending a human to a real-world location for a check, verification, photo, queue task, or pickup. Validates account caps, live worker coverage, and balance; returns reward_krw, platform_fee_krw, and exact total_charge_krw. Present that total to the user and obtain explicit confirmation before errand_dispatch.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lng | number | yes | – |
| radius_m | integer | – | Default 3000. |
| reward_krw | integer | yes | – |
| task_type | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Errand MCP server?
Errand is a hosted endpoint at https://errand.be/api/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 · errand.be
claude mcp add --transport http be-errand-errand 'https://errand.be/api/mcp'
What is the Errand MCP server?
Errand is an MCP server listed in the public MCP registry as be.errand/errand. Dispatch nearby humans for on-site checks, photos, pickups and queues with verified evidence. This page covers its hosted endpoint (https://errand.be/api/mcp).
Is the Errand MCP server safe to use?
Errand scores 89 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 Errand MCP server expose?
Errand exposes 7 tools: errand_list_capabilities, errand_check_coverage, errand_quote, errand_dispatch, errand_get_status, and 2 more. Their descriptions and schemas cost roughly 871 tokens of context every time the server is loaded.
Does the Errand MCP server require authentication?
Yes. Errand asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Errand MCP server still maintained?
Errand is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.