agentPickup
NPM · @AGENTPICKUP/MCP · 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 (11 hours ago)
Scores higher than 31% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 116 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (FSL-1.1-ALv2) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1319 tokens (~131/item across 10 items; 10 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 Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% 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 11 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 5 Nov 26 −5
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Source repository: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.3.0 → 0.3.1 functional
- 4 Nov 26 +11
- Tool safety: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Schema quality: 732 → 1289 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → 0.89 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.3.0 functional
- 3 Nov 26 55
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 6 Nov 2026 · Analysed npm/@agentpickup/mcp@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 116 packages
| Packages resolved | 116 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
close_group_order Close a group order now ~79
Close a group order early, as its organiser. Unpaid shares are left out; the shop gets the rest as one order.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| organiser_key | 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.
create_pickup_order Order for pickup ~185
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. Where the shop takes cards, `payment: "card"` returns a checkout link for the user to pay on instead.
| 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 |
| payment | string | – | Who pays: agent (USDC over x402, or a test payment at a test shop) or card (the user pays on a checkout link). Default: agent where the shop takes it, else card. |
| 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.
group_order_status Check a group order ~69
Who's in a group order, what they ordered, who has paid, and whether it has closed and been collected.
| Name | Type | Req | Description |
|---|---|---|---|
| code | 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.
join_group_order Join a group order ~129
Add the user's items to a group order with its code. Returns the order id; pay it with pay_order before the group closes. The organiser collects everything, so the user gets a receipt, not a QR.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The group's code |
| string | yes | The user's email, for their receipt | |
| items | array | yes | – |
| name | string | yes | The user's name, shown to staff on their items |
| 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 ~68
No wallet is set up here, so this returns the price and pay link for another x402 client to pay.
| 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.
start_group_order Start a group order ~143
Start a group order (a coffee run) at a shop. Returns a code to share: each person's agent joins with it and pays for their own items. When it closes, the shop gets one combined order and the organiser is emailed its pickup QR.
| Name | Type | Req | Description |
|---|---|---|---|
| closes_in_minutes | integer | – | Default 15 |
| organiser_email | string | yes | Where the group's pickup QR goes |
| organiser_name | string | yes | Who collects, shown to staff |
| shop_url | string | – | An agentPickup shop's URL, as find_shops returns it. Defaults to https://agentpickup.app. |
| title | string | – | e.g. "Friday coffee run" |
No output schema declared.
No examples provided.
How do I install the agentPickup MCP server?
agentPickup runs locally as an npm package, launched with npx -y @agentpickup/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @agentpickup/mcp
claude mcp add dav3trad3r-agentpickup -- npx -y @agentpickup/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 npm package (@agentpickup/mcp).
Is the agentPickup MCP server safe to use?
agentPickup scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. 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 10 tools: find_shops, get_shop, create_pickup_order, pay_order, order_status, and 5 more. Their descriptions and schemas cost roughly 1,068 tokens of context every time the server is loaded.
Is the agentPickup MCP server still maintained?
agentPickup is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the agentPickup MCP server under?
agentPickup declares the FSL-1.1-ALv2 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the agentPickup MCP server?
VerifyMCP ran 16 checks on agentPickup, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.