Arkforge MCP

What ark-forge/arkforge-mcp MCP server does

The ark-forge/arkforge-mcp MCP server exposes ArkForge as a certifying HTTP proxy. Rather than sending a request directly to an upstream API, an agent can submit the target URL, HTTP method, optional JSON payload, description, and optional caller identity through ArkForge. The service forwards the call and returns both the upstream response and a proof of the transaction.

The proof covers the exact request and response. It includes SHA-256 hashes for each side, a combined chain hash, the called API domain, a timestamp authority result, a Sigstore Rekor log entry, and an Ed25519 signature made by ArkForge. A verification URL provides a public location for checking the proof without contacting ArkForge.

This fits audit trails for external API calls, webhook receipt records, service-to-service requests, data returned by external providers, and certified actions in automation workflows.

How it works

Call certify_call with an upstream URL and, when needed, a JSON body. The method defaults to POST, while GET is also supported. ArkForge acts as the intermediary, sends the request, records the returned response, and constructs the proof bundle. The result contains a proof_id, verification URL, response data, hashes, timestamp information, and signature.

The independent signing model is central to the ark-forge/arkforge-mcp MCP server: the proof is signed by ArkForge rather than by the calling agent. RFC 3161 timestamping supplies time evidence, and Sigstore Rekor provides an immutable public log entry.

Setup and configuration

The README provides a stdio configuration using uvx:

{
  "mcpServers": {
    "arkforge": {
      "command": "uvx",
      "args": ["arkforge-mcp"],
      "env": {
        "ARKFORGE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Set ARKFORGE_API_KEY to an API key obtained from ArkForge. The documented free plan includes 500 proofs per month. Paid plans increase the monthly proof allowance, and the Enterprise plan includes QTSP eIDAS timestamping according to the README.

Tools and capabilities

The ark-forge/arkforge-mcp MCP server provides four tools:

• certify_call sends a GET or POST request through ArkForge and returns its proof details.
• get_proof retrieves the complete proof bundle for a supplied proof_id.
• verify_proof returns a human-readable explanation of what a proof certifies, for users or auditors.
• get_usage reports the remaining credits for the current month.

The same ArkForge service also exposes a REST endpoint for clients that do not use MCP, but that endpoint is separate from the MCP tool interface.

Limitations and notes

Requests must be routed through ArkForge to receive a proof; direct calls to an upstream API are not certified by this server. The documented certify_call inputs support a target URL, JSON payload, POST or GET method, a description, and an optional agent identity. Usage is constrained by the account's monthly proof allowance.

The proof records the request and response hashes and related metadata, but the supplied material does not document handling for other HTTP methods, non-JSON bodies, custom headers, retries, or streaming responses. Confirm those requirements with ArkForge before relying on this server for them. The ark-forge/arkforge-mcp MCP server requires an ArkForge API key to operate.