# Zenfulfillment MCP by usefulapi (remote · zenfulfillment.usefulapi.io)

Read Zenfulfillment orders and stock; import or cancel orders and mark returns done.

- Trust score: 18/100 (low)
- Change this week: −44
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `zenfulfillment.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-zenfulfillment/zenfulfillment.md), [page](https://verifymcp.io/servers/io-usefulapi-zenfulfillment/zenfulfillment)

## Channel facts

- Endpoint: `https://zenfulfillment.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-zenfulfillment 'https://zenfulfillment.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-zenfulfillment": {
      "url": "https://zenfulfillment.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-zenfulfillment": {
      "type": "http",
      "url": "https://zenfulfillment.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-zenfulfillment]
url = "https://zenfulfillment.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-zenfulfillment": {
      "type": "remote",
      "url": "https://zenfulfillment.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-zenfulfillment --url 'https://zenfulfillment.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-zenfulfillment:
    url: "https://zenfulfillment.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-zenfulfillment": {
      "Transport": "http",
      "Url": "https://zenfulfillment.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-zenfulfillment -t streamable-http -u 'https://zenfulfillment.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-zenfulfillment": {
      "type": "http",
      "url": "https://zenfulfillment.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 18, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-02 (score 18, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 66, +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.

### 2026-10-31 (score 65, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] 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

### 2026-10-30 (score 62)

First indexed and scored.

## MCP tools (9)

### `zenfulfillment_list_orders` (~271 tokens)

List orders

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.

Input parameters:

- `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).

### `zenfulfillment_get_order` (~107 tokens)

Get order

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}.

Input parameters:

- `reference` (string, required): External order reference (the shop's order number).

### `zenfulfillment_list_stock` (~112 tokens)

List stock levels

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.

Input parameters:

- `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).

### `zenfulfillment_list_inventory_shipments` (~230 tokens)

List inbound shipments

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.

Input parameters:

- `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).

### `zenfulfillment_get_inventory_shipment` (~74 tokens)

Get inbound shipment

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.

Input parameters:

- `reference` (string, required): Inventory shipment ZF reference, e.g. ZF01123700.

### `zenfulfillment_list_returns` (~247 tokens)

List returns

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.

Input parameters:

- `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).

### `zenfulfillment_import_order` (~328 tokens)

Create or update an order

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.

Input parameters:

- `city` (string, required): City.
- `company` (string): Recipient company.
- `country` (string, required): 2-letter ISO country code, e.g. DE.
- `email` (string): Recipient email (carriers use it for tracking notices).
- `items` (array, required): The products to ship.
- `name` (string, required): 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, required): Your own order reference/number (for example Bestellung1). An existing reference updates that order.
- `region` (string): Region/state.
- `street` (string, required): Street and house number.
- `street2` (string): Address line 2 (c/o, floor...).
- `zip` (string, required): Postal code.

### `zenfulfillment_cancel_orders` (~99 tokens)

Cancel orders

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.

Input parameters:

- `references` (array, required): Order references to cancel (as in the Reference column, e.g. the ZF reference or your own order number).

### `zenfulfillment_mark_return_done` (~101 tokens)

Mark return as refunded

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.

Input parameters:

- `return_id` (string, required): The return's `_id` from zenfulfillment_list_returns.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-zenfulfillment/zenfulfillment#diagnostics

## Score history

- 2026-11-06: 18
- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 66
- 2026-10-31: 65
- 2026-10-30: 62

## Common questions

### 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.

## Links

- Remote endpoint: https://zenfulfillment.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/zenfulfillment/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-zenfulfillment/zenfulfillment.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-zenfulfillment/zenfulfillment/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-zenfulfillment/zenfulfillment.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-zenfulfillment/zenfulfillment