Skip to content

epc.is EPCIS Repository MCP server

is.epc/mcpepc.isstreamable-httpv2026.11.1Scanned

EPCIS 2.0 repository: trace products, query and count events, resolve GS1 Digital Links.

18 tools: 8 change things and 10 only read.

Tools: 0 delete, 0 irreversible, 8 write, 10 read.
  • Reads private data · 4
  • Reads text others write · 1
  • Can send data out · 0
  • 8 findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the epc.is EPCIS Repository MCP server can do

The epc.is EPCIS Repository MCP server is published by epc.is, a domain the MCP Registry verified. It has 18 tools. It can create or change data (8 tools: checkEpcisConformance, digitalLinkToUrn, dpp, links and 4 more), but cannot delete data. 10 tools only read.

4 tools read private data (get_event, listDocumentIdentifiers, query_events and 1 more); 1 tool brings in text other people can write (verify_credential).

The fixed checks matched 8 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 2026.11.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

18 tools

Changes things 8Claude Code: ask
  • checkEpcisConformanceScore an EPCIS document across every conformance dimension at once, including whether it used the identifiers it was given.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 before presenting a document to a user. Pass suppliedText as what the user actually told you, verbatim — their whole request is fine. This is the only way to detect a FABRICATED identifier, which passes every other check and yet describes a different physical object. Leave it empty only when the user genuinely supplied nothing.

    Annotations the server declares

    • title: Check EPCIS conformance
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • digitalLinkToUrnConvert a GS1 Digital Link URI into the legacy EPC URN form.1 finding

    Why it is in this group

    • The name "digitalLinkToUrn" says "link": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "digitalLinkToUrn" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "digitalLinkToUrn" says "link": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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. Only use URNs when the user explicitly asks for them — Digital Link is the preferred form.

    Annotations the server declares

    • title: Digital Link to EPC URN
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • dppThe Digital Product Passport of a product, Lot or Serial by its GS1 Digital Link, from the DPP API (EN 18223 structure).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 fields their access tier allows are included. representation: compressed (default), operational, full, gs1 or eu.

    Annotations the server declares

    • title: Digital Product Passport
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • masterdataWhat 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 like, as the platfor…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 like, as the platform publishes it.

    Annotations the server declares

    • title: Master data of an identifier
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • traceTrace a Serial, Lot or container through the repository as the signed-in user.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 their inputs, level by level) and the container it was packed in; forward: what was made from it and what it was packed into, down to where each result was last seen. Every step names its eventID, Read Point and time. A Lot is class level (/10/), a Serial or SSCC instance level. A returnable asset (GRAI, /8003/) or an individual asset (GIAI, /8004/), such as a minecart, a pack donkey or a bottle, answers what it carries now (every ADD minus every DELETE of the AggregationEvents it is the parent of), where it was last seen and its latest events.

    Annotations the server declares

    • title: Trace a product, lot or container
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • verify_credentialVerify 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 and key, status (rev…Reads text others write5 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The title mentions "credential".

      Matched text

      title: "Verify a credential"

      What this check looks for
    • Info

      The annotations title mentions "credential".

      Matched text

      annotations.title: "Verify a credential"

      What this check looks for
    • Info

      The description mentions "Credential".

      Matched text

      description: "Verify a Verifiable Credential (JSON-LD with a Data Integrity proof, a..."

      What this check looks for
    • Info

      The input schema at properties.credential.description mentions "credential".

      Matched text

      inputSchema.properties.credential.description: "the credential: a JSON-LD object as JSON text, a compa..."

      What this check looks for
    • Info

      The input schema at required[0] mentions "credential".

      Matched text

      inputSchema.required[0]: "credential"

      What this check looks for
    Description, as the server wrote it
    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 and key, status (revoked or suspended) and the trust of the issuer. Answers valid true or false with the stage-by-stage verdict. The credential is sent to the verifier as given; nothing is stored.

    Annotations the server declares

    • title: Verify a credential
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
Only reads 10Show 10 read-only tools
  • describeCbvTermGet the CBV's own definition of a term, and its example of use.No findings

    Why it is in this group

    • The name "describeCbvTerm" says "describe": a word for reading.
    Description, as the server wrote it
    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 definitions are the standard's text, not a paraphrase.

    Annotations the server declares

    • title: Describe a CBV term
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • findCbvTermsFind candidate CBV terms for an EPCIS event field by matching words from a description of what happened.No findings

    Why it is in this group

    • The name "findCbvTerms" says "find": a word for reading.
    Description, as the server wrote it
    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 the description, most specific first, or the whole list when nothing matches. This is a NAME match, not a semantic one: it narrows the choice, it does not make it. Two terms can both look plausible for the same sentence — `collecting` and `receiving` are the known example — and only the CBV definitions settle that. Read the returned candidates as a shortlist to reason about, and prefer being explicit with the user over guessing between near-synonyms.

    Annotations the server declares

    • title: Find CBV terms
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_eventOne EPCIS event by its eventID, exactly as the repository holds it (JSON-LD), for the signed-in user.Reads private dataNo findings

    Why it is in this group

    • The name "get_event" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    One EPCIS event by its eventID, exactly as the repository holds it (JSON-LD), for the signed-in user.

    Annotations the server declares

    • title: Get one EPCIS event
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • listCbvTermsList every standard CBV term for an EPCIS event field.No findings

    Why it is in this group

    • The name "listCbvTerms" says "list": a word for reading.
    Description, as the server wrote it
    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 standard, and a term that is not on it will be rejected when the document is captured.

    Annotations the server declares

    • title: List CBV terms
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • listDocumentIdentifiersList the identifiers an EPCIS document actually uses, grouped by the field that carries them.Reads private dataNo findings

    Why it is in this group

    • The name "listDocumentIdentifiers" says "list": a word for reading.

    What it can reach

    • private-dataThe name "listDocumentIdentifiers" says "list" and "document": it reads documents.
    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    Description, as the server wrote it
    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 and places you intended, without reading the whole JSON.

    Annotations the server declares

    • title: List identifiers in a document
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • query_eventsQuery the EPCIS 2.0 repository as the signed-in user, who sees exactly what their account may read.Reads private dataNo findings

    Why it is in this group

    • The name "query_events" says "query": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "query" and "repository": it reads repositories.
    Description, as the server wrote it
    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 optional and they are AND-ed, several values of one comma-separated are OR-ed. Identifiers are GS1 Digital Links (https://id.gs1.org/01/<gtin>/21/<serial>, /10/<lot>, /00/<sscc>, /414/<gln>/254/<ext>) or EPC URNs. Answers one page, newest first, each event compact with its eventID; pass nextPage back for more.

    Annotations the server declares

    • title: Query EPCIS events
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • summarizeCount the signed-in user's EPCIS events, computed by the repository in one call, grouped by one dimension: eventType, bizStep, disposition, readPoint, bizLocation, action, day or m…Reads private dataNo findings

    Why it is in this group

    • The name "summarize" says "summarize": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "count" and "repository": it reads repositories.
    Description, as the server wrote it
    Count the signed-in user's EPCIS events, computed by the repository in one call, grouped by one dimension: eventType, bizStep, disposition, readPoint, bizLocation, action, day or month. Takes the same filters as query_events. Use it for "how many", "which steps", "per day" questions instead of paging through events; then query_events for the events behind a bucket.

    Annotations the server declares

    • title: Summarize events
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • validateCbvTermCheck whether a value is a standard CBV term for an EPCIS event field, before putting it in a document.No findings

    Why it is in this group

    • The name "validateCbvTerm" says "validate": a word for reading.
    Description, as the server wrote it
    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 term when the value is a known near-miss. Use this whenever you are not certain of a term. EPCIS 2.0 JSON requires the bare short name (`shipping`), never the EPCIS 1.x URN (`urn:epcglobal:cbv:bizstep:shipping`) and never the CBV URI (`https://ref.gs1.org/cbv/BizStep-shipping`) — all three are checked here and only the first is accepted.

    Annotations the server declares

    • title: Validate a CBV term
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • validateEpcisDocumentCheck an EPCIS 2.0 JSON document against the GS1 schema AND the OpenEPCIS rules — the same two validators the capture endpoint runs.No findings

    Why it is in this group

    • The name "validateEpcisDocument" says "validate": a word for reading.
    Description, as the server wrote it
    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 you produce, before you present it; a document that fails here will be rejected on capture. Reports the two layers separately, because they are different properties: the schema permits things that are wrong in this architecture, such as `ilmd` on a serialised item. Repairs are listed as things for YOU to fix, not applied. A document that needed a repair is a document whose shape was wrong.

    Annotations the server declares

    • title: Validate an EPCIS document
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • validateIdentifierCheck whether a GS1 identifier is valid, including its mod-10 check digit.No findings

    Why it is in this group

    • The name "validateIdentifier" says "validate": a word for reading.
    Description, as the server wrote it
    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 EPC URN (urn:epc:id:sgtin:...). Use this before putting any identifier into an EPCIS document. Never guess a check digit and never derive a new identifier by changing a digit of an existing one — ask this tool instead.

    Annotations the server declares

    • title: Validate a GS1 identifier
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:20 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.epc.is/.well-known/oauth-protected-resource/mcp
Authorization servers
https://auth.epc.is/realms/platform
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.epc.is/mcp: tools/list returned 18 tools to an anonymous client, including checkEpcisConformance (write), digitalLinkToUrn (write), dpp (write), links (write), masterdata (write) and 3 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 warn5 info
  • The server marks "digitalLinkToUrn" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "digitalLinkToUrn" says "link": a word for a change.

    What this check looks for
  • Warnlinks

    The server marks "links" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "links" says "link": a word for a change.

    What this check looks for
  • The server marks "urnToDigitalLink" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "urnToDigitalLink" says "link": a word for a change.

    What this check looks for
  • The title mentions "credential".

    Matched text

    title: "Verify a credential"

    What this check looks for
  • The annotations title mentions "credential".

    Matched text

    annotations.title: "Verify a credential"

    What this check looks for
  • The description mentions "Credential".

    Matched text

    description: "Verify a Verifiable Credential (JSON-LD with a Data Integrity proof, a..."

    What this check looks for
Show 2 more findings

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 2026.11.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__epc__describeCbvTerm",
      "mcp__epc__findCbvTerms",
      "mcp__epc__get_event",
      "mcp__epc__listCbvTerms",
      "mcp__epc__listDocumentIdentifiers",
      "mcp__epc__query_events",
      "mcp__epc__summarize",
      "mcp__epc__validateCbvTerm",
      "mcp__epc__validateEpcisDocument",
      "mcp__epc__validateIdentifier"
    ],
    "ask": [
      "mcp__epc__checkEpcisConformance",
      "mcp__epc__digitalLinkToUrn",
      "mcp__epc__dpp",
      "mcp__epc__links",
      "mcp__epc__masterdata",
      "mcp__epc__trace",
      "mcp__epc__urnToDigitalLink",
      "mcp__epc__verify_credential"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as epc. Review it before you use it.

Capability tags behind 5 rules
  • mcp__epc__get_event private-data
  • mcp__epc__listDocumentIdentifiers private-data
  • mcp__epc__query_events private-data
  • mcp__epc__summarize private-data
  • mcp__epc__verify_credential untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/is.epc/mcp/verify?hash=8504cdb977366093d38858d7eadc7a361a5a9c49af02300d733c3ab0fa073f8c" | jq -e '.changed == false'

Pinned hash 8504cdb97736, from Nov 19, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/is.epc/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for is.epc/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/is.epc/mcp.svg)](https://radar.anlyon.com/servers/is.epc/mcp)

Source: MCP Registry. Synced Nov 19, 2026, 12:18 UTC.

epc.is EPCIS Repository MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the epc.is EPCIS Repository MCP server safe?

No scan can promise that. What its definitions show: 18 tools, 8 of which can change, send or delete something, and 8 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the epc.is EPCIS Repository MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the epc.is EPCIS Repository MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the epc.is EPCIS Repository MCP server have?

18 tools: 8 write, 10 read. checkEpcisConformance, digitalLinkToUrn, dpp, links, masterdata, trace, urnToDigitalLink, verify_credential and 10 more.

Does the epc.is EPCIS Repository MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the epc.is EPCIS Repository MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the epc.is EPCIS Repository MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.