Skip to main content
Glama
ArkForge Trust Layer

ArkForge Trust Layer

by ark-forge

Capa de Confianza ArkForge — Servidor MCP

Proxy de certificación de terceros: obtenga una prueba criptográfica independiente para cualquier llamada HTTP.

Funciona con agentes de IA, webhooks, microservicios o cualquier cliente HTTP. La prueba está firmada por ArkForge (un tercero independiente), no por quien realiza la llamada.

Obtenga su clave API gratuita (500 pruebas/mes) →


Por qué es importante

Cuando un sistema realiza una llamada HTTP, no existe un registro independiente de lo que se envió, lo que se recibió o cuándo ocurrió. Cualquiera de las partes podría negar o alterar la transacción.

ArkForge soluciona esto actuando como un proxy de certificación: el emisor dirige su solicitud a través de ArkForge, que firma el paquete completo de solicitud+respuesta con una clave Ed25519, le asigna una marca de tiempo mediante RFC 3161 y lo ancla en Sigstore Rekor, un registro inmutable y auditable públicamente.

La prueba resultante es verificable permanentemente en una URL pública, por cualquier persona, sin necesidad de contactar a ArkForge.

Esta es la diferencia entre un certificado autofirmado y uno emitido por una CA. Otras herramientas producen pruebas firmadas por el propio emisor. ArkForge produce pruebas firmadas por un tercero independiente.


Related MCP server: @lucairn/mcp-server

Casos de uso

  • Agentes de IA — pista de auditoría para cada llamada API externa (Claude, GPT, Mistral, LangChain, AutoGen)

  • Webhooks — pruebe que un evento de Stripe o GitHub se recibió con este payload exacto

  • Microservicios — registro a prueba de manipulaciones entre servicios internos (cumplimiento, fintech)

  • Proveedores de datos — pruebe que una API externa devolvió este valor en esta marca de tiempo

  • Automatizaciones — certifique una acción en un flujo de trabajo de n8n o Zapier


Instalación

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

Obtenga una clave API gratuita (500 pruebas/mes) en arkforge.tech.


Herramientas

certify_call

Dirija una llamada HTTP a través de ArkForge y obtenga una prueba criptográfica de la transacción.

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)

Devuelve proof_id, verification_url, upstream_response, chain_hash, timestamp y la signature Ed25519.

Utilice esto en lugar de llamar a la API directamente cuando necesite un registro auditable.

Respuesta de ejemplo:

{
  "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

Recupere el paquete de prueba completo para un proof_id determinado.

verify_proof

Obtenga un resumen legible por humanos de lo que certifica una prueba: útil para explicar a un usuario o auditor qué se verificó de forma independiente.

get_usage

Compruebe sus créditos restantes para el mes actual.


Qué contiene cada prueba

Campo

Descripción

proof_id

Identificador único — URL pública permanente

hashes.request

SHA-256 de la solicitud exacta enviada

hashes.response

SHA-256 de la respuesta exacta recibida

hashes.chain

Hash combinado — a prueba de manipulaciones

parties.seller

Dominio de la API llamada

timestamp_authority

Marca de tiempo RFC 3161 vía FreeTSA (QTSP eIDAS en Enterprise)

rekor

Entrada de registro inmutable de Sigstore Rekor

arkforge_signature

Firma Ed25519 mediante la clave independiente de ArkForge


Precios

Plan

Pruebas/mes

Precio

Gratuito

500

0 €

Pro

5.000

29 €/mes

Enterprise

50.000 + QTSP eIDAS

149 €/mes

Obtenga su clave API →


API REST

El servidor MCP es una ruta de integración. La misma API funciona desde cualquier lenguaje o framework:

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 tools
certify_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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      This 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.
      15
      73 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Privacy-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.
      1
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A 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.
      13
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Verifiable 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.
      1
      MIT