| FMRS | 60 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 18 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - MCP server developers who need rich interactive UI inside tool call results
- Teams already using hosts that support the MCP Apps extension (Claude, ChatGPT, VS Code, Goose, Postman)
- Developers who want official spec-compliant starter templates across multiple front-end frameworks (React, Vue, Svelte, Preact, Solid, vanilla JS)
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| Not for | - Users looking for a single ready-to-use MCP server/tool — this repo is a protocol spec, SDK, and example collection, not one server
- Setups where the client host doesn't support the MCP Apps extension (README states host support varies)
- Anyone needing a production-supported, officially maintained host implementation — README explicitly says there's no supported host in the repo beyond the reference basic-host example
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| Required permissions | - The spec/SDK itself carries no inherent permissions; specific permissions depend on which example server is used (e.g., the system-monitor example reads local OS metrics, the video-resource example serves binary media resources)
- README does not provide a complete permissions manifest for any single server
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| Risks and side effects | - UI content runs as server-supplied HTML inside a sandboxed iframe on the host — the actual isolation and trust boundary depend on the specific host implementation, not on this repo
- The spec has both a stable 2026-01-26 version and an actively developed draft version, so interfaces may change as the spec evolves
- License labeling is inconsistent — the README badge shows Apache 2.0 while the repo's catalog metadata records NOASSERTION — verify actual license terms before use
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 0 | 0 |
|---|