Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
CEM is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
CEM's published research on building with AI: definitions, papers, calculators and the CEM Score.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http cem-mcp https://mcp.cemresearchproject.org/mcp
# 2 — ask your agent for something these tools do
# ui_list, ui_search, ui_get and 11 more
CEM costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CEAll 1 server
cemresearchproject1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http cem-mcp https://mcp.cemresearchproject.org/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The CEM UI kit (cem-ui registry/): tokens, brand assets, layout primitives, utilities, engines, frames, templates, components (one per job) and the old partials. Without a kind, the count of each kind and their ids; with one, every entry of that kind. Kinds: token, asset, primitive, utility, engine, frame, template, component, partial.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | Only this kind |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words to find, e.g. "site header" or "tabs" |
| kind | string | no | Only this kind |
| limit | integer | no | At most this many (default 20) |
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 name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Id, x- tag or name |
| kind | string | no | Only this kind, when an id is shared |
The CEM design laws, cem-ui LAWS.md, the one rules document. Without a law, the whole file. With a number (1 to 20), that law as written. With words ("accent edge", "white"), every law that holds all of them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| law | string | no | A law number, or words to find in the laws |
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 checks cem-ui's own css/ and templates/; it takes no other repo. With a check name, every finding for that check (laws.mjs --list). Never records a baseline.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check | string | no | One check, e.g. "no-accent-edge" or "surface-ladder" |
The 21 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 CRP is up.
No parameter schema on file.
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 (templates/tool-calcs/{slug}.blade.php: the recalc function, the helpers it calls and its constants), and the citation it gives.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | e.g. "drift-tax", "build-compression" |
Score answers to the CEM Score self-assessment (24 questions, 12 dimensions) by the calculator's own rules (cem-ui templates/tool-calcs/cem-score.blade.php: getDimGrade, updateScores). Without answers, the 24 questions with each answer's score. Answers are keyed by question (d1q1 … d12q2), each the chosen answer's score, 1 to 5. Nothing is stored.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | no | e.g. {"d1q1": 5, "d1q2": 4} |
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 and pages. Every word must match the title, full title, summary or code. Returns each result's code, title, kind and address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words or a code, e.g. "drift tax", "DOI-07", "PB-011" |
| kind | string | no | Only this kind, as the index names it, e.g. "Playbook", "Tool", "Page" |
| limit | integer | no | At most this many (default 10) |
Find CEM's reviews of software tools (reviews.cemresearchproject.org): tool reviews, product pages with their listed prices, buying guides and categories, by words. Every word must match the title or summary. Returns each result's title, kind, summary and page. These are reviews of tools, separate from CEM's research.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words, e.g. "newsletter", "shopify page builder", "beehiiv" |
| kind | string | no | Only this kind |
| limit | integer | no | At most this many (default 10) |
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_index table). Only codes CRP lists publicly are served.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The code, e.g. "DOI-07" |
| max_chars | integer | no | Cut the markdown at this many characters (default 60000) |
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 operator levels, and for questions about building or operating with AI that CEM's research covers. Returns CEM's own definition with its code (cite it, e.g. F-003) and the best research documents, each with its code, one-line summary and page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The question, e.g. "What is the Pendulum?" |
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 deeper or wants more than the definition and documents give: for what a term means, cem_answer is the answer, free and instant. At most 100 written answers a day across every channel; past that, or when the AI account can't answer, it returns
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The question |
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 published positions that bear on the question, each with when it applies, and the closest published research; write the answer from them in your own words and keep his positions apart from what you infer. With deeper: true, a written answe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | What to ask OP-01, e.g. "Should I raise money or build with what I have?" |
| deeper | boolean | no | A written answer in his voice (counts on the daily limit) |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install CEM or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.1.0 · scanned 8 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestc56ed46f6c41b7657ec06e48fc7b722d4e84cce8c2d0bc53da85c1990f857600
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ui_list | no tags | |
| ui_search | no tags | |
| ui_get | no tags | |
| ui_laws | no tags | |
| ui_check | no tags | |
| calculators_list | no tags | |
| calculator_get | no tags | |
| cem_score | no tags | |
| research_search | no tags | |
| reviews_search | no tags | |
| research_get | no tags | |
| cem_answer | no tags | |
| ask_cem | no tags | |
| ask_op01 | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc56ed46f6c41b765
Scanned2026-11-08
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish CEM can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.