Zenfulfillment MCP by usefulapi
REMOTE · ZENFULFILLMENT.USEFULAPI.IO
Read Zenfulfillment orders and stock; import or cancel orders and mark returns done.
Available components
Last scanned (11 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 the endpoint redirected instead of responding directly. 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 (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
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.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- 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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 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.
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: fail → pass ▲ functional
- New prompt “check_inbound_deliveries” functional
- New prompt “find_low_stock_skus” functional
- New prompt “mark_a_processed_return_done” functional
- New prompt “send_an_order_for_fulfillment” functional
- New prompt “track_orders_and_shipments” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.2.0 → 1.4.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.1 → 1.1.0 functional
- 30 Oct 26 62
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 · Probed https://zenfulfillment.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of zenfulfillment.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | 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 |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zenfulfillment.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/zenfulfillment/ |
| http (plaintext) | http://zenfulfillment.usefulapi.io/mcp | Inconclusive | 302 | http://zenfulfillment.usefulapi.io/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 →
zenfulfillment_cancel_orders Cancel orders ~99
WRITE, cannot be undone: cancel orders by reference (up to 50). Only orders that can still be cancelled (before the warehouse has packed or shipped them) are cancelled; the others come back in `errors`. Confirm the references with the user first. POST /orders/cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| references | array | yes | Order references to cancel (as in the Reference column, e.g. the ZF reference or your own order number). |
No output schema declared.
No examples provided.
zenfulfillment_get_inventory_shipment Get inbound shipment ~74
One inbound inventory shipment by its ZF reference (for example ZF01123700): SKU lines with announced and arrived quantities and the note. GET /inventory_shipments/export/{reference}/reference.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Inventory shipment ZF reference, e.g. ZF01123700. |
No output schema declared.
No examples provided.
zenfulfillment_get_order Get order ~107
One order by its EXTERNAL reference, i.e. the order number from the connected shop or from your own import (for example 332-11-5599), with addresses, products with quantities (ordered, shipped, returned, refunded) and shipments with tracking numbers. Not the ZF reference: use zenfulfillment_list_orders with query for that. GET /orders/external/{reference}.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | External order reference (the shop's order number). |
No output schema declared.
No examples provided.
zenfulfillment_import_order Create or update an order ~328
WRITE: send ONE order to the Zenfulfillment warehouse for picking, packing and shipping to the given address (fulfillment and shipping fees apply per the contract). The reference is your own order number: a reference that already exists UPDATES that order instead of creating a new one. Each item becomes one CSV row (Reference;Date;Name;Company;Street1;Street2;Zip Code;City;Region;Country;Email;Phone;SKU;Quantity). Use SKUs from zenfulfillment_list_stock. Check the address with the user first. In test mode nothing ships. POST /orders/import.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City. |
| company | string | – | Recipient company. |
| country | string | yes | 2-letter ISO country code, e.g. DE. |
| string | – | Recipient email (carriers use it for tracking notices). | |
| items | array | yes | The products to ship. |
| name | string | yes | Recipient name. |
| order_date | string | – | Order date, yyyy-mm-dd (default today, UTC). |
| phone | string | – | Recipient phone number. A leading + is sent as 00 (international prefix) so spreadsheets never read it as a formula. |
| reference | string | yes | Your own order reference/number (for example Bestellung1). An existing reference updates that order. |
| region | string | – | Region/state. |
| street | string | yes | Street and house number. |
| street2 | string | – | Address line 2 (c/o, floor...). |
| zip | string | yes | Postal code. |
No output schema declared.
No examples provided.
zenfulfillment_list_inventory_shipments List inbound shipments ~230
List inbound inventory shipments (goods you sent to the warehouse) with reference, SKU lines, announced quantity, quantity arrived and note. Filter by ONE status, created/updated time or free text (ZF number, tracking code, type). Rows are grouped per shipment. Paging as in list_orders. GET /inventory_shipments/export.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only shipments created at or after this time. |
| created_before | string | – | Only shipments created at or before this time. |
| page | integer | – | Page number, from 1 (default 1). Use the previous reply's next_page. |
| per_page | integer | – | Results per page, 10-50 (default 25). |
| query | string | – | Free-text search: ZF number, tracking code, type. |
| status | string | – | Only shipments in this status (one at a time). |
| updated_after | string | – | Lower bound on the last update time (updatedAtMin). |
| updated_before | string | – | Upper bound on the last update time (updatedAtMax). |
No output schema declared.
No examples provided.
zenfulfillment_list_orders List orders ~271
List or search the fulfillment orders of this Zenfulfillment account (warehouse pick/pack/ship), with status, order reference, shop order number, totals, shipping and billing address, the products ordered/shipped and shipments (tracking number, carrier). Filter by ONE status, created/updated time or free text. The export has one row per product line; rows are grouped into orders. Paging: pass next_page back as page; an empty page is the end. GET /orders/export.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only orders created at or after this time. |
| created_before | string | – | Only orders created at or before this time. |
| page | integer | – | Page number, from 1 (default 1). Use the previous reply's next_page. |
| per_page | integer | – | Results per page, 10-50 (default 25). |
| query | string | – | Free-text search: shipping street, city, country, zip, customer name, order number or ZF number. |
| status | string | – | Only orders in this status (one at a time). |
| updated_after | string | – | Lower bound on the last update time (updatedAtMin). |
| updated_before | string | – | Upper bound on the last update time (updatedAtMax). |
No output schema declared.
No examples provided.
zenfulfillment_list_returns List returns ~247
List returns processed by the warehouse (PROCESSED = received, DONE = marked refunded), with the return's `_id` (needed by zenfulfillment_mark_return_done), ZF reference, note, products with quantity, reason, condition and whether they were actually returned, and the original order. Filter by ONE status, time or free text. Paging as in list_orders. GET /returns/export.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only returns created at or after this time. |
| created_before | string | – | Only returns created at or before this time. |
| page | integer | – | Page number, from 1 (default 1). Use the previous reply's next_page. |
| per_page | integer | – | Results per page, 10-50 (default 25). |
| query | string | – | Free-text search: street, city, country, zip, customer name, order number or ZF number. |
| status | string | – | Only returns in this status. |
| updated_after | string | – | Lower bound on the last update time (updatedAtMin). |
| updated_before | string | – | Upper bound on the last update time (updatedAtMax). |
No output schema declared.
No examples provided.
zenfulfillment_list_stock List stock levels ~112
Stock on hand in the Zenfulfillment warehouse per SKU (sku, quantity_on_stock). Filter by SKU text and/or a maximum quantity to find low stock (then sorted lowest first). GET /products/export.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most SKUs to return (default 200). |
| max_quantity | integer | – | Only SKUs with at most this many units on stock (use for low-stock checks). |
| sku_contains | string | – | Only SKUs containing this text (case-insensitive). |
No output schema declared.
No examples provided.
zenfulfillment_mark_return_done Mark return as refunded ~101
WRITE: set a return's status to DONE (refunded) in Zenfulfillment. Zenfulfillment only records the status; refund the customer in your shop yourself. Use the `_id` from zenfulfillment_list_returns (not the ZF reference). Cannot be set back through the API. POST /returns/{returnId}/done.
| Name | Type | Req | Description |
|---|---|---|---|
| return_id | string | yes | The return's `_id` from zenfulfillment_list_returns. |
No output schema declared.
No examples provided.
How do I install the Zenfulfillment MCP by usefulapi server?
Zenfulfillment MCP by usefulapi is a hosted endpoint at https://zenfulfillment.usefulapi.io/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 · zenfulfillment.usefulapi.io
claude mcp add --transport http io-usefulapi-zenfulfillment 'https://zenfulfillment.usefulapi.io/mcp'
What is the Zenfulfillment MCP by usefulapi server?
Zenfulfillment MCP by usefulapi is listed in the public MCP registry as io.usefulapi/zenfulfillment. Read Zenfulfillment orders and stock; import or cancel orders and mark returns done. This page covers its hosted endpoint (https://zenfulfillment.usefulapi.io/mcp).
Is the Zenfulfillment MCP by usefulapi server safe to use?
Zenfulfillment MCP by usefulapi scores 18 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 Zenfulfillment MCP by usefulapi server expose?
Zenfulfillment MCP by usefulapi exposes 9 tools: zenfulfillment_list_orders, zenfulfillment_get_order, zenfulfillment_list_stock, zenfulfillment_list_inventory_shipments, zenfulfillment_get_inventory_shipment, and 4 more. Their descriptions and schemas cost roughly 1,569 tokens of context every time the server is loaded.
Does the Zenfulfillment MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Zenfulfillment MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Zenfulfillment MCP by usefulapi server still maintained?
Zenfulfillment MCP by usefulapi 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 did VerifyMCP test on the Zenfulfillment MCP by usefulapi server?
VerifyMCP ran 4 checks on Zenfulfillment MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Zenfulfillment MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 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.