Find an app
Account
Toggle menu

Use in your browser

Check a product link resolver

Check one live GS1 Digital Link resolver for redirects, linkset negotiation, target resolution, and URI syntax. Compare two resolvers under the same bounded checks.

Guest includes 50 lifetime app requests. Create a free account for 100 app requests each calendar month. One allowance across every app, in your browser and your agent.One allowance across every app, in your browser and your agent. Manage usage

Add Product Link Resolver Check to your agent

Connect this app on its own. Add other PowMCP apps whenever your agent needs another job done.

Open the apps workspace A glowing app tile clicking into a slot on a dark agent device, with the PowMCP app box behind it

Connect directly

Choose your agent. Each button opens a new tab with only this app's endpoint ready to add.

Use another agent

Copy one ready-to-send prompt for any agent that supports remote MCP connections.

Manual endpoint, JSON, and terminal commands

For clients that require manual configuration, use this app-only endpoint, its JSON entry, or one terminal command.

ChatGPT: enable Developer mode in Settings → Security and login, then add this MCP endpoint from the Plugins page. Availability depends on your account and workspace policy. PowMCP has not yet verified ChatGPT account linking. OpenAI setup guide

https://powmcp.com/product-link-resolver-check/mcp
{
  "mcpServers": {
    "powmcp-product-link-resolver-check": {
      "type": "http",
      "url": "https://powmcp.com/product-link-resolver-check/mcp"
    }
  }
}

Terminal agents add this app with one command:

Claude Code
claude mcp add --transport http powmcp-product-link-resolver-check https://powmcp.com/product-link-resolver-check/mcp
Codex CLI
codex mcp add powmcp-product-link-resolver-check --url https://powmcp.com/product-link-resolver-check/mcp
Gemini CLI
gemini mcp add --transport http powmcp-product-link-resolver-check https://powmcp.com/product-link-resolver-check/mcp

Manage, disable, or remove this connection in your agent's own MCP settings. PowMCP does not label an external connection as installed without confirmation from that client.

Proof

What it does

Check a product 2D-barcode resolver before you ship it

Verify that a live GS1 Digital Link resolver behaves as a GS1-Conformant resolver (redirect codes, Accept-header content negotiation, the linkType=all RFC 9264 linkset API, linktype-target resolvability, and URI-syntax conformance) with the observed HTTP behavior as evidence, or compare two resolvers under identical bounded checks. It reports live conformance behavior only, never official GS1 certification.

Category
Developer Tools

Request cost1 completed result

Guests get 50 lifetime app requests. Free accounts get 100 each calendar month.

Tools in this app

01

Product Link Resolver Check

resolver_check

Verify that one live GS1 Digital Link resolver URL behaves as a GS1-Conformant resolver, with observed HTTP behavior as evidence. Sends header-varied requests to the resolver (Accept: application/linkset+json to negotiate the RFC 9264 linkset and Accept: text/html to observe redirect behavior) and follows redirects manually so the actual 3xx code is inspected, not swallowed. Runs five checks: redirect-code semantics, Accept-header content negotiation, the linkType=all RFC 9264 linkset shape, linktype-target resolvability, and self-authored URI-syntax conformance (GTIN check digit, AI ordering, qualifier position). Returns per-check pass/fail with distinguished absence-of-evidence states (resolver-unreachable vs nonconformant, linkset-not-served vs malformed, no-content-negotiation vs wrong-content-type, declared-but-unresolvable targets). Use for single-resolver readiness and diagnosis; use resolver_compare for two resolvers. This reports live conformance behavior against a pinned dated profile only, never official GS1 certification, and never a judgment on whether the destinations behind the links are the correct product pages. Each call live-fetches the resolver several times and can take up to about 45 seconds.

02

Product Link Resolver Compare

resolver_compare

Run the identical bounded GS1 Digital Link conformance checks against exactly two live resolver URLs (two brand resolvers, or one resolver before versus after a config change) and diff, rank, and report conformance drift. Each resolver is checked with the same five checks resolver_check runs (redirect semantics, Accept-header content negotiation, RFC 9264 linkset, linktype-target resolvability, URI syntax) under identical limits, then reported side by side with a difference table of checks that pass on one resolver and fail on the other, and a ranking by pass state then fewer failed conformance checks, only when the measured checks support one. The two resolvers are compared only as resolver targets under identical checks and are not required to serve the same product; the comparison never infers that one resolver's product data or destinations are better or more correct. Use resolver_check for a single resolver. Neither result is official GS1 certification. Each comparison live-fetches both resolvers several times and can take up to about 90 seconds.

Product Link Resolver Check questions

Scope and boundaries for Product Link Resolver Check.

01What can I check with Product Link Resolver Check?

Test https://id.gs1.org/01/09506000134376?linkType=all with maxTargets set to 2, exercising the resolver's HTML redirect and application/linkset+json negotiation paths.

02How should I read the result?

Read reachable, then pass and the five checks. A pass means the resolver was reachable and every bounded redirect, content-negotiation, linkset, probed-target, and URI-syntax check passed; fix the first failed check from its state and detail. Targets-not-evaluated is absence of evidence, truncation makes the report incomplete, and comparison ranking covers resolver conformance only, not destination correctness.

03What are its limits?

This is a bounded live check against a pinned conformance profile, not official GS1 certification. Only a requested number of link targets is probed, and a reachable destination does not establish that it is the correct product page or that its product data is accurate.