Log inSubmit server

Git vs TAG IT Verify

A side-by-side look at the Git and TAG IT Verify MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Git logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth requiredTAG IT Verify logoTAG IT VerifyIndustrial & IoTVerify on-chain lifecycle state and provenance of NFC-tagged physical products.35FairAuth: not declared

Verdict: choose Git for version control work as a local process; choose TAG IT Verify for industrial & iot. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Git logoChoose Git when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like repo_path, context_lines, target.
Explore Git

TAG IT Verify logoChoose TAG IT Verify when

  • You need dedicated capabilities in the Industrial & IoT domain.
Explore TAG IT Verify

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGit logoGitTAG IT Verify logoTAG IT Verify
CategoryVersion ControlIndustrial & IoT
Quality signal81/100 · Excellent35/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars91,5261
Directory activity 51 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools16Not listed
Full listingView Git View TAG IT Verify

Tools & capabilities

Git tools 16

  • repo_path
  • context_lines
  • target
  • message
  • MERGE_HEAD
  • HEAD
  • files
  • max_count
  • start_timestamp
  • end_timestamp
  • branch_name
  • base_branch
  • +4 more on the listing page

TAG IT Verify tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Git

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "installations"
      ]
    }
  }
}

TAG IT Verify

No confirmed install command for TAG IT Verify yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Git is categorized under Version Control and uses a local stdio subprocess. TAG IT Verify belongs to Industrial & IoT and uses an install path we have not confirmed yet. Pick Git for version control work and TAG IT Verify for industrial & iot.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. TAG IT Verify has no confirmed install command yet — follow its own setup instructions.

Git is listed as free. Auth: no auth required. TAG IT Verify has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add git and tag-it-verify as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 51 views, 0 installs and 91,526 GitHub stars. TAG IT Verify has 35/100 (Fair) with 4 views, 0 installs and 1 GitHub stars.

Popular comparisons with Git

Popular comparisons with TAG IT Verify