Verify on-chain lifecycle state and provenance of NFC-tagged physical products.
Connect Remote server
claude mcp add --transport http nfc-verify https://verify.tagit.network/mcp
{
"mcpServers": {
"nfc-verify": {
"url": "https://verify.tagit.network/mcp"
}
}
}
{
"servers": {
"nfc-verify": {
"type": "http",
"url": "https://verify.tagit.network/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://verify.tagit.network/mcp
Tools 3 found in our last check
verify_assetReturn 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. Byte-identical to the public JSON at GET https:…
get_lifecycle_historyReturn 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 re-derived independently from a Base Sepol…
check_flaggedFast 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 (end-of-life) and unminted assets are also not flagge…
Details
| Endpoint | https://verify.tagit.network/mcp (Streamable HTTP) |
| First published | 29 Jul 2026 |
| Last updated | 29 Jul 2026 |
| Registry name | network.tagit/nfc-verify |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
