io.github.SaravananJaichandar/etch

Registre officiel Sécurité

Etch is a signed audit chain for AI agent decisions, offline-verifiable against pinned public keys.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http etch 'https://etch.systems/mcp' --header 'Authorization: <Bearer token. For zero-signup try-it-now (500 events, 14-day retention), run: curl -X POST https://etch.systems/v1/your-project. The response returns a token; use '\''Bearer <token>'\'' as the header value. For a persistent project token, sign up at https://etch.systems/signup.>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "etch": {
            "type": "http",
            "url": "https://etch.systems/mcp",
            "headers": {
                "Authorization": "<Bearer token. For zero-signup try-it-now (500 events, 14-day retention), run: curl -X POST https://etch.systems/v1/your-project. The response returns a token; use 'Bearer <token>' as the header value. For a persistent project token, sign up at https://etch.systems/signup.>"
            }
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. etch-mcp
  2. Try in 30 seconds, no signup
  3. Per-client config
  4. Verify
  5. What Etch is NOT
  6. License
  7. Registry listings

etch-mcp

Etch is a signed audit chain for AI agent decisions, offline-verifiable against pinned public keys.

This repository is the MCP integration surface for Etch, the hosted service. It carries only:

  • The MCP registry metadata (server.json, glama.json)
  • Per-client integration examples for Claude Code / Cursor / Continue / Cline / Codex
  • Documentation for attaching an MCP-compliant client to Etch

The hosted Etch service source is proprietary and lives in a separate repository. Nothing in this repository is required to be inspected or modified in order to use Etch.

Try in 30 seconds, no signup

curl -X POST https://etch.systems/v1/your-project

The response returns a bearer token, an MCP endpoint URL, and an anonymous project id. Point any MCP-compliant client at https://etch.systems/mcp with the token. Anonymous projects carry 500 signed events over 14 days; convert to a persistent project any time to keep the chain forever.

Full walk-through: etch.systems/docs/quickstart.

Per-client config

Claude Code

~/.claude/settings.json:

{
  "mcpServers": {
    "etch": {
      "url": "https://etch.systems/mcp",
      "headers": {
        "Authorization": "Bearer wm_YOUR_ANON_TOKEN"
      }
    }
  }
}
Cursor

~/.cursor/mcp.json (or .cursor/mcp.json at the project root):

{
  "mcpServers": {
    "etch": {
      "url": "https://etch.systems/mcp",
      "headers": {
        "Authorization": "Bearer wm_YOUR_ANON_TOKEN"
      }
    }
  }
}
Continue

~/.continue/config.yaml:

mcpServers:
  - name: etch
    url: https://etch.systems/mcp
    headers:
      Authorization: Bearer wm_YOUR_ANON_TOKEN
Cline (VS Code)

~/.config/Cline/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json:

{
  "mcpServers": {
    "etch": {
      "url": "https://etch.systems/mcp",
      "headers": {
        "Authorization": "Bearer wm_YOUR_ANON_TOKEN"
      }
    }
  }
}
Codex CLI

~/.codex/config.toml:

[mcp_servers.etch]
url = "https://etch.systems/mcp"
headers = { Authorization = "Bearer wm_YOUR_ANON_TOKEN" }

Per-client documentation with current config file locations is kept up-to-date at etch.systems/docs/mcp-clients.

Verify

Every event Etch signs is verifiable offline against pinned public keys with the OSS reference verifier. Auditors pin fingerprints once at pilot onboarding; every past epoch is verifiable indefinitely without contacting Etch.

What Etch is NOT

  • Not a media-provenance envelope (that lane is C2PA and SPIF). Etch signs decisions, not content. Comparison: etch.systems/vs/c2pa.
  • Not a transparency log (that lane is Sigstore Rekor). Etch is a per-project chain that anchors epochs on Rekor. Comparison: etch.systems/vs/sigstore-rekor.
  • Not a watermarking system. Etch records who reviewed an output and what they applied, not whether a specific model touched the text.

License

The metadata and documentation in this repository are MIT-licensed (see LICENSE). The hosted Etch service is Business Source License 1.1 with a hosted-service restriction; see etch.systems/pricing for terms.

Registry listings

Etch is listed on:

PulseMCP auto-indexes from the Official MCP Registry when their intake resumes; no separate submission needed.

For issues with the hosted service, contact via etch.systems. For issues with the metadata or integration examples in this repository, open a GitHub issue here.

Questions fréquentes

Qu'est-ce que io.github.SaravananJaichandar/etch ?

Etch is a signed audit chain for AI agent decisions, offline-verifiable against pinned public keys.

Comment installer io.github.SaravananJaichandar/etch ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http etch 'https://etch.systems/mcp' --header 'Authorization: <Bearer token. For zero-signup try-it-now (500 events, 14-day retention), run: curl -X POST https://etch.systems/v1/your-project. The response returns a token; use '\''Bearer <token>'\'' as the header value. For a persistent project token, sign up at https://etch.systems/signup.>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.SaravananJaichandar/etch ?

Oui. Il attend Authorization, à renseigner dans sa configuration.

io.github.SaravananJaichandar/etch est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.SaravananJaichandar/etch ?

Il est publié par SaravananJaichandar. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.