ArkForge Trust Layer MCP Server is a third-party attestation proxy used to obtain independent cryptographic proof for any HTTP call. It is suitable for AI agents, webhooks, microservices, or any HTTP client, proving that the proof is signed by ArkForge (an independent third party), rather than by the caller.
Purpose
When a system makes an HTTP call, there is no independent record that can prove what was sent, what was received, and when it happened, and either party could deny or tamper with the transaction. ArkForge solves this problem by acting as an attestation proxy: the caller routes the request through ArkForge, which signs the complete request+response package with an Ed25519 key, adds a timestamp via RFC 3161, and anchors it in Sigstore Rekor—a tamper-evident, publicly auditable log. The generated proof can be permanently verified at a public URL, and anyone can verify it without contacting ArkForge. Official materials compare it to the difference between a self-signed certificate and a CA-issued certificate: proofs generated by other tools are signed by the caller itself, while proofs generated by ArkForge are signed by an independent third party.
Main capabilities
- Route HTTP calls through ArkForge to obtain cryptographic proof of that transaction.
- Return proof_id, verification_url, upstream_response, chain_hash, timestamp, and Ed25519 signature.
- Can replace direct API calls when an auditable record is needed.
- Retrieve the complete proof package based on proof_id.
- Obtain a readable summary of what the proof certifies, making it easy to explain to users or auditors which content has been independently verified.
- Query the remaining quota for the current month.
What each proof contains
Official materials do not list a specific inventory of what each proof contains, only stating that it includes proof_id, verification_url, upstream_response, chain_hash, timestamp, and Ed25519 signature. More details are not currently provided.
How to use
An API key must first be obtained at arkforge.tech. Official free keys are provided (500 proofs per month). This MCP server is one integration path, and the same API can also be called from any language or framework.Official materials do not provide specific installation commands, code examples, or API endpoint information, and none are currently provided.
Applicable scenarios
- AI agents: provide an audit trail for every external API call (materials mention Claude, GPT, Mistral, LangChain, AutoGen).
- Webhooks: prove that a Stripe or GitHub event and its exact payload were received.
- Microservices: provide tamper-evident logs between internal services (compliance, fintech scenarios).
- Data providers: prove that an external API returned a certain value at a certain timestamp.
- Automation: certify a certain operation in an n8n or Zapier workflow.
Limitations
Official materials do not specify the specific limitation terms, platform support scope, rate limits (other than the free quota of 500 proofs per month), or pricing information, and none are currently provided. Proofs are signed by ArkForge as an independent third party, and their trustworthiness depends on trust in ArkForge and Sigstore Rekor.
