Aga MCP Server vs Hash

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

Aga MCP Server logoAga MCP ServerCryptography · Local subprocess (stdio)Verifiable decision records for AI agents: signed receipts for calls to its own governed tools.61GoodAuth: not declaredHash logoHashCryptography · Local subprocess (stdio)Cryptographic hash & HMAC MCP.49FairAuth: not declared

Verdict: choose Aga MCP Server for cryptography work as a local process; choose Hash for cryptography as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Aga MCP Server logoChoose Aga MCP Server when

  • You need dedicated capabilities in the Cryptography domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_server_info, get_portal_state, init_chain.
Explore Aga MCP Server

Hash logoChoose Hash when

  • You need dedicated capabilities in the Cryptography domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like hash, hmac.
Explore Hash

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAga MCP Server logoAga MCP ServerHash logoHash
CategoryCryptographyCryptography
Quality signal61/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools152

Tools & capabilities

Aga MCP Server tools 15

  • get_server_infoGet AGA server info, public keys, and portal state.
  • get_portal_stateGet current portal state, loaded artifact info, and enforcement status.
  • init_chainInitialize continuity chain with genesis event.
  • attest_subjectAttest subject, generate sealed Policy Artifact. Auto-loads into portal.
  • measure_integrityMeasure subject state, compare to sealed reference. Generates signed receipt for every measurement.
  • revoke_artifactRevoke an active policy artifact mid-session. Portal terminates on next measurement. (NCCoE Phase 3b)
  • verify_chainVerify continuity chain integrity.
  • generate_evidence_bundleExport the canonical SEP evidence bundle: signed PERMITTED/DENIED tool-call receipts + Merkle proofs + a mandatory signed checkpoint, for offline third-party verification (verify_bundle_offline, aga-verify, or aga-receipt-spec/verify/verify-sep.mjs). Pin gateway_public_key to prove provenance.
  • verify_bundle_offlineVerify a canonical SEP evidence bundle offline (full §6 algorithm: structural floor, receipt signatures, chain+ordering, leaf-recompute + Merkle bijection, signed checkpoint). Pass pinned_public_key to also prove provenance.
  • request_claimRequest disclosure of a claim. Auto-substitutes if denied.
  • list_claimsList available claims with sensitivity levels.
  • delegate_to_subagentDerive a constrained policy artifact for a sub-agent. Scope can only diminish, never expand. (NCCoE constrained delegation)
  • +3 more on the listing page

Hash tools 2

  • hashCompute a cryptographic hash (hex digest) of text: algorithm = md5, sha1, sha256 (default), sha384, or sha512. Keyless/offline; the input is not stored or transmitted. MD5/SHA-1 are legacy (checksums only, not security).
  • hmacCompute an HMAC (hex) of text with a secret key. algorithm = sha1, sha256 (default), sha384, or sha512. Keyless/offline.

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.

Aga MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "aga-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@attested-intelligence/aga-mcp-server@3.6.6"
      ]
    }
  }
}

Hash

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "hash": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hash"
      ]
    }
  }
}

Frequently asked questions

Aga MCP Server is categorized under Cryptography and uses a local stdio subprocess. Hash belongs to Cryptography and uses a local stdio subprocess. Pick Aga MCP Server for cryptography work and Hash 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.

Aga MCP Server has no declared pricing — check the project's own site. Hash 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 aga-mcp-server and hash as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Aga MCP Server has a quality signal of 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Hash has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.