negative-results-mcp
Nullary MCP Server
Negative results intelligence for drug discovery — over the Model Context Protocol.
Nullary is a hosted MCP server that lets AI agents query measured negative results from drug discovery: inactive compounds, failed selectivity panels, terminated clinical trials, failed CRISPR screens, antibody developability failures, and more — each result carrying full provenance (source database, DOI/PMID, license).
This repository documents the public MCP interface. The server is hosted; the data pipeline and application code are maintained separately.
Connect
Nullary is a remote MCP server (streamable-HTTP) — nothing to install, no API key:
https://mcp.nullary.ai/mcpClaude Code / generic MCP client
{
"mcpServers": {
"nullary": {
"url": "https://mcp.nullary.ai/mcp"
}
}
}Cursor
Settings → MCP → Add new MCP server → paste the URL above (transport: streamable-HTTP).
Claude Desktop
Settings → Connectors → Add custom connector → URL https://mcp.nullary.ai/mcp.
What you can ask
"What's failed against EGFR?" — failed compounds, trials, and screens for a target, across modalities
"Which kinase inhibitors were inactive in ChEMBL?"
"Show terminated Phase 2 oncology trials and why they stopped"
"Failed CRISPR knockouts for TP53"
Tools are organized by modality (small molecule, CRISPR, antibody, peptide, PROTAC, clinical trial, …); every response cites its source.
Tools
The server exposes 35 tools — served live via the MCP tools/list method. Full JSON
Schemas (inputs per tool) are in tools.json. Tools span the seven
modalities plus cross-modality history, compound/provenance lookups, and the Layer-1
model registry.
Tool | Description |
| Inactive small-molecule compound-target pairs. |
| Small molecules that failed selectivity. |
| Small-molecule ADMET failures. |
| Failed/ineffective CRISPR guides. |
| Non-dependency / failed essentiality screens. |
| Ancestry-specific CRISPR failures. |
| Antibody developability failures. |
| Discontinued/terminated clinical antibodies. |
| Failed peptide therapeutics. |
| Peptide stability/half-life failures. |
| PROTACs that failed degradation/ternary/permeability. |
| PROTAC E3-ligase recruitment / ternary failures. |
| ASOs/siRNAs that failed engagement/developability. |
| Oligonucleotide delivery failures. |
| Failed/terminated vaccines (by pathogen/indication). |
| Failed vaccine immunogen designs. |
| ADCs that failed at any stage. |
| ADC failures attributed to linker chemistry. |
| Bispecifics that failed at any stage. |
| Bispecific format/engineering failures. |
| ADMET failures across ALL modalities. |
| Drug-drug interaction failures. |
| Approaches that failed for a mechanism (by target). |
| Findings that failed to replicate. |
| Clinical/preclinical safety failures across modalities. |
| ALL failed approaches against a target across every modality. |
| ALL failed approaches for an indication across every modality. |
| Vaccine + antimicrobial + antibody failures for a pathogen. |
| A compound + its full negative profile across modalities/sources. |
| Full provenance + detail for a single finding by id. |
| Target "graveyard" / exhaustion index — how picked-over a target is, by modality and outcome. |
| The most heavily-pursued targets, ranked by recorded negative findings. |
| Summary of the Layer-1 inactivity-scoring model registry. |
| Per-target Layer-1 model card: training counts + held-out scaffold-split metrics. |
| Per-modality and per-source coverage stats. |
Links
Website: https://nullary.ai
Docs: https://nullary.ai/docs
Coverage: https://nullary.ai/coverage
Research: https://nullary.ai/research
MCP Registry: listed as
ai.nullary/nullary
License
This documentation repository is MIT-licensed. The underlying data is provided under each source's respective license — see the coverage page.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nullary-ai/nullary-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server