etch
# etch-mcp
[](https://glama.ai/mcp/servers/SaravananJaichandar/etch-mcp)
[](https://mcpservers.org/servers/saravananjaichandar/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](https://etch.systems), 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](https://etch.systems/docs/quickstart).
## Per-client config
### Claude Code
`~/.claude/settings.json`:
```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):
```json
{
"mcpServers": {
"etch": {
"url": "https://etch.systems/mcp",
"headers": {
"Authorization": "Bearer wm_YOUR_ANON_TOKEN"
}
}
}
}
```
### Continue
`~/.continue/config.yaml`:
```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`:
```json
{
"mcpServers": {
"etch": {
"url": "https://etch.systems/mcp",
"headers": {
"Authorization": "Bearer wm_YOUR_ANON_TOKEN"
}
}
}
}
```
### Codex CLI
`~/.codex/config.toml`:
```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](https://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.
- Reference verifier posture and benchmark numbers: [etch.systems](https://etch.systems)
- Framework mapping (SR 11-7, EU AI Act Article 12, ISO 42001, NIST AI RMF): [etch.systems/aarm](https://etch.systems/aarm)
- FAQ: [etch.systems/docs/faq](https://etch.systems/docs/faq)
## 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](https://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](https://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](https://etch.systems/pricing) for terms.
## Registry listings
Etch is listed on:
- [Official MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.SaravananJaichandar/etch`
- [Glama.ai MCP servers](https://glama.ai/mcp/servers) (auto-indexed from `glama.json` in this repo)
- [mcpservers.org](https://mcpservers.org/servers/saravananjaichandar/etch-mcp)
- [punkpeye/awesome-mcp-servers](https://github.com/punkpeye/awesome-mcp-servers) under Knowledge & Memory
- [agentrust-io/awesome-ai-governance](https://github.com/agentrust-io/awesome-ai-governance) under Agent Identity & Attestation
- [ottosulin/awesome-ai-security](https://github.com/ottosulin/awesome-ai-security) under MCP Security
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](https://etch.systems). For issues with the metadata or integration examples in this repository, open a GitHub issue here.
TDQS
Scored across 31 tools
Most tools have clearly distinct purposes (e.g., query_fact vs. search_global, record_decision vs. record_correction). A few pairs like get_constraints/get_agents_md_constraints and simulate_change/validate_change have some overlap, but the descriptions differentiate them sufficiently for an agent to choose correctly.
All tool names follow a consistent verb_noun pattern in snake_case (get_*, record_*, predict_*, etc.). Even compound names like get_co_edit_suggestions and prove_entry_inclusion maintain the pattern without mixing conventions.
With 31 tools, the surface is significantly larger than the typical well-scoped server. While the server covers a broad domain, this count places a heavy burden on agent selection and navigation, likely reducing overall coherence.
The tool set covers a comprehensive lifecycle: seeding, ingestion, querying, validation, prediction, audit, and export. Minor gaps exist, such as no explicit update/delete for facts or constraints, but these are likely handled internally, so core workflows are supported without dead ends.