agentPickup
REMOTE · AGENTPICKUP.APP · 2 COMPONENTS
Find pickup shops near you, order, pay by card or USDC (x402), and get the QR to collect in person.
Available components
Last scanned (16 hours ago)
Scores higher than 53% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category E-commerce
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 −1
- Endpoint reachability: reachable → unreachable ▼ security
- TLS certificate: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 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 5 Nov 2026 · Probed https://agentpickup.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentpickup.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| agentpickup.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentpickup.app/mcp | Unreachable | ||
| http (plaintext) | http://agentpickup.app/mcp | HTTPS enforced |
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 →
create_pickup_order Order for pickup ~112
Create an order to collect in person. Returns the order id and total; pay it with pay_order. The shop emails the pickup QR to `email` once it's paid.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email. The pickup QR goes here. | |
| items | array | yes | – |
| name | string | – | Name for the order, shown to staff |
| shop_url | string | – | An agentPickup shop's URL, as find_shops returns it. Defaults to https://agentpickup.app. |
No output schema declared.
No examples provided.
find_shops Find pickup shops ~200
Find agentPickup shops to order from: near a point (lat/lng), in a suburb or city (place), or selling something (query). Returns each shop's shop_url, pickup address, hours, whether it's open now, distance, and matching menu items.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Where the user is: latitude. Send with lng. |
| limit | integer | – | – |
| lng | number | – | Where the user is: longitude. Send with lat. |
| open_now | boolean | – | Only shops open now (shops without listed hours stay in). |
| place | string | – | A suburb, street or city to match against shop addresses, e.g. "Surry Hills". |
| query | string | – | What the user wants, e.g. "flat white" or "croissant". Leave out to list everything. |
| radius_km | number | – | With lat/lng: how far to look. Default 10. |
No output schema declared.
No examples provided.
get_pickup_pass Get the pickup pass ~75
The pass link, pickup code and QR content for an order this wallet paid, by signing in with the wallet (Sign-In-With-X).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
| shop_url | string | – | An agentPickup shop's URL, as find_shops returns it. Defaults to https://agentpickup.app. |
No output schema declared.
No examples provided.
get_shop See what a shop sells ~57
What the shop sells (item ids and prices), where to collect, and which payments it takes.
| Name | Type | Req | Description |
|---|---|---|---|
| shop_url | string | – | An agentPickup shop's URL, as find_shops returns it. Defaults to https://agentpickup.app. |
No output schema declared.
No examples provided.
order_status Check an order ~63
Whether an order is waiting for payment, paid, ready to collect, collected or expired.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
| shop_url | string | – | An agentPickup shop's URL, as find_shops returns it. Defaults to https://agentpickup.app. |
No output schema declared.
No examples provided.
pay_order Pay for an order ~107
Pay an order in USDC over x402 from wallet 0xd253e213cE143Aa0E1e1cAfc92f7AE82c98aB3bB. This spends money: confirm the items and total with the user first. Returns the pickup pass link.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
| shop_url | string | – | An agentPickup shop's URL, as find_shops returns it. Defaults to https://agentpickup.app. |
No output schema declared.
No examples provided.
How do I install the agentPickup MCP server?
agentPickup is a hosted endpoint at https://agentpickup.app/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 · agentpickup.app
claude mcp add --transport http dav3trad3r-agentpickup 'https://agentpickup.app/mcp'
What is the agentPickup MCP server?
agentPickup is an MCP server listed in the public MCP registry as io.github.dav3trad3r/agentpickup. Find pickup shops near you, order, pay by card or USDC (x402), and get the QR to collect in person. This page covers its hosted endpoint (https://agentpickup.app/mcp).
Is the agentPickup MCP server safe to use?
agentPickup scores 68 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 agentPickup MCP server expose?
agentPickup exposes 6 tools: find_shops, get_shop, create_pickup_order, pay_order, order_status, get_pickup_pass. Their descriptions and schemas cost roughly 614 tokens of context every time the server is loaded.
Does the agentPickup MCP server require authentication?
Its publisher declares no required credentials for agentPickup. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the agentPickup MCP server still maintained?
agentPickup is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the agentPickup MCP server?
VerifyMCP ran 3 checks on agentPickup, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about agentPickup: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.