Skip to content
Claidex logo

Claidex MCP server

Which MCP servers are Claidex's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to Claidex

Whose server it is
  • Registry namecom.claidex/failure-intelligenceverified in the MCP registry

The registry name sits under claidex.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools24
  • Server calls itselfclaidex
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 177 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Trace terminated clinical trials back to their preclinical hypotheses; Read sourced mechanistic post-mortems of failed drug programs; Review failure mechanisms behind terminated oncology and neurology trials.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "Trace terminated clinical trials back to their preclinical hypotheses", the likely first call is search_claims.
  • For "Read sourced mechanistic post-mortems of failed drug programs", the likely first call is search_claims.
  • For "Review failure mechanisms behind terminated oncology and neurology trials", the likely first call is search_claims.
  • Parameters are untyped or undescribed in 14 of 24 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • What an agent can do with it3 of 3 use cases
  • Use10 npm downloads a week
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer728 ms
  • Space in an agent's context≈ 3,695 tokensthe definitions of all its tools (24), which an agent carries on every turn
  • Tool definitionsC · 74 of 100
  • Typed results0 of 24 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 14 of 24
  • Not saying whether it only reads or can destroy: 24 of 24

What an agent can do with it

  • can do · Trace terminated clinical trials back to their preclinical hypotheses
  • can do · Read sourced mechanistic post-mortems of failed drug programs
  • can do · Review failure mechanisms behind terminated oncology and neurology trials

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers24 tools · read 2026-10-24
  • claidex_capabilities

    Return the Claidex MCP feature map, configured storage/model providers, safety controls, resources, prompts, and tool counts.

  • claidex_claim_risk_matrix

    Search claims and summarize MRS bands, trial phases, failure archetypes, and high-risk programs for rapid diligence.

  • claidex_health_snapshot

    Return Sentinel metrics, coverage, graph counts, recent automation runs, MRS bands, and preprint-watch summaries.

  • claidex_research_prompt

    Compose a rigorous, reusable investigation prompt that tells an MCP client which Claidex tools and resources to use.

  • claidex_tool_catalog

    Return the complete MCP tool catalog, optionally including full input schemas and filtering native versus agent-backed tools.

  • consult_specialist_model

    Ask a specialist Gateway model for code, database/tool-calling, statistics, literature, preprint, or mechanistic synthesis support. Use for hard subproblems, second opinions, code generation/review, or complex synthesis.

  • fetch

    Fetch a specific result returned by search. This compatibility tool supports OpenAI and ChatGPT remote MCP retrieval flows.

  • fetch_research_url

    Fetch a public HTTPS research URL, JSON API response, package metadata endpoint, documentation page, or dataset preview. Blocks private/internal hosts and truncates large responses.

  • get_claim_content

    Retrieve the complete text content of a specific Claidex Claim by its slug. Use this when you need to read the full post-mortem analysis, including hypothesis, failure mechanism, and prevention analysis.

  • query_chembl

    Look up a drug or compound in ChEMBL. Returns mechanism of action, primary target, ChEMBL ID, max development phase, molecular type, and synonyms.

  • query_clinicaltrials

    Search ClinicalTrials.gov for clinical trials. Can search by drug name, condition, target, or NCT ID. Returns trial status, phase, sponsor, primary endpoints, and why_stopped if terminated.

  • query_failure_graph

    Query the Claidex failure graph for a specific gene target. Returns the Mechanism Risk Score (MRS), failure counts by phase and archetype, and all related claim slugs.

  • query_openfda

    Query the FDA FAERS database for adverse event signals for a drug. Returns top adverse event terms, serious case count, and death count.

  • query_opentargets

    Query Open Targets for target-disease association evidence. Returns genetic evidence score, clinical evidence, known drugs, tractability, and safety liabilities for a gene-disease pair.

  • query_package_registry

    Look up package metadata from npm or PyPI before recommending code, analysis packages, API clients, or dataset tooling.

  • rank_documents_by_embedding

    Embed a query and candidate documents, then rank documents by cosine similarity. Use for semantic matching, retrieval checks, clustering triage, and lightweight RAG over user-provided passages.

  • rerank_documents

    Rerank candidate documents/passages against a query using a dedicated reranking model. Use after retrieval/search when exact relevance ordering matters.

  • run_computation

    Evaluate deterministic mathematical expressions with optional variables. Use for algebra, matrices, vectors, transformations, descriptive numerical checks, and reproducible calculations. Does not execute arbitrary JavaScript or install…

  • run_statistical_analysis

    Run a statistical analysis computation. Supports: Wilson confidence intervals, binomial proportions, phase transition success rates, power calculations, Bayesian posterior estimates, descriptive statistics, and two-proportion comparisons…

  • search

    Search Claidex failure claims and preprint flags. This compatibility tool returns citation-ready results for OpenAI and ChatGPT remote MCP flows.

  • search_claims

    Search the Claidex failure database for post-mortems matching a drug name, gene target, disease, failure archetype, or sponsor. Returns matching claims with title, slug, drug, target, disease, phase, failure archetype, Open Targets score…

  • search_preprint_flags

    Search the Claidex Preprint Watch database for bioRxiv preprints flagged as contradicting the clinical failure record. Search by target gene, disease, or preprint title.

  • search_pubmed

    Search PubMed for biomedical literature. Returns title, authors, journal, year, DOI, abstract, and PMID for each result.

  • web_search

    Search the web for recent news, investor commentary, analyst notes, press releases, and conference coverage about drugs, clinical trials, or biomedical mechanisms.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "failure-intelligence": {
      "type": "http",
      "url": "https://app.claidex.com/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http claidex https://app.claidex.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://app.claidex.com/api/mcp as a custom connector in the settings.

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.