Skip to content
TAG IT Network logo

TAG IT Network MCP server

Which MCP servers are TAG IT Network's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to TAG IT Network

Whose server it is
  • Registry namenetwork.tagit/nfc-verifyverified in the MCP registry

The registry name sits under tagit.network. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools3
  • Server calls itselfnetwork.tagit/nfc-verify
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 210 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 9, the first on 2026-10-20
  • INITE MCP score88 of 100answers 100 · definitions 100 · context 100 · use 8 · connects 100
  • Use1 GitHub stars
  • Answered100% of days9 of 9 daily checks
  • Median first answer207 ms
  • Space in an agent's context≈ 792 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · check a product's authenticity by tapping its NFC chip
  • not sure · track a product's ownership and handler history on-chain
  • cannot · locate lost items through their on-chain record

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-20
  • verify_asset

    Return the canonical on-chain verification verdict for a TAG IT physical asset: its lifecycle state (MINTED, BOUND, ACTIVATED, CLAIMED, FLAGGED, RECYCLED), whether that state counts as authentic, and a re-derivable chain reference…

  • get_lifecycle_history

    Return the ordered on-chain event timeline for a TAG IT asset, oldest first: mint, NFC tag binding, every state transition, and every resale. Each event carries the block number and transaction hash that produced it, so any entry can be…

  • check_flagged

    Fast yes/no on whether a TAG IT asset is currently FLAGGED — TAGITCore lifecycle state 5, meaning an open lost / stolen / recall investigation. IMPORTANT: `flagged: false` does NOT mean the asset is in good standing. RECYCLED…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "nfc-verify": {
      "type": "http",
      "url": "https://verify.tagit.network/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http tagit https://verify.tagit.network/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://verify.tagit.network/mcp as a custom connector in the settings.

OpenAPI spec

4 paths, read 2026-10-20. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.