# Peppol (npm · @pipeworx/mcp-peppol)

Peppol participant lookup (SML + SMP + Peppol Directory).

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-peppol/peppol-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-peppol/peppol-mcp)
- npm · `@pipeworx/mcp-peppol`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-peppol/pipeworx-mcp-peppol.md), [page](https://verifymcp.io/servers/pipeworx-io-peppol/pipeworx-mcp-peppol)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-peppol`
- Version: `0.2.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**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-peppol).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 776 tokens (~258/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 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 Peppol MCP server?

Peppol runs locally as an npm package, launched with npx -y @pipeworx/mcp-peppol. 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 pipeworx-io-peppol -- npx -y @pipeworx/mcp-peppol
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-peppol": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-peppol"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-peppol": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-peppol"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-peppol -- npx -y @pipeworx/mcp-peppol
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-peppol": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-peppol"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-peppol --command npx --arg -y --arg @pipeworx/mcp-peppol
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-peppol:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-peppol"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-peppol": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-peppol"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-peppol -t stdio -c npx -a -y @pipeworx/mcp-peppol
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-peppol": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-peppol"
      ]
    }
  }
}
```

## 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 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 79)

First indexed and scored.

## MCP tools (3)

### `lookup_participant` (~281 tokens)

Check whether a company is registered on the Peppol e-invoicing network and list every document type it accepts. Resolves the participant identifier through the Peppol SML (DNS/BDXL) to its SMP, then reads the SMP ServiceGroup — the authoritative registration check, keyless, no Peppol membership needed. Returns registered=false with the reason when the identifier has no SML record. Use search_participants first if you have a company name rather than an identifier.

Input parameters:

- `environment` (string): "production" (default) queries the live Peppol network. "test" queries the pilot SML (acc.edelivery.tech.ec.europa.eu).
- `participantId` (string, required): Peppol participant identifier as "{schemeCode}:{value}", e.g. "0208:1021916675" (Belgian company number), "0192:989995278" (Norwegian org number), "0088:7300010000001" (GLN). The leading 4-digit sche…
- `scheme` (string): Identifier scheme. Effectively always the default "iso6523-actorid-upis"; only override for a non-standard network.

### `get_participant_endpoint` (~254 tokens)

Get the AS4 delivery details a sender needs for one specific document type: transport profile, receiving endpoint URL, process identifier, and the service activation/expiration window. Call lookup_participant first to get the exact documentTypeId to pass here. An expired ServiceExpirationDate means the participant is listed but that document type is no longer deliverable.

Input parameters:

- `documentTypeId` (string, required): Full document type identifier value exactly as lookup_participant returned it in documentTypes[].value, e.g. "urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#…
- `documentTypeScheme` (string): Document type scheme, default "busdox-docid-qns".
- `environment` (string): "production" (default) or "test".
- `participantId` (string, required): Peppol participant identifier, e.g. "0192:989995278".
- `scheme` (string): Participant identifier scheme, default "iso6523-actorid-upis".

### `search_participants` (~187 tokens)

Search the Peppol Directory (directory.peppol.eu, OpenPEPPOL's opt-in business-card index) by company name, VAT/organisation number or country to find a participant identifier. Use this to turn a company name into the "{schemeCode}:{value}" identifier that lookup_participant needs. Registration on the network does not require publishing a business card, so absence here is not proof a company is not on Peppol — confirm with lookup_participant.

Input parameters:

- `country` (string): Optional 2-letter ISO country code filter, e.g. "NO", "BE", "DE".
- `limit` (number): Max matches to return, 1-100. Default 10.
- `q` (string, required): Free-text query: company name, VAT number, or organisation number, e.g. "Atelier OSLO" or "1021916675".

## Diagnostics

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

## Score history

- 2026-11-05: 79
- 2026-11-04: 79

## Common questions

### What is the Peppol MCP server?

Peppol is an MCP server listed in the public MCP registry as io.github.pipeworx-io/peppol. Peppol participant lookup (SML + SMP + Peppol Directory). This page covers its npm package (@pipeworx/mcp-peppol).

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

Peppol scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Peppol MCP server expose?

Peppol exposes 3 tools: lookup_participant, get_participant_endpoint, search_participants. Their descriptions and schemas cost roughly 722 tokens of context every time the server is loaded.

### Is the Peppol MCP server still maintained?

Peppol 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 Peppol MCP server under?

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

### What did VerifyMCP test on the Peppol MCP server?

VerifyMCP ran 15 checks on Peppol, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Peppol: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-peppol
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-peppol
- Repository: https://github.com/pipeworx-io/mcp-peppol
- Website: https://pipeworx.io/packs/peppol
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-peppol/pipeworx-mcp-peppol.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-peppol/pipeworx-mcp-peppol/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-peppol/pipeworx-mcp-peppol.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-peppol/pipeworx-mcp-peppol