ArkForge Trust Layer
ArkForge 信任层 — MCP 服务器
第三方认证代理 — 为任何 HTTP 调用获取独立的加密证明。
适用于 AI 代理、Webhook、微服务或任何 HTTP 客户端。 该证明由 ArkForge(独立的第三方)签名 — 而非由调用方签名。
为什么这很重要
当系统进行 HTTP 调用时,没有关于发送了什么、接收了什么或何时发生的独立记录。任何一方都可能否认或篡改交易。
ArkForge 通过充当认证代理来解决这个问题:调用方通过 ArkForge 路由其请求,ArkForge 使用 Ed25519 密钥对完整的请求+响应包进行签名,通过 RFC 3161 添加时间戳,并将其锚定在 Sigstore Rekor 中 — 这是一个不可篡改、可公开审计的日志。
生成的证明可以在公共 URL 上由任何人永久验证,无需联系 ArkForge。
这就是自签名证书与 CA 颁发证书之间的区别。 其他工具生成的证明由调用方自己签名。ArkForge 生成的证明由独立的第三方签名。
Related MCP server: @lucairn/mcp-server
使用场景
AI 代理 — 针对每次外部 API 调用(Claude、GPT、Mistral、LangChain、AutoGen)的审计追踪
Webhook — 证明 Stripe 或 GitHub 事件已收到且载荷完全一致
微服务 — 内部服务之间防篡改的日志(合规性、金融科技)
数据提供商 — 证明外部 API 在此时间戳返回了此值
自动化 — 认证 n8n 或 Zapier 工作流中的操作
安装
{
"mcpServers": {
"arkforge": {
"command": "uvx",
"args": ["arkforge-mcp"],
"env": {
"ARKFORGE_API_KEY": "your_api_key_here"
}
}
}
}在 arkforge.tech 获取免费的 API 密钥(每月 500 次证明)。
工具
certify_call
通过 ArkForge 路由 HTTP 调用并获取交易的加密证明。
target URL of the upstream API to call
payload JSON body (optional)
method "POST" or "GET" (default: "POST")
description Human-readable description included in the proof
agent_identity Identifier for the calling system (optional)返回 proof_id、verification_url、upstream_response、chain_hash、timestamp 和 Ed25519 signature。
当您需要可审计记录时,请使用此工具代替直接调用 API。
响应示例:
{
"proof_id": "prf_20260310_143022_a1b2c3",
"verification_url": "https://trust.arkforge.tech/v1/proof/prf_20260310_143022_a1b2c3",
"upstream_response": { "status": "ok" },
"chain_hash": "e3b0c44298fc1c149afb...",
"timestamp": "2026-03-10T14:30:22.481Z",
"timestamp_authority": "verified",
"rekor_log_id": "https://rekor.sigstore.dev/api/v1/log/entries/...",
"seller": "api.example.com",
"signature": "MCowBQYDK2VwAyEA..."
}get_proof
检索给定 proof_id 的完整证明包。
verify_proof
获取证明所认证内容的易读摘要 — 有助于向用户或审计员解释经过独立验证的内容。
get_usage
检查您当月剩余的额度。
每个证明包含的内容
字段 | 描述 |
| 唯一标识符 — 永久公共 URL |
| 所发送请求的 SHA-256 哈希值 |
| 所接收响应的 SHA-256 哈希值 |
| 组合哈希 — 防篡改 |
| 被调用 API 的域名 |
| 通过 FreeTSA 获取的 RFC 3161 时间戳(企业版支持 QTSP eIDAS) |
| Sigstore Rekor 不可篡改日志条目 |
| 由 ArkForge 独立密钥生成的 Ed25519 签名 |
定价
计划 | 每月证明次数 | 价格 |
免费版 | 500 | €0 |
专业版 | 5,000 | €29/月 |
企业版 | 50,000 + QTSP eIDAS | €149/月 |
REST API
MCP 服务器只是一种集成路径。相同的 API 适用于任何语言或框架:
curl -X POST https://trust.arkforge.tech/v1/proxy \
-H "X-Api-Key: your_key" \
-H "Content-Type: application/json" \
-d '{"target": "https://api.example.com/action", "payload": {"data": "value"}}'Available Tools
4 toolscertify_callA
Call an external API and get a cryptographic proof of the transaction.
Use this INSTEAD of calling the API directly when you need an auditable, tamper-evident record of what was sent and received.
The proof is signed by ArkForge (independent third party), timestamped via RFC 3161, and anchored in Sigstore Rekor — not self-signed by your agent.
Args: target: URL of the upstream API to call (e.g. "https://api.example.com/v1/action") payload: JSON body to send to the upstream API (optional for GET requests) method: HTTP method — "POST" or "GET" (default: "POST") description: Human-readable description of what this call does (included in the proof) agent_identity: Identifier for the calling agent (optional, included in the proof)
Returns: JSON with proof_id, verification_url, the upstream API response, chain_hash, and timestamp. Share verification_url with any third party to let them independently verify what happened.
Inputs: target (required), payload, method, description, +1 more. Returns: result
get_proofA
Retrieve the full cryptographic proof for a given proof ID.
Returns the complete proof bundle: request/response hashes, parties, RFC 3161 timestamp, Sigstore Rekor log entry, and archive.org snapshot.
Args: proof_id: The proof identifier (e.g. "prf_20260310_143022_a1b2c3")
Inputs: proof_id (required). Returns: result
get_usageA
Check your ArkForge API usage and remaining credits for the current period.
Returns your tier (Free / Pro / Enterprise), proofs used, proofs remaining, and the reset date.
Inputs: no named parameters. Returns: result
verify_proofA
Get a human-readable summary of what a proof certifies.
Useful for explaining to a user or auditor what was independently verified, without reading raw JSON.
Args: proof_id: The proof identifier (e.g. "prf_20260310_143022_a1b2c3")
Inputs: proof_id (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct and non-overlapping purpose: certify_call creates proofs, get_proof retrieves raw proof data, get_usage checks account status, and verify_proof provides human-readable summaries. There is no ambiguity about when to use which tool, as they target different stages of the proof lifecycle and administrative functions.
All tools follow a consistent verb_noun pattern with clear, descriptive names: certify_call, get_proof, get_usage, and verify_proof. The naming is uniform, using snake_case throughout, and the verbs (certify, get, verify) accurately reflect the actions without mixing conventions.
With 4 tools, this server is well-scoped for its purpose of providing cryptographic proof and verification services. Each tool serves a clear role in the workflow—creating, retrieving, verifying proofs, and managing usage—without being overly sparse or bloated, making it efficient for agents to navigate.
The tool set covers the core lifecycle of proof creation, retrieval, and verification, along with administrative usage checks. A minor gap exists in the lack of tools for managing or deleting proofs, but this does not hinder basic operations, and agents can still perform essential tasks without dead ends.
Maintenance
Related MCP Connectors
Free hosted notary: make any AI agent's actions provable in one call. Verify signed agent logs.
Attestation infrastructure for the agentic economy: signed, independently verifiable verdicts.
Notary for AI agents: seal fingerprints, verify proofs, check mandates. Anchored in Bitcoin.
Checks AI agent actions before they run. Signed, RFC 3161 timestamped evidence for audits.
Related MCP Servers
- AlicenseBqualityBmaintenanceThis server acts as a Portal (zero-trust Policy Enforcement Point) for AI agents. Every tool call is attested, measured against a sealed cryptographic reference, and logged to a tamper-evident continuity chain with signed receipts.1573 npmMIT
- AlicenseAqualityBmaintenancePrivacy-preserving AI gateway. Sanitises PII before prompts reach Anthropic / OpenAI / your LLM, then emits a signed cryptographic certificate per call (Ed25519 + RFC 3161 + Sigstore Rekor). EU GDPR + AI Act ready. Free tier 500/mo with BYOK.12MIT
- AlicenseBqualityBmaintenanceA governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.13MIT

EVIDIQ Circuit MCPofficial
AlicenseNot gradedqualityBmaintenanceVerifiable API proxy and circuit breaker guard for autonomous agents, offering TLS attestation, payload schema inspection, circuit breaker enforcement, webhook signature verification, and 0G-anchored receipt attestation.1MIT