About TAG IT Verify
Verify on-chain lifecycle state and provenance of NFC-tagged physical products
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://verify.tagit.network/mcpclaude mcp add --transport http network-tagit-nfc-verify https://verify.tagit.network/mcp{"mcpServers":{"network-tagit-nfc-verify":{"type":"http","url":"https://verify.tagit.network/mcp"}}}Open in Cursor{"servers":{"network-tagit-nfc-verify":{"type":"http","url":"https://verify.tagit.network/mcp"}}}Open in VS Code{"mcpServers":{"network-tagit-nfc-verify":{"type":"http","url":"https://verify.tagit.network/mcp"}}}{"mcpServers":{"network-tagit-nfc-verify":{"serverUrl":"https://verify.tagit.network/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
3| Parameter | Type | Required | Description |
|---|---|---|---|
| token_id | string|integer | Yes | TAGITCore token id as a decimal integer, e.g. 5 or "5". uint256 range. Prefer the string form for ids above 2^53. Ids that were never minted are not an error on-chain: they resolve to a zero record and are reported as ASSET_NOT_FOUND. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.