# TAG IT Verify

An MCP server that answers questions about the lifecycle and origin of physical goods carrying NFC tags. Handy when your agent needs network data mid-conversation.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 1
- Author: TAG-IT-NETWORK
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/TAG-IT-NETWORK/tagit-dashboard/tree/HEAD/apps/verify
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/tag-it-verify

## What it does

The server lives at `https://verify.tagit.network/mcp` and speaks HTTP. Your agent treats it like any other MCP server: ask about a tag, get back what the network knows about it.

In Claude the whole setup is one line: `claude mcp add --transport http nfc-verify https://verify.tagit.network/mcp`. Swap the name to `verify` if you prefer — the rest of the command stays the same. Codex, Cursor, GitHub Copilot and Gemini CLI each take their own config block, but the URL does not change.

No API keys appear in any of the install commands, and nothing runs locally. If your firewall or proxy blocks `verify.tagit.network`, the connection simply fails, so check that route first.

## Requirements
- Remote server: `https://verify.tagit.network/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http nfc-verify https://verify.tagit.network/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add verify --url https://verify.tagit.network/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "verify": {
            "url": "https://verify.tagit.network/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "verify": {
            "type": "http",
            "url": "https://verify.tagit.network/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http verify https://verify.tagit.network/mcp
```

## When to use it
- look up the current state of an NFC tag by its id
- check where a product came from before accepting a shipment
- compare tag data against what a supplier claims
- pull lifecycle details for a batch without leaving the chat

## Example prompts
- Check tag `nfc-001` with verify
- What does the network know about this product's origin?
- Show the state of the tag from my last query

## Similar
- [verify-this](https://affpapa.org/en/nevibecode/skills/verify-this.md) — skill · 2400 installs
- [audit-verify-explain-grade-5](https://affpapa.org/en/nevibecode/skills/audit-verify-explain-grade-5.md) — skill · 1400 installs
- [verify](https://affpapa.org/en/nevibecode/skills/yeachan-heo-verify.md) — skill · 652 installs
- [verify-and-stop](https://affpapa.org/en/nevibecode/skills/verify-and-stop.md) — skill · 104900 installs
- [modernize-verify](https://affpapa.org/en/nevibecode/commands/modernize-verify.md) — command · ★ 44770
- [vibe-verify](https://affpapa.org/en/nevibecode/skills/vibe-verify.md) — skill · ★ 3191

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md