Provenance vs ALEETH Authority MCP

In-depth architectural comparison of the Provenance and ALEETH Authority MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

P

Choose Provenance when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Provenance Details

Choose ALEETH Authority MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore ALEETH Authority MCP Details

Feature & Specification Comparison

Specification	P Provenance Developer Tools	ALEETH Authority MCP Developer Tools
Summary	Stamp any data to the Markovian chain for a verifiable provenance receipt. Proves timing, not truth.	The first MCP governed by ICA. Every action is gated and sealed with a verifiable receipt.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "provenance": {
      "command": "npx",
      "args": [
        "-y",
        "provenance"
      ]
    }
  }
}

{
  "mcpServers": {
    "aleeth-authority-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-spec-check"
      ]
    }
  }
}

Related MCP Server Comparisons