Log inSubmit server

Git vs XProof

A side-by-side look at the Git and XProof 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 requiredXProof logoXProofCryptographyProof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.33EmergingAuth: not declared

Verdict: choose Git for version control work as a local process; choose XProof for cryptography. 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

XProof logoChoose XProof when

  • You need dedicated capabilities in the Cryptography domain.
Explore XProof

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGit logoGitXProof logoXProof
CategoryVersion ControlCryptography
Quality signal81/100 · Excellent33/100 · Emerging
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars91,4871
Directory activity 49 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools16Not listed
Full listingView Git View XProof

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

XProof 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"
      ]
    }
  }
}

XProof

No confirmed install command for XProof 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. XProof belongs to Cryptography and uses an install path we have not confirmed yet. Pick Git for version control work and XProof for cryptography.

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. XProof has no confirmed install command yet — follow its own setup instructions.

Git is listed as free. Auth: no auth required. XProof 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 xproof 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 49 views, 0 installs and 91,487 GitHub stars. XProof has 33/100 (Emerging) with 1 views, 0 installs and 1 GitHub stars.

Popular comparisons with Git

Popular comparisons with XProof