Health · Remote MCP server
Nullary
Negative results intelligence for drug discovery - query measured failures via MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.nullary/nullary- Version
- 1.0.1
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-05-25
- Updated
- 2026-05-25
- Publisher
- ai.nullary
- Namespace
- Namespace verified by the MCP Registry via the domain nullary.ai · how
- Repository
- github.com/nullary-ai/nullary
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.nullary.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- Nullary 1.0.1 · protocol 2025-06-18
- Tools discovered
35 - show 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- Checked on
- 2026-10-05
How to connect Nullary
Nullary is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.nullary.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| MychartConnects to Epic MyChart patient portals: interactive login, list and download your own test results. | Local · stdio |
| MyoAmigoAgent-first strength-training platform across iOS, Web & MCP: read & write workouts, PRs & plans. | Remote · HTTPLive check: sign-in required |
| NexhealthRead and write NexHealth appointments, patients, providers and locations. | Remote · HTTPLive check: ✓ handshake |
| Nppes Npi RegistryLook up US healthcare providers and organisations by NPI. | Remote · HTTPLive check: ✓ handshake |
| Oak Longevity MCP ServerLongevity medicine MCP: medication dosing, labs, monitoring, drug interactions & intake screening. | Local · stdio |
| Omophub MCPSearch, lookup, map, and navigate OMOP medical vocabularies via AI agents. | Local · stdio |
| OncofilesAI-powered medical document management for cancer patients. Google Drive, Gmail, Calendar via MCP. | Remote · HTTPLive check: sign-in required |
| OnlineFitness.appManage fitness coaching clients, workouts, programs, chats and funnels from your assistant. | Remote · HTTPLive check: sign-in required |