MCP Server

Connect Claude or any MCP client to the epc.is EPCIS 2.0 repository. Your agent queries and traces supply chain events, resolves GS1 Digital Links and checks identifiers, with your own sign-in and read-only.

https://mcp.epc.is/mcp connects Claude and any other MCP client to the epc.is EPCIS 2.0 repository. Your agent signs in with your epc.is account and reads exactly what that account may read. It traces a product, a lot or a container through every step, explains events in plain language and resolves GS1 Digital Links to their master data and linksets. Every answer names the eventIDs it rests on, so you can check it.

Add epc.is Repository to Claude Then, under Advanced settings, enter the OAuth client ID epcis-mcp and leave the secret empty.
Claude Code
claude mcp add --transport http epcis https://mcp.epc.is/mcp --client-id epcis-mcp --callback-port 8976
Endpoint: https://mcp.epc.is/mcp (Streamable HTTP, OAuth 2.1 with PKCE)

What you need

  • A free epc.is account. Every account may use the MCP server.
  • Claude (Pro, Max, Team or Enterprise for custom connectors), Claude Code, or any MCP client that speaks Streamable HTTP and OAuth 2.1 with PKCE.

Connect

Claude and Claude Desktop

  1. Click Add epc.is Repository to Claude above, or open Settings, Connectors, Add custom connector.
  2. Name epc.is Repository, URL https://mcp.epc.is/mcp.
  3. Under Advanced settings, enter the OAuth client ID epcis-mcp. Leave the client secret empty.
  4. Connect. The epc.is sign-in opens. Afterwards the tools appear in the connector menu of every chat.

Claude Code

claude mcp add --transport http epcis https://mcp.epc.is/mcp --client-id epcis-mcp --callback-port 8976

Run /mcp in a session to sign in through the browser. Claude Code keeps the token in the system keychain and refreshes it on its own.

Other MCP clients

The server follows the MCP authorization spec. Without a token it answers 401 with WWW-Authenticate: Bearer resource_metadata=... (RFC 9728), which names the authorization server https://auth.epc.is/realms/platform. Use the public client epcis-mcp with PKCE (S256) and the scopes openid and offline_access. Redirects are registered for Claude.ai and for http://localhost:8976/callback.

Tools

Every tool is read-only and carries readOnlyHint. The repository tools call the EPCIS REST API with your own token, so tenant isolation applies exactly as for any other client.

ToolWhat it does
traceBackward: what a serial, lot or SSCC was made from and packed in. Forward: what was made from it and where it went. For a returnable or individual asset (GRAI, GIAI) what it carries now and where it was last seen
query_eventsEPCIS Query Language: event type, bizStep, disposition, identifier, read point, business location, time window and any further parameter, one page at a time
get_eventOne event by its eventID, as the repository holds it
masterdataWhat the GS1 Digital Link resolver knows about a product, place or party
linksThe full linkset of a GS1 Digital Link: passport, master data, EPCIS events, instructions
validateIdentifierA GS1 identifier checked, check digit included
urnToDigitalLink, digitalLinkToUrnEPC URN and GS1 Digital Link converted both ways
listCbvTerms, findCbvTerms, describeCbvTerm, validateCbvTermThe Core Business Vocabulary with its definitions
validateEpcisDocument, checkEpcisConformance, listDocumentIdentifiersAn EPCIS 2.0 document checked against schema and rules

Prompts

Clients that show MCP prompts offer three starting points:

PromptAsks for
trace_productThe history of a serial, lot or container, backward and forward, with every eventID
explain_eventOne event explained along what, when, where, why and how
audit_lotOrigin, transformations, custody and gaps of a lot, optionally against EUDR, a Digital Product Passport or FSMA 204

Try it

  • Which events did my repository receive in the last hour?
  • Trace this lot backward and tell me where its raw materials came from.
  • Show me the links of https://id.epc.is/01/09523001010089.
  • Convert urn:epc:id:sgtin:0614141.107346.2017 to a GS1 Digital Link and check it.

Master data and linksets of the OpenEPCIS Factory products are public, so masterdata and links answer for them from any account. Events stay with the tenant that captured them.

Privacy and security

  • Your rights, nothing more. The server passes your token through to api.epc.is unchanged. It holds no service account and adds no rights.
  • Read-only by construction. The server only sends GET requests. It cannot capture, change or delete events.
  • Stateless. Nothing is stored on the MCP server. Answers go to your client and nowhere else.

Troubleshooting

SymptomCause
401 after signing inThe token was issued to another client than epcis-mcp, so it lacks the audience https://mcp.epc.is/mcp
403The account lacks the role mcp. Sign in again; write to info@benelog.com if it persists
Tools answer with no eventsYour account sees no events yet; the MCP server adds no rights to what api.epc.is shows you
Claude Code asks to sign in againSign in with /mcp; the offline_access scope keeps the session alive
Last updated: