# Cemresearchproject Cem MCP server

Source: https://glimind.com/server/mcp-registry%2Forg.cemresearchproject%2Fcem
Registry id: `mcp-registry/org.cemresearchproject/cem`
Status: live (checked 2026-11-22T18:38:25.862Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 703
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "cemresearchproject-cem-mcp-server": {
      "type": "http",
      "url": "https://mcp.cemresearchproject.org/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http cemresearchproject-cem-mcp-server https://mcp.cemresearchproject.org/mcp
```

## Tools (13)

- `ask_cem`: A longer written answer from CEM's research, with the passages it drew on and their pages. Use it only after cem_answer, and only when the person asks to go dee
- `ask_op01`: OP-01's view: the operator in CEM's research, the one person whose every commit, session and dollar the research measures. By default, free and instant: OP-01's
- `calculator_get`: One calculator: what it measures (cem-ui registry/tools.json), its inputs with their defaults, and its formula as the calculator's own code computes it (templat
- `calculators_list`: The CEM calculators, the same on every site (cem-ui registry/tools.json), with what each measures, and its page and formula code from CRP's search index when CR
- `cem_answer`: Use for any question about CEM (the Compounding Execution Method) or a term it defines, such as the Drift Tax, the Pendulum, the Governor, Sweeps, Cycles or ope
- `research_get`: One public CEM document by its code (DOI-07, PB-011, …): its entry in CRP's search index and its markdown from work-hub content/ (located through the content_in
- `research_search`: Find CEM research by words or code in CRP's public search index (GET /search/index.json): papers, playbooks, case studies, book chapters, figures, calculators a
- `reviews_search`: Find CEM's reviews of software tools (reviews.cemresearchproject.org): tool reviews, product pages with their listed prices, buying guides and categories, by wo
- `ui_check`: Run cem-ui's laws check (scripts/laws.mjs, `npm run laws`) and return its table: each law's check, the count now, and the baseline it may not rise above. It che
- `ui_get`: One UI kit entry in full, as cem-ui registry/ records it: by id ("site-header", "shell", "spacing", "CRP:ask-cem-panel"), component tag ("x-site-header") or nam
- `ui_laws`: The CEM design laws, cem-ui LAWS.md, the one rules document. Without a law, the whole file. With a number (1 to 16), that law as written. With words ("accent ed
- `ui_list`: The CEM UI kit (cem-ui registry/): tokens, brand assets, layout primitives, utilities, engines, frames, templates, components (one per job) and the old partials
- `ui_search`: Find UI kit entries (cem-ui registry/) whose id, name or any recorded field holds every word of the query. Returns the best matches, id first.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
