# Jam MCP vs Momentic MCP server (slim)

> Jam MCP scores 51.5 (D) to Momentic's 45.1 (E) for browser debug. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/jam-mcp-vs-momentic-mcp.md (~2,450 tokens) · this version ~1,480 tokens · JSON https://www.anchorterminal.com/compare/jam-mcp-vs-momentic-mcp.json · canonical https://www.anchorterminal.com/compare/jam-mcp-vs-momentic-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Jam MCP scores 51.5 (D) on agent readiness against Momentic MCP server's 45.1 (E), and leads in 5 of 7 scored categories. Both do browser debug.

- Jam MCP: D 51.5, rank #1024 of 1510 · https://www.anchorterminal.com/tools/jam-mcp.min.md
- Momentic MCP server: E 45.1, rank #1207 of 1510 · https://www.anchorterminal.com/tools/momentic-mcp.min.md
- Jam MCP, good for Engineering teams that file bugs with Jam and want a coding agent to read the recording and fix the bug. Ahead on Schema & documentation, 55 against 50; Agent ergonomics, 50 against 33; Security & auth, 63 against 56; Payments & pricing, 40 against 30; Maintenance & community, 60 against 53.
- Momentic MCP server, good for Engineering teams who want an assistant to bug-bash deployed apps and pull requests with Momentic.

| Category | Jam MCP | Momentic MCP server |
| --- | --- | --- |
| Reliability (16%) | 45 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 55 | 50 |
| Agent ergonomics (13%) | 50 | 33 |
| Security & auth (14%) | 63 | 56 |
| Payments & pricing (10%) | 40 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 60 | 53 |
| Transparency & trust (7%) | 48 | 50 |

| Fact (where they differ) | Jam MCP | Momentic MCP server |
| --- | --- | --- |
| Vendor | Jam | Momentic |
| Hosted endpoint | `https://mcp.jam.dev/mcp` | `https://mcp.momentic.ai` |
| Tools exposed | 37 | none |
| MCP registry | `dev.jam/jam` | `ai.momentic/momentic` |
| Privacy policy last updated | not read yet | no document linked |

Why the edge:
- Agent ergonomics, Jam MCP +17: Jam MCP 50 (About 37 tools (5), with a getDetails snapshot that suggests which tools to try next (5 back). Filters and limits on network requests and search (14 of 20). No documented errors (3 of 20). Delete tools exist (deleteJam, deleteFolder, deleteComment); annotations not read (8 of 20). A CLI with the same fields for every tool (15). 10 + 14 + 3 + 8 + 15 = 50.); Momentic MCP server 33 (Tool count not read (5). Sessions are followed and reviewed rather than dumped (10 of 20). No documented errors (3 of 20). Annotations not read (5 of 20). OAuth on one URL and a CLI (10 of 15). 5 + 10 + 3 + 5 + 10 = 33.)
- Payments & pricing, Jam MCP +10: Jam MCP 40 (No machine payment protocol (0). Public per-seat price ($14) (10). Free plan for everyone (20). Personal access tokens exist but a person creates them after a browser sign-up (10 of 20). 0 + 10 + 20 + 10 = 40.); Momentic MCP server 30 (No machine payment protocol (0). Plan prices public (10). Free plan with $50 of usage a month (20). A person signs up and approves OAuth (0). 0 + 10 + 20 + 0 = 30.)
- Security & auth, Jam MCP +7: Jam MCP 63 (OAuth, or a personal access token for CI; no scopes published (20 of 30). Calls are bounded by what the user can see; no read-only mode (8 of 20). Recordings carry console logs, network bodies and page text from the recorded site, and no injection guidance was found (3 of 15). Workspace audit logs listed among security controls (12 of 15). SOC 2 Type II with annual audits and quarterly vulnerability assessments; no security.txt (404) (20). 20 + 8 + 3 + 12 + 20 = 63.); Momentic MCP server 56 (OAuth only, no API keys on the remote server (22 of 30). Sessions run against apps the user points at; no read-only mode documented (5 of 20). The agent reads pages of the app under test; no injection guidance in the docs read (3 of 15). Session and run history in the dashboard (8 of 15). SOC 2 Type 2 with annual penetration tests, zero-data-retention agreements with model providers, and request headers scrubbed from traces (18 of 20). 22 + 5 + 3 + 8 + 18 = 56.)
- Maintenance & community, Jam MCP +7: Jam MCP 60 (Registry version 1.36.3 updated 3 November 2026 (30). Dated changelog not found to count, though the registry version implies frequent releases (10 of 20). Help centre and feedback tool, no public changelog (10 of 15). Official registry entry dev.jam/jam (10 of 15, its repository field points at a skills repository). No package to read (0). 30 + 10 + 10 + 10 + 0 = 60. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.); Momentic MCP server 53 (Registry entry ai.momentic/momentic updated 3 November 2026 (30). Dated releases not counted (0). Docs and support; changelog not read (8 of 15). Official registry entry under its own namespace (15). No package read (0). 30 + 0 + 8 + 15 + 0 = 53. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.)
- Schema & documentation, Jam MCP +5: Jam MCP 55 (Typed schemas by protocol, not read without sign-in (15 of 25). llms.txt (10). Every tool has a sentence on what it returns, and some say when to use them (15 of 20). Filters documented for getNetworkRequests (statusCode, contentType, host, method, limit, after) (8 of 15). Example prompts, no error responses (5 of 15). Versioned in the registry (1.36.3); no public changelog found (2 of 15). 15 + 10 + 15 + 8 + 5 + 2 = 55.); Momentic MCP server 50 (Schemas not read without sign-in (15 of 25). llms.txt (10). Docs describe what sessions and runs the agent can start and review (10 of 20). Inputs not verifiable (5 of 15). Example flows, no error responses (5 of 15). Registry 1.0.1 on 3 November; docs changelog not read (5 of 15). 15 + 10 + 10 + 5 + 5 + 5 = 50.)