# Tagit Verify MCP server

Source: https://glimind.com/server/mcp-registry%2Fnetwork.tagit%2Fverify
Registry id: `mcp-registry/network.tagit/verify`
Status: live (checked 2026-10-27T10:57:15.289Z)

## Verdict

Tagit Verify MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 407 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (96/100) across 3 tools, costing an agent about 751 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 407 ms | 53% of MCP servers |
| p95 handshake latency | 2584 ms | — |
| Checks in 30 days | 4,985 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 8 min | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 3 | — |
| Tool-list size for an agent | ~751 tokens | 80% of MCP servers |
| Days observed | 29 | — |

## Install

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

Claude Code:

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

## Tools (3)

- `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: `flag
- `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
- `verify_asset`: Return the canonical on-chain verification verdict for a TAG IT physical asset: its lifecycle state (MINTED, BOUND, ACTIVATED, CLAIMED, FLAGGED, RECYCLED), whet

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.