Skip to content
External endpointresponds

TAG IT Verify

Verify on-chain lifecycle state and provenance of NFC-tagged physical products.

Endpoint URL
https://verify.tagit.network/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
309 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
network.tagit/nfc-verify

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
network.tagit/nfc-verify
Version
1.0.0
Capability keys
tools
Tool names
verify_asset, get_lifecycle_history, check_flagged
Instructions excerpt

TAG IT Verify answers questions about the on-chain state of physical products that carry a TAG IT NFC tag. It reads TAGITCore (an ERC-721 digital-twin contract) on Base Sepolia and reports a lifecycle verdict for a token id. Lifecycle: 0 NONE, 1 MINTED, 2 BOUND (NFC tag cryptographically linked), 3 ACTIVATED (QA passed, in distribution), 4 CLAIMED (consumer-owned), 5 FLAGGED (lost/stolen/recall investigation), 6 RECYCLED (end of life). THREE LIMITS THAT CHANGE WHAT THE ANSWERS MEAN: 1. `authentic: true` is a claim about lifecycle state ONLY. It is NOT evidence that anyone physically held the product. Physical presence requires an NFC tap that produces an NTAG 424 DNA SUN cryptogram; no software can manufacture one, and this server has no tool that can substitute for it. Never report a verdict from here as proof of presence. 2. The data is Base Sepolia TESTNET, from a contract that has NOT been externally audited. Say so before it is used in any decision that moves money o

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 338ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 766ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 439ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 309ms