# Epc MCP server

Source: https://glimind.com/server/mcp-registry%2Fis.epc%2Fmcp
Registry id: `mcp-registry/is.epc/mcp`
Status: live (checked 2026-11-22T15:02:36.062Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 411
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "epc-mcp-server": {
      "type": "http",
      "url": "https://mcp.epc.is/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http epc-mcp-server https://mcp.epc.is/mcp
```

## Tools (18)

- `checkEpcisConformance`: Score an EPCIS document across every conformance dimension at once, including whether it used the identifiers it was given. Use this as a final self-check befor
- `describeCbvTerm`: Get the CBV's own definition of a term, and its example of use. Use this to confirm that a term means what you think before putting it in a document — the defin
- `digitalLinkToUrn`: Convert a GS1 Digital Link URI into the legacy EPC URN form. Supply the GCP (company prefix) length if you know it; pass 0 to let the resolver determine it. Onl
- `dpp`: The Digital Product Passport of a product, Lot or Serial by its GS1 Digital Link, from the DPP API (EN 18223 structure). Read with the user's sign-in, so the fi
- `findCbvTerms`: Find candidate CBV terms for an EPCIS event field by matching words from a description of what happened. Returns the terms whose names share a word stem with th
- `get_event`: One EPCIS event by its eventID, exactly as the repository holds it (JSON-LD), for the signed-in user.
- `links`: The full GS1 Digital Link linkset of an identifier: every link type the resolver serves for it (product passport, master data, EPCIS repository, instructions an
- `listCbvTerms`: List every standard CBV term for an EPCIS event field. Use this instead of recalling terms from memory — the list is small, closed, and generated from the CBV s
- `listDocumentIdentifiers`: List the identifiers an EPCIS document actually uses, grouped by the field that carries them. Use this to check at a glance that a document is about the objects
- `masterdata`: What the GS1 Digital Link resolver knows about a product (GTIN, Lot, Serial), a place (GLN, SGLN) or a party (PGLN): name, description, brand, location and the 
- `query_events`: Query the EPCIS 2.0 repository as the signed-in user, who sees exactly what their account may read. Filters are EPCIS Query Language parameters; every one is op
- `summarize`: Count the signed-in user's EPCIS events, computed by the repository in one call, grouped by one dimension: eventType, bizStep, disposition, readPoint, bizLocati
- `trace`: Trace a Serial, Lot or container through the repository as the signed-in user. backward: what it was made from (the TransformationEvents that output it, then th
- `urnToDigitalLink`: Convert a legacy EPC URN (urn:epc:id:sgtin:0614141.107346.2017) into the preferred GS1 Digital Link URI form. Use this whenever you have a URN but want to emit 
- `validateCbvTerm`: Check whether a value is a standard CBV term for an EPCIS event field, before putting it in a document. Returns VALID, or NOT STANDARD with the nearest standard
- `validateEpcisDocument`: Check an EPCIS 2.0 JSON document against the GS1 schema AND the OpenEPCIS rules — the same two validators the capture endpoint runs. Call this on every document
- `validateIdentifier`: Check whether a GS1 identifier is valid, including its mod-10 check digit. Accepts a GS1 Digital Link URI (https://id.gs1.org/01/09521000002159/21/SER-1) or an 
- `verify_credential`: Verify a Verifiable Credential (JSON-LD with a Data Integrity proof, a VC-JOSE compact JWS or an SD-JWT VC) with the platform's verifier: signature, issuer DID 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
