Name: Claimora
Author: claimora

Claimora MCP

Scientific and legal claim graph. Query claims, evidence, contradictions, and innovation flags.

Tool-list grade A Remote · Streamable HTTP API key 8 tools v0.1.0

No reviews yet by claimora The publisher’s own endpoint — this marketplace is not in the path

96/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Scientific and legal claim graph. Query claims, evidence, contradictions, and innovation flags.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http claimora-mcp https://claimora.si/mcp --header 'X-Claimora-Paid-Token: ${X_CLAIMORA_PAID_TOKEN}'

# 2 — ask your agent for something these tools do
#   query_claims, get_evidence, get_contradictions and 5 more

It needs X_CLAIMORA_PAID_TOKEN (Free tier is 10 calls per day. Paid calls are 0.01 USDC. Token from https://claimora.si/credits): this sends it in the X-Claimora-Paid-Token header from your environment, so export it first — its endpoint answers 401 without it.

Claimora costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

claimora1 server

1 category

All 1 server

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 Code reads X_CLAIMORA_PAID_TOKEN (Free tier is 10 calls per day. Paid calls are 0.01 USDC. Token from https://claimora.si/credits) from your environment each time it connects and sends it in the X-Claimora-Paid-Token header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx X_CLAIMORA_PAID_TOKEN … and open a new terminal (Windows).

claude mcp add --scope user --transport http claimora-mcp https://claimora.si/mcp --header 'X-Claimora-Paid-Token: ${X_CLAIMORA_PAID_TOKEN}'

Reconnect, 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 — but its publisher asks for a key of their own on every call.

What it asks of you

Nothing is required, but it can take X-Claimora-Paid-Token header (Free tier is 10 calls per day. Paid calls are 0.01 USDC. Token from https://claimora.si/credits.) if you want to set it.

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

8 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.

Only tools that write or reach the network

Search claim statements and excerpts, strongest matches first. Use this when you have keywords or a domain and want the strongest matching claims. Returns claim id, status, evidence strength, and a shortened excerpt. Example: query_claims(query="transformer", domain="ai-ml", limit=5). Example: query_claims(query="United States", domain="data-protection", limit=5).

Parameter	Type	Required	Notes
query	string	yes	Text matched against the claim statement and its excerpt. Example: transformer.
domain		no	Restrict results to one domain. Example: ai-ml.
filters		no	Optional status, minimum evidence strength, and assertion type. Example: {"status": "consensus", "min_strength": 0.6}.
limit	integer	no	Page size. Example: 5.
offset	integer	no	Number of hits to skip. Example: 0.

Provenance for one claim. Excerpts are short unless full_text is true. Use this after a search when you have a claim id and need the papers behind it. Example: get_evidence(claim_id="claim-attention"). Example: get_evidence(claim_id="claim-attention", full_text=true).

Parameter	Type	Required	Notes
claim_id	string	yes	Claim id returned by a search tool. Example: claim-attention.
full_text	boolean	no	Return stored excerpts without shortening. Example: false.

List claims stored as contradicting one claim. Returns each opposing claim id, status, evidence strength, and opposition strength. Example: get_contradictions(claim_id="<id from query_claims>").

Parameter	Type	Required	Notes
claim_id	string	yes	Claim id to inspect.

List claims whose last_updated is at or after a timestamp. Use this to read claims that changed after a time you already checked. Returns claim id, status, evidence strength, and a shortened excerpt. Example: get_updates(since="2026-01-01T00:00:00Z", domain="ai-ml", limit=20). Example: get_updates(since="2026-10-01T00:00:00Z", domain="consciousness", offset=20).

Parameter	Type	Required	Notes
since	string	yes	ISO-8601 timestamp. Claims updated at or after this time. Example: 2026-01-01T00:00:00Z.
domain		no	Restrict results to one domain. Example: ai-ml.
limit	integer	no	Page size. Example: 20.
offset	integer	no	Number of hits to skip. Example: 0.

List innovation flags, strongest first. Use this when you want links between claims rather than the claims themselves. Returns flag id, domain, summary, strength, and the claim ids on each path. Example: get_innovation_flags(domain="ai-ml", min_strength=0.5, limit=10). Example: get_innovation_flags(domain="quantum", min_strength=0.8, limit=5).

Parameter	Type	Required	Notes
domain		no	Restrict flags to one domain. Example: ai-ml.
min_strength		no	Drop flags below this strength, from 0 to 1. Example: 0.5.
limit	integer	no	Page size. Example: 10.
offset	integer	no	Number of hits to skip. Example: 0.

Find claims from a natural-language question. This build matches text only. Use this when the input is a question instead of keywords. Example: search_smart(natural_language="How do transformers handle long context?", domain="ai-ml", limit=5). Example: search_smart(natural_language="What limits healthspan?", domain="longevity", limit=5).

Parameter	Type	Required	Notes
natural_language	string	yes	A question or description of the claims you want. Example: How do transformers handle long context?
domain		no	Restrict results to one domain. Example: ai-ml.
limit	integer	no	Page size. Example: 5.
offset	integer	no	Number of hits to skip. Example: 0.

List authors linked to one claim. Use this when you have a claim id and need the people linked to it. Returns author id, name, and orcid. The list is empty when none are linked. Example: get_authors(claim_id="claim-attention"). Example: get_authors(claim_id="<id from query_claims>").

Parameter	Type	Required	Notes
claim_id	string	yes	Claim id returned by a search tool. Example: claim-attention.

List law records for one jurisdiction and area of law. Use this when you want jurisdiction-scoped records. Omitting jurisdiction returns science claims. Returns record id, status, evidence strength, a shortened excerpt, jurisdiction, and area of law. Example: query_law(jurisdiction="DE", area_of_law="data-protection", query="consent", limit=5). Example: query_law(query="transforme

Parameter	Type	Required	Notes
jurisdiction		no	Jurisdiction code. Example: DE. Omit it to search science.
area_of_law		no	Area of law slug. Example: data-protection.
query	string	no	Text matched against the statement and its excerpt. Example: consent.
limit	integer	no	Page size. Example: 5.

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

Nothing here is billable: mcprush charges nothing to install Claimora or to call it, at any volume.

ATool-list grade · score 96 / 100

Release 0.1.0 · scanned 28 Oct 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 digestc8730169f5b5e3f1d582f1b5dbc098de8dc8de1ced3dd5b81bc48f0583695243

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
query_claims	no tags
get_evidence	no tags
get_contradictions	no tags
get_updates	no tags
get_innovation_flags	no tags
search_smart	no tags
get_authors	no tags
query_law	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 digestc8730169f5b5e3f1

Scanned2026-10-28

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.