Skip to content

Claimora MCP server

si.claimora/claimoraclaimora.sistreamable-httpv0.1.0Scanned

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

7 tools: 7 only read.

Tools: 0 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Claimora MCP server can do

The Claimora MCP server is published by claimora.si, a domain the MCP Registry verified. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 3 findings (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Only reads 7Show 7 read-only tools
  • get_authorsList authors linked to one claim.No findings

    Why it is in this group

    • The name "get_authors" says "get": a word for reading.
    Description, as the server wrote it
    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>").
  • get_contradictionsList claims stored as contradicting one claim.No findings

    Why it is in this group

    • The name "get_contradictions" says "get": a word for reading.
    Description, as the server wrote it
    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>").
  • get_evidenceProvenance for one claim.No findings

    Why it is in this group

    • The name "get_evidence" says "get": a word for reading.
    Description, as the server wrote it
    Provenance for one claim. Excerpts are short unless full_text is true. unpublished is true for a private unpublished paper. The stored excerpt, page, and section stay on provenance. An empty provenance doi is filled from a DOI already stored on that row, including the DataCite DOI of an arXiv id. The graph is not written. status_note on a consensus claim with no stored contradiction is: No stored contradiction; not independent multi-source consensus. When no independent supporting claim is present, the note also says: Single-source claim; not multi-source consensus. evidence_note is: Extractor confidence in the claim statement, not study quality. A previously read source role is appended when one is known. When that role is absent, one statement cue appends a single Role line. A clear finding is not labeled method or background, a hedge is a limitation, and a statement with no cue has no Role line. integrity_warning is set when the statement unit looks truncated relative to the excerpt, or the magnitude looks extreme relative to the excerpt. The statement and the excerpt are not rewritten. 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).
  • get_innovation_flagsList innovation flags.1 finding

    Why it is in this group

    • The name "get_innovation_flags" says "get": a word for reading.

    Findings

    • Info

      The description is 3,331 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "..._innovation_flags(domain="consciousness", cross_domain_only=True, limit=10)."

      What this check looks for
    Description, as the server wrote it
    List innovation flags. The default sort is discovery. Use this when you want links between claims rather than the claims themselves. Pass claim_id to navigate from one claim to the flags that contain it. Each hit includes flag_type, strength, summary, the other claim ids, and those claims' primary domains. Filters are flag_type, min_strength, and cross_domain_only. The claim list is ranked by relationship strength and novelty. A path that only names the claim, a partner that repeats the claim, and a near-duplicate of a partner already returned are omitted. Discovery combines relationship strength, novelty, and conceptual overlap. A near-copy, a stock template, a lexical basis, or flag_type lexical or lexical_association is left off the default strength and discovery lists. The stored row is not changed. A claim_id lookup still returns that flag. flag_type lexical or lexical_association still returns that class. sort strength orders by the stored relationship strength. Every flag includes flag_type, cross_domain, complementary, and summary. summary says why the claims are linked. A lexical relationship_basis adds “Shared vocabulary only. No substantive mechanism was established.” on read. The stored summary is not rewritten. complementary is a ranking hint when two independent sources share a measurable variable or process and discuss different aspects. It reuses relationship_basis, does not change flag_type, and does not state a hypothesis. A weak link stays weak. flag_type is lexical_association for shared terminology with no substantive relation, scientific_connection for a conceptual or methodological relationship, contradiction for a stored disagreement, or innovation when the claims state a mechanism that could transfer. lexical selects the same weak rows. cross_domain is true when the claims have different primary domains. It is not a flag_type and does not raise strength. Older rows may still use cross_domain or research_hypothesis. strength is computed for that pair. It is not claim evidence strength. A weak lexical link stays low. min_strength 0 does not put it back on the default lists. Returns flag id, domain, summary, strength, flag_type, cross_domain, connected_domain, the claim ids on each path, and a claims array in that same order. Each claims item has claim_id, statement, and evidence strength. Full evidence stays on get_evidence. connected_domain is the primary domain of the claim that does not match the flag domain. It is null when the claims share a primary domain. Optional cross_domain_only, when true, returns only flags whose connected_domain is set. Optional flag_type keeps one label, for example lexical. Optional sort is discovery or strength. discovery is the default. Repeated claim paths return once, keeping the strongest flag for that pair. Example: get_innovation_flags(domain="ai-ml", min_strength=0.5, limit=10). Example: get_innovation_flags(domain="ai-ml", sort="strength", limit=10). Example: get_innovation_flags(claim_id="claim-attention", min_strength=0.5, limit=10). Example: get_innovation_flags(domain="quantum", min_strength=0, flag_type="lexical", limit=5). Example: get_innovation_flags(domain="consciousness", cross_domain_only=True, limit=10).
  • get_updatesList claims whose last_updated is at or after a timestamp.No findings

    Why it is in this group

    • The name "get_updates" says "get": a word for reading.
    Description, as the server wrote it
    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, a shortened excerpt, and source_url, doi, and paper_id when those are known. 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).
  • query_claimsSearch claim statements and excerpts.1 finding

    Why it is in this group

    • The name "query_claims" says "query": a word for reading.

    Findings

    • Info

      The description is 2,413 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ple: query_claims(query="United States", domain="data-protection", limit=5)."

      What this check looks for
    Description, as the server wrote it
    Search claim statements and excerpts. A domain keeps claims whose primary domain is that value or one of its aliases, such as cs.LG for ai-ml. An exact multi-token phrase matches whole tokens. A single ordinary token also matches its singular or plural. When no stored claim holds every token, statement hits for each token come before excerpt-only hits, a row with no content-term overlap is dropped, and match_reason starts with no stored co-occurrence. An empty remainder stays empty. K17, PDAC, NCC, IIT, and LLM match the full names in the alias map. Hits are ordered by keyword overlap, then a domain match, then evidence strength. That retrieval order stays ahead of the stored score. match_reason records that the stored score is evidence_strength. cross_domain also keeps claims from other domains that carry the domain as a secondary tag. When the query is one domain keyword and domain is omitted, claims in that domain come first. Use this when you have keywords or a domain and want the strongest matching claims. Returns claim id, status, evidence strength, a shortened excerpt, match_reason, source_url, doi, and paper_id when those are known, up to two supporting claims, and one contradicting claim when one is stored. Each related claim carries that same compact pointer. unpublished is true for a private unpublished paper. Full provenance stays on get_evidence. status_note on a consensus claim with no stored contradiction is: No stored contradiction; not independent multi-source consensus. When no independent supporting claim is present, the note also says: Single-source claim; not multi-source consensus. evidence_note is: Extractor confidence in the claim statement, not study quality. A previously read source role is appended when one is known. When that role is absent, one statement cue appends a single Role line. A clear finding is not labeled method or background, a hedge is a limitation, and a statement with no cue has no Role line. integrity_warning is set when the statement unit looks truncated relative to the excerpt, or the magnitude looks extreme relative to the excerpt. The statement and the excerpt are not rewritten. Example: query_claims(query="transformer", domain="ai-ml", limit=5). Example: query_claims(query="United States", domain="data-protection", limit=5).
  • search_smartFind claims from a natural-language question.1 finding

    Why it is in this group

    • The name "search_smart" says "search": a word for reading.

    Findings

    • Info

      The description is 2,813 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...natural_language="What causes LLM hallucinations in RAG systems?", limit=5)."

      What this check looks for
    Description, as the server wrote it
    Find claims from a natural-language question. The central research concept and its scientific synonyms outrank incidental context words. Generic overlap that does not address the question is penalized. A keyword with no function word stays on the lexical match. A question tries its content phrases first. When that match is thin, extracted concepts, shorter phrases, and synonyms are combined and deduplicated before ranking. Exact keywords are not required. Question hits stay on strategy question. fallback is null when the content-phrase match already addressed the concept, keyword when every hit came from a literal concept or shorter phrase, and expanded when a synonym supplied a hit. Rank puts the concept above context words. Retrieval relevance stays ahead of evidence_strength, and match_reason records that the stored score is evidence_strength. A lexical phrase matches whole tokens. K17, PDAC, NCC, IIT, and LLM match the full names in the alias map. notice is no_matching_claims when nothing matches. notice is no_evidence when every returned hit has an empty excerpt. A hit with an empty excerpt says no evidence in match_reason. exploratory true keeps matches under the default relevance threshold. Each hit includes match_reason, source_url, doi, and paper_id when those are known, up to two supporting claims, and one contradicting claim when one is stored. Each related claim carries that same compact pointer. unpublished is true for a private unpublished paper. Full provenance stays on get_evidence. status_note on a consensus claim with no stored contradiction is: No stored contradiction; not independent multi-source consensus. When no independent supporting claim is present, the note also says: Single-source claim; not multi-source consensus. evidence_note is: Extractor confidence in the claim statement, not study quality. A previously read source role is appended when one is known. When that role is absent, one statement cue appends a single Role line. A clear finding is not labeled method or background, a hedge is a limitation, and a statement with no cue has no Role line. integrity_warning is set when the statement unit looks truncated relative to the excerpt, or the magnitude looks extreme relative to the excerpt. The statement and the excerpt are not rewritten. A domain keeps claims whose primary domain is that value or one of its aliases. cross_domain also keeps claims from other domains that carry the domain as a secondary tag. 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 causes LLM hallucinations in RAG systems?", limit=5).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:24 UTC, unchanged since Oct 26, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

3 info
  • The description is 2,413 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ple: query_claims(query="United States", domain="data-protection", limit=5)."

    What this check looks for
  • The description is 3,331 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "..._innovation_flags(domain="consciousness", cross_domain_only=True, limit=10)."

    What this check looks for
  • The description is 2,813 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...natural_language="What causes LLM hallucinations in RAG systems?", limit=5)."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 6 changed.+1 added~6 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http claimora https://claimora.si/mcp
claude mcp add --transport http claimora https://claimora.si/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__claimora__query_claims",
      "mcp__claimora__get_evidence",
      "mcp__claimora__get_contradictions",
      "mcp__claimora__get_updates",
      "mcp__claimora__get_innovation_flags",
      "mcp__claimora__search_smart",
      "mcp__claimora__get_authors"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as claimora. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/si.claimora/claimora/verify?hash=022bf88d37a6cedcdf88bdbc059b227031efd7c6c00d63b49be7740aa50a73db" | jq -e '.changed == false'

Pinned hash 022bf88d37a6, from Nov 9, 2026, 07:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/si.claimora/claimora/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for si.claimora/claimora
[![Anlyon Radar](https://radar.anlyon.com/badge/si.claimora/claimora.svg)](https://radar.anlyon.com/servers/si.claimora/claimora)

Source: MCP Registry · repository. Synced Oct 25, 2026, 22:18 UTC.

Claimora MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Claimora MCP server safe?

No scan can promise that. What its definitions show: 7 tools, all of which only read, and 3 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Claimora MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Claimora MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Claimora MCP server have?

7 tools: 7 read. query_claims, get_evidence, get_contradictions, get_updates, get_innovation_flags, search_smart and get_authors.

Does the Claimora MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Claimora MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Claimora MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.