ESGO
PYPI · ESGO-MCP
ESGO API for AI assistants: search empty-run truck capacity and publish transport requests
Available components
Last scanned (7 hours ago)
Scores higher than 61% of PyPI servers
Category Maps and Location
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ESGO-Logistics/esgo-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 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 662 tokens (~165/item across 4 items; 4 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Oct 26 64
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 5 Nov 2026 · Analysed pypi/esgo-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ESGO-Logistics/esgo-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ESGO-Logistics/esgo-mcp/.github/workflows/publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 3313748645 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d4e17a36a6864d17d01adf48b43b57e49e7de2054fc89c98c67331d01bb083d5 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| 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 →
matches_search Search matching capacity ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | 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 | yes | Origin, ideally postcode and city. |
| service_ids | array | – | Required additional services (ESGO service IDs). |
| weight_kg | number | yes | Cargo weight in kilograms. |
No output schema declared.
No examples provided.
me_retrieve Retrieve the current API key ~37
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_requests_create Create an open transport request ~253
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cargo_description | string | – | Free text for the carrier. |
| cargo_type | string | yes | Kind of cargo. |
| destination | string | yes | Destination, ideally postcode and city. |
| loading_meters | number | yes | 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 | yes | 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 | yes | Pickup time windows; at least one. |
| weight_kg | number | yes | Cargo weight in kilograms. |
No output schema declared.
No examples provided.
open_requests_list_matches List matches of an open request ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | ID of one of your open requests, as returned by open_requests_create. |
No output schema declared.
No examples provided.
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.
pypi · esgo-mcp
claude mcp add esgo-logistics-esgo-mcp -- uvx esgo-mcp
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.