MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Claimscope 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.
99/100
trust score
175
downloads a day
local
runs on your machine
12
tools declared
What it does
Compare engine answers, inspect disagreement and grade study evidence for questions.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user claimscope-mcp '--' npx -y @reneturcios/claimscope mcp
# 2 — ask your agent for something these tools do
# ecca_synthesize, ecca_pre_mortem, ecca_decision_tournament and 9 more
Claimscope costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 381 servers
CloudCorpRecords381 servers
28 categories
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. This one runs on your machine: your client starts Claimscope as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user claimscope-mcp '--' npx -y @reneturcios/claimscope mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: 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 your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
12 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Compare answers from configured engines and inspect disagreement, with lexical similarity and final-answer agreement when measurable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The core inquiry, hypothesis, or decision challenge to synthesize. |
| model | string | no | Label echoed in the result. Every value dispatches through the same registered engines; depth decides fast or multi-engine. |
| depth | string | no | intuitive and fast route to one engine; executive, pioneer and deep route a multi-engine dispatch (free callers: two engines first, expanding on measured divergence, one deep solve per day). Any other |
| antagonist | boolean | no | When true, forces one engine to act as adversarial red-team antagonist. |
Executes an adversarial pre-mortem identifying failure modes and early warning indicators using empirical argument verification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| premise | string | yes | The strategic plan, architecture, or business premise to stress-test. |
| horizonMonths | integer | no | Time horizon in months to simulate forward failure modes. |
Evaluates multi-option decision matrix using minimax regret and Pareto ranking over candidate pathways.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| decisionContext | string | yes | Context of the decision to evaluate. |
| options | array | yes | List of discrete options or strategic pathways. |
Measures lexical and semantic divergence across candidate assertions to penalize sycophancy.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| assertions | array | yes | Array of candidate assertions or claims to measure divergence for. |
Use one keyed tier-quota slot to sharpen rough student questions without adding facts; return detected niches and refinement chips. A closed engine ceiling falls back locally.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The rough question or text to refine and sharpen. |
Use one keyed tier-quota slot and dispatch-ceiling reservation to fetch and grade studies from scholarly indexes; return fetched evidence and explicit gaps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The research question to fetch and grade studies for. |
| niche | string | no | Subject niche to focus the research on: psychology, learning, nutrition or money. |
Independently answer a question and compare the candidate against deterministic panel agreement. Show named dissent; spends one solve.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The question the candidate answer responds to. |
| candidate_answer | string | yes | The candidate answer to verify against the panel. |
Psychology research: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The psychology question to research and give a verdict on. |
Learning and study skills: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The learning / study-skills question to research and give a verdict on. |
Nutrition and supplements: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The nutrition / supplements question to research and give a verdict on. |
Money and business: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The money / business question to research and give a verdict on. |
Check one ecca.claim-protocol 1.0 document for shape: versioned, engine slots only (no vendor names), split causes from the published taxonomy, question text only with consent, seal present. Returns ok with the error list; validates shape, never the record behind it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | object | yes | The protocol document to check (docs/CLAIM_PROTOCOL.md). |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Claimscope 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: —
ATrust score 99 / 100
Release 0.1.0 · scanned 5 Nov 2026
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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digesta8f17276556ae2d09d5c87a3c4c35196ab109ebf8c9d35386ab5a758b2cde6b0
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digesta8f17276556ae2d0
Scanned2026-11-05
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
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 Claimscope 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.