claude mcp add arkforge-mcp -- npx -y arkforge-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
2 ★ · ark-forge/arkforge-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 2 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository ark-forge/arkforge-mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party certifying proxy — get an independent cryptographic proof for any HTTP call. Works with **AI agents, webhooks, microservices, or any HTTP client**. The proof is signed by ArkForge (independent third party) — **not by the caller**. **Get your free API key (500 proofs/month) →** --- Why this matters When a system makes an HTTP call, there is no independent record of what was sent, what was received, or when it happened. Either party could deny or alter the transaction. ArkForge fixes this by acting as a **certifying proxy**: the caller routes its request through ArkForge, which signs the full request+response bundle with an Ed25519 key, timestamps it via RFC 3161, and anchors it in Sigstore Rekor — an immutable, publicly auditable log. The resulting proof is permanently verifiable at a public URL, by anyone, without contacting ArkForge. **This is the difference between a self-signed certificate and a CA-issued one.** Other tools produce proofs signed by the caller itself. ArkForge produces proofs signed by an independent third party. --- Use cases - **AI agents** — audit trail for every external API call (Claude, GPT, Mistral, LangChain, AutoGen) - **Webhooks** — prove a Stripe or GitHub event was received with this exact payload - **Microservices** — tamper-evident log between internal services (compliance, fintech) - **Data providers** — prove an external API returned this value at this timestamp - **Automations** — certify an action in an n8n or Zapier workflow --- Installation Get a free API key (500 proofs/month) at arkforge.tech. --- Tools certify_call Route an HTTP call through ArkForge and get a cryptographic proof of the transaction. Returns proof_id, verification_url, upstream_response, chain_hash, timestamp, and Ed25519 signature. **Use this instead of calling the API directly** when you need an auditable record. Example response: get_proof Retrieve the full proof bundle for a given proof_id. verify_proof Get a human-readable summary of what a proof certifies — useful for explaining to a user or auditor what was independently verified. get_usage Check your remaining credits for the current month. --- What each proof contains | Field | Description | |---|---| | proof_id | Unique identifier — permanent public URL | | hashes.request | SHA-256 of the exact request sent | | hashes.response | SHA-256 of the exact response received |