Nullary MCP Server

https://mcp.nullary.ai/mcp Remote v1.0.1

Published by mcp.nullary.ai — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Negative results intelligence for drug discovery — query measured failures via MCP.

Trust grade
A
100/100
Last scanned get badge →
Trust
A · 100/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 100/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 0 = 100. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 35

Each tool and what it can reach — enumerated from the running server.

  • get_compoundno sensitive capability
  • get_coverageno sensitive capability
  • get_finding_provenanceno sensitive capability
  • get_model_cardno sensitive capability
  • get_target_landscapeno sensitive capability
  • list_modelsno sensitive capability
  • list_top_targetsno sensitive capability
  • search_adc_linker_failuresno sensitive capability
  • search_admet_failuresno sensitive capability
  • search_admet_failures_all_modalitiesno sensitive capability
Show 25 more tools ↓
  • search_ancestry_specific_failuresno sensitive capability
  • search_bispecific_format_failuresno sensitive capability
  • search_developability_failuresno sensitive capability
  • search_drug_drug_interaction_failuresno sensitive capability
  • search_failed_adcsno sensitive capability
  • search_failed_bispecificsno sensitive capability
  • search_failed_clinical_antibodiesno sensitive capability
  • search_failed_essentiality_screensno sensitive capability
  • search_failed_guidesno sensitive capability
  • search_failed_oligonucleotidesno sensitive capability
  • search_failed_peptide_therapeuticsno sensitive capability
  • search_failed_protacsno sensitive capability
  • search_failed_replicationsno sensitive capability
  • search_failed_selectivityno sensitive capability
  • search_failed_vaccinesno sensitive capability
  • search_inactive_compoundsno sensitive capability
  • search_indication_historyno sensitive capability
  • search_mechanism_failuresno sensitive capability
  • search_oligo_delivery_failuresno sensitive capability
  • search_pathogen_historyno sensitive capability
  • search_peptide_stability_issuesno sensitive capability
  • search_protac_e3_issuesno sensitive capability
  • search_safety_failuresno sensitive capability
  • search_target_historyno sensitive capability
  • search_vaccine_immunogenicity_failuresno sensitive capability

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.1 latest A 100/100 0 1.10.0 2026-07-24

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-nullary-ai/badge.svg)](https://mcptrustchecker.com/registry/mcp-nullary-ai)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-nullary-ai"><img src="https://mcptrustchecker.com/registry/mcp-nullary-ai/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-nullary-ai/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://mcp.nullary.ai/mcp --online

Use the free API → How scoring works

More in Other