mcpField
E
etch

etch

Remote
github.com/SaravananJaichandarSecurity0Updated 9w ago
Repository

About etch

etch is an MCP integration for a hosted service that records AI agent decisions in a signed audit chain. It is intended for teams that need events to remain verifiable offline against pinned public keys.

Key features

  1. 01Signed audit chain for agent decisions
  2. 02Offline verification with pinned public keys
  3. 03Per-client MCP setup examples
  4. 04Anonymous project creation

Use cases

  1. 01Keep a verifiable record of agent decisions
  2. 02Audit past events without contacting Etch
  3. 03Connect Claude Code or Cursor to Etch

MCP support

Provides the integration surface for connecting MCP-compliant clients to the hosted Etch service. Clients use its MCP endpoint with a bearer token.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://etch.systems/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://etch.systems/mcpAuth required

Tools

Details

From the project README

etch-mcp

etch-mcp MCP server Listed on mcpservers.org

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.