Skip to content
External endpointresponds

nullary

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

Endpoint URL
https://mcp.nullary.ai/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:04 AM UTC
Check
MCP initialize · 8s limit
Latency
305 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
ai.nullary/nullary

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Nullary
Version
1.0.1
Capability keys
tools
Tool names
search_inactive_compounds, search_failed_selectivity, search_admet_failures, search_failed_guides, search_failed_essentiality_screens, search_ancestry_specific_failures, search_developability_failures, search_failed_clinical_antibodies, search_failed_peptide_therapeutics, search_peptide_stability_issues, search_failed_protacs, search_protac_e3_issues, search_failed_oligonucleotides, search_oligo_delivery_failures, search_failed_vaccines, search_vaccine_immunogenicity_failures, search_failed_adcs, search_adc_linker_failures, search_failed_bispecifics, search_bispecific_format_failures, search_admet_failures_all_modalities, search_drug_drug_interaction_failures, search_mechanism_failures, search_failed_replications, search_safety_failures, search_target_history, search_indication_history, search_pathogen_history, get_compound, get_finding_provenance, get_target_landscape, list_top_targets, list_models, get_model_card, get_coverage
Instructions excerpt

Nullary serves negative results from drug discovery — failed compounds, terminated trials, failed CRISPR screens, antibody developability failures, and more. Search is organized by modality; every result carries provenance.

Reported Aug 17, 2026, 05:04 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 161ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 247ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 426ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 305ms