# ESGO (pypi · esgo-mcp)

ESGO API for AI assistants: search empty-run truck capacity and publish transport requests

- Trust score: 64/100 (medium)
- Change this week: −15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `esgo-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/esgo-logistics-esgo-mcp/esgo-mcp.md), [page](https://verifymcp.io/servers/esgo-logistics-esgo-mcp/esgo-mcp)

## Channel facts

- Registry: `pypi`
- Package: `esgo-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to ESGO-Logistics/esgo-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 662 tokens (~165/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the ESGO MCP server?

ESGO runs locally as a PyPI package, launched with uvx esgo-mcp. 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 esgo-logistics-esgo-mcp -- uvx esgo-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "esgo-logistics-esgo-mcp": {
      "command": "uvx",
      "args": [
        "esgo-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "esgo-logistics-esgo-mcp": {
      "command": "uvx",
      "args": [
        "esgo-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add esgo-logistics-esgo-mcp -- uvx esgo-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "esgo-logistics-esgo-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "esgo-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add esgo-logistics-esgo-mcp --command uvx --arg esgo-mcp
```

### Hermes

```yaml
mcp_servers:
  esgo-logistics-esgo-mcp:
    command: "uvx"
    args: ["esgo-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "esgo-logistics-esgo-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "esgo-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add esgo-logistics-esgo-mcp -t stdio -c uvx -a esgo-mcp
```

### Other

```json
{
  "mcpServers": {
    "esgo-logistics-esgo-mcp": {
      "command": "uvx",
      "args": [
        "esgo-mcp"
      ]
    }
  }
}
```

## 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-05 (score 64, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-19 (score 64)

First indexed and scored.

## MCP tools (4)

### `matches_search` (~180 tokens)

Search matching capacity

Search matching capacity

Finds trips whose route, time and free capacity fit your shipment. Prices are non-binding estimates; a fixed price is the standing offer of the carrier. Counts against the daily quota "matches_search".

Required API key scope: matches:read.

Input parameters:

- `destination` (string, required): Destination, ideally postcode and city.
- `loading_meters` (number|null): Loading meters needed (max 13.6).
- `loading_requirement` (string): How the cargo has to be loaded. "any" never filters; "seite" (side) and "oben" (top) exclude box bodies; "heck" means rear loading.
- `origin` (string, required): Origin, ideally postcode and city.
- `service_ids` (array): Required additional services (ESGO service IDs).
- `weight_kg` (number, required): Cargo weight in kilograms.

### `me_retrieve` (~37 tokens)

Retrieve the current API key

Retrieve the current API key

Use this call to check that your key works and how many calls are left today. It needs no scope.

### `open_requests_create` (~253 tokens)

Create an open transport request

Create an open transport request

Posts a transport request that carriers on ESGO see. ESGO matches it against existing trips right away and against every new trip later. Counts against the daily quota "open_requests_create". Not retried automatically: a repeated call creates a second request.

Required API key scope: open_requests:write.

Input parameters:

- `cargo_description` (string): Free text for the carrier.
- `cargo_type` (string, required): Kind of cargo.
- `destination` (string, required): Destination, ideally postcode and city.
- `loading_meters` (number, required): Loading meters needed (max 13.6).
- `loading_requirement` (string): How the cargo has to be loaded. "any" never filters; "seite" (side) and "oben" (top) exclude box bodies; "heck" means rear loading.
- `origin` (string, required): Origin, ideally postcode and city.
- `service_ids` (array): Required additional services (ESGO service IDs).
- `target_price_eur` (number|null): Optional target price in EUR shown to carriers as orientation.
- `time_windows` (array, required): Pickup time windows; at least one.
- `weight_kg` (number, required): Cargo weight in kilograms.

### `open_requests_list_matches` (~76 tokens)

List matches of an open request

List matches of an open request

Trips ESGO has matched to one of your open requests, best first. Reading them does not mark them as seen in the dashboard.

Required API key scope: open_requests:read.

Input parameters:

- `request_id` (string, required): ID of one of your open requests, as returned by open_requests_create.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/esgo-logistics-esgo-mcp/esgo-mcp#diagnostics

## Score history

- 2026-11-05: 64
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 64
- 2026-10-27: 64
- 2026-10-26: 64
- 2026-10-25: 64
- 2026-10-24: 64
- 2026-10-23: 64
- 2026-10-22: 64
- 2026-10-21: 64
- 2026-10-20: 64
- 2026-10-19: 64

## Common questions

### What is the ESGO MCP server?

ESGO is an MCP server listed in the public MCP registry as io.github.ESGO-Logistics/esgo-mcp. ESGO API for AI assistants: search empty-run truck capacity and publish transport requests. This page covers its PyPI package (esgo-mcp).

### Is the ESGO MCP server safe to use?

ESGO scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 ESGO MCP server expose?

ESGO exposes 4 tools: matches_search, me_retrieve, open_requests_create, open_requests_list_matches. Their descriptions and schemas cost roughly 546 tokens of context every time the server is loaded.

### Is the ESGO MCP server still maintained?

ESGO is still listed as active in the MCP registry. We last reached this channel on 5 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 ESGO MCP server under?

ESGO declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/esgo-mcp/
- Socket report: https://socket.dev/pypi/package/esgo-mcp
- Repository: https://github.com/ESGO-Logistics/esgo-mcp
- Website: https://es-go.de/developers
- Changelog RSS feed: https://verifymcp.io/servers/esgo-logistics-esgo-mcp/esgo-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/esgo-logistics-esgo-mcp/esgo-mcp.json
- HTML version of this page: https://verifymcp.io/servers/esgo-logistics-esgo-mcp/esgo-mcp