Argo Hub Picking y Packing
REMOTE · WWW.ARGOHUB.ES
Calculate parcel preparation hours and average capacity using your own time assumptions.
Available components
Last scanned (16 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Data and Analytics
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 Security100
- 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, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 286 tokens (~286/item across 1 items; 1 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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 (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 +70
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Nov 26 6
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 21 Nov 2026 · Probed https://www.argohub.es/mcp/picking-packing
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.argohub.es | CN=YR2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 5235fbbf4e87405191d8a726ad3369d447e |
| SANs: www.argohub.es | ||||||
| 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 secure
Validation of www.argohub.es. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| es. | DS published | 4901, 54404 | 8, 8 | Verified |
| argohub.es. | DS published | 31516 | 13 | Verified |
| www.argohub.es. | Verified address RRset verified with the apex keys |
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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.argohub.es/mcp/picking-packing | Verified | 200 | |
| http (plaintext) | http://www.argohub.es/mcp/picking-packing | HTTPS enforced | 308 | https://www.argohub.es/mcp/picking-packing |
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 →
calculate_picking_workload Ecommerce picking and packing workload calculator ~208
Calculate parcel preparation hours and average capacity needs from parcels, minutes per parcel, other work and available productive hours. It does not model shifts, concurrency, learning curves, carrier cutoffs or the actual daily workload distribution. Check peaks before sizing resources. It does not estimate payroll savings or recommend hiring or dismissal. Freed founder hours do not automatically represent cash savings. Input fields: parcels: An order shipped in two boxes counts as two parcels. minutesPerParcel: Measure picking, packing and labelling without double counting the next field. otherMinutes: Receipts, inventory checks and work excluded above. 0 if absent. workingDays: The average does not represent campaign peaks. productiveHours: Optional. Time available for all scenario tasks after breaks and unrelated duties. Blank means no staffing estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| minutesPerParcel | number | yes | – |
| otherMinutes | number | yes | – |
| parcels | integer | yes | – |
| productiveHours | number | – | – |
| workingDays | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| limitations | array | yes | – |
| method | array | yes | – |
| metrics | object | yes | – |
| pendingFields | array | yes | – |
| sources | array | yes | – |
| status | string | yes | – |
| tool | string | yes | – |
| vatIncluded | boolean | – | – |
No examples provided.
How do I install the Argo Hub Picking y Packing MCP server?
Argo Hub Picking y Packing is a hosted endpoint at https://www.argohub.es/mcp/picking-packing, 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 · www.argohub.es
claude mcp add --transport http es-argohub-www-picking-packing 'https://www.argohub.es/mcp/picking-packing'
What is the Argo Hub Picking y Packing MCP server?
Argo Hub Picking y Packing is an MCP server listed in the public MCP registry as es.argohub.www/picking-packing. Calculate parcel preparation hours and average capacity using your own time assumptions. This page covers its hosted endpoint (https://www.argohub.es/mcp/picking-packing).
Is the Argo Hub Picking y Packing MCP server safe to use?
Argo Hub Picking y Packing scores 80 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 Argo Hub Picking y Packing MCP server expose?
Argo Hub Picking y Packing exposes 1 tool: calculate_picking_workload. Their descriptions and schemas cost roughly 208 tokens of context every time the server is loaded.
Does the Argo Hub Picking y Packing MCP server require authentication?
No. We connected to Argo Hub Picking y Packing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Argo Hub Picking y Packing MCP server still maintained?
Argo Hub Picking y Packing is still listed as active in the MCP registry. We last reached this channel on 21 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 Argo Hub Picking y Packing MCP server?
VerifyMCP ran 13 checks on Argo Hub Picking y Packing, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.