TAG IT Verify is an MCP server with 3 tools an agent can call, among them check_flagged, get_lifecycle_history, verify_asset. It answers at https://verify.tagit.network/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Verify on-chain lifecycle state and provenance of NFC-tagged physical products.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 (end-of-life) Inputs: token_id |
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 re- Inputs: token_id |
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. Byte-ide Inputs: token_id |
Every block below points at https://verify.tagit.network/mcp. Pick your client and copy.
claude mcp add --transport http tag-it-verify https://verify.tagit.network/mcp
{
"mcpServers": {
"tag-it-verify": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://verify.tagit.network/mcp"]
}
}
}{
"mcpServers": {
"tag-it-verify": {
"url": "https://verify.tagit.network/mcp"
}
}
}{
"servers": {
"tag-it-verify": {
"type": "http",
"url": "https://verify.tagit.network/mcp"
}
}
}{
"context_servers": {
"tag-it-verify": {
"url": "https://verify.tagit.network/mcp"
}
}
}{
"mcpServers": {
"tag-it-verify": {
"serverUrl": "https://verify.tagit.network/mcp"
}
}
}{
"mcpServers": {
"tag-it-verify": {
"url": "https://verify.tagit.network/mcp"
}
}
}name: TAG IT Verify
version: 0.0.1
schema: v1
mcpServers:
- name: TAG IT Verify
type: streamable-http
url: https://verify.tagit.network/mcp{
"mcpServers": {
"tag-it-verify": {
"httpUrl": "https://verify.tagit.network/mcp"
}
}
}{
"mcpServers": {
"tag-it-verify": {
"type": "http",
"url": "https://verify.tagit.network/mcp"
}
}
}{
"mcpServers": {
"tag-it-verify": {
"url": "https://verify.tagit.network/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fverify.tagit.network%2Fmcp&type=streamable_http&id=tag-it-verify&name=TAG%20IT%20Verify
It answered our last check on 24 October 2026 in 205 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by tagit.network and served from verify.tagit.network, the vendor's own domain: https://verify.tagit.network/mcp.
3, as returned by the server's own tools/list on 22 September 2026: check_flagged, get_lifecycle_history, verify_asset.
It answered our last check on 24 October 2026 in 205 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://verify.tagit.network/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: network.tagit. Endpoint host: verify.tagit.network. ARD identifier: urn:air:network.tagit:mcp:nfc-verify.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.