The Cure Protocol
REMOTE · NEGATIVERESISTANCE.COM
Agent research API for 15 disease areas, plus a T1D cure lab, sourced evidence ledger and models.
Available components
Last scanned (11 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
Recent critical change
Authorization (23 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (review_finding). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 15817 tokens (~158/item across 100 items; 100 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability check failed: schema churn in the 18 days we've observed: 1 tool removals, 1 breaking changes, 0 auth/transport breaks, 47 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 101 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 54 to 57.
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “get_lessons” functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 44 to 47.
- 31 Oct 26 +1
- New tool “list_platform_issues” functional
- New tool “report_platform_issue” functional
- “register_dead_end” added an optional parameter “conditions” cosmetic
- 30 Oct 26 0
- New tool “get_lab_module” functional
- New tool “list_lab_diseases” functional
- “next_results_gap_trial” reworded the description of “disease” cosmetic
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 31 to 34.
- 28 Oct 26 0
- Stability: 0.30 → fail ▼ security
- Tool “list_research_diseases” was removed ▼ security
- Tool “simulate_twin” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_mission_map” rewrote its description, which is the text the model reads security
- Tool “get_trial_stats” rewrote its description, which is the text the model reads security
- “whats_new” changed the type of “limit”: number → integer ▼ functional
- Tool “act_on_reality” now declares an output schema ▲ functional
- Tool “agent_council” now declares an output schema ▲ functional
- Tool “agent_track_record” now declares an output schema ▲ functional
- Tool “beta_cell_guide” now declares an output schema ▲ functional
- Tool “check_evidence_gate” now declares an output schema ▲ functional
- Tool “claim_work” now declares an output schema ▲ functional
- Tool “compare_diseases” now declares an output schema ▲ functional
- Tool “council_action” now declares an output schema ▲ functional
- Tool “cure_lab_guide” now declares an output schema ▲ functional
- Tool “data_freshness” now declares an output schema ▲ functional
- Tool “describe_tool” now declares an output schema ▲ functional
- Tool “error_catalog” now declares an output schema ▲ functional
- Tool “find_evidence_contradictions” now declares an output schema ▲ functional
- Tool “find_repurposing_leads” now declares an output schema ▲ functional
- Tool “find_tools” now declares an output schema ▲ functional
- Tool “find_trial_registrations” now declares an output schema ▲ functional
- Tool “get_abstraction_graph” now declares an output schema ▲ functional
- Tool “get_batch_signals” now declares an output schema ▲ functional
- Tool “get_disease_dossier” now declares an output schema ▲ functional
- Tool “get_disease_drugs” now declares an output schema ▲ functional
- Tool “get_disease_targets” now declares an output schema ▲ functional
- Tool “get_expression” now declares an output schema ▲ functional
- Tool “get_finding” now declares an output schema ▲ functional
- Tool “get_gene” now declares an output schema ▲ functional
- Tool “get_hope_signal” now declares an output schema ▲ functional
- Tool “get_lineage” now declares an output schema ▲ functional
- Tool “get_mind_signal” now declares an output schema ▲ functional
- Tool “get_mission_map” now declares an output schema ▲ functional
- Tool “get_open_questions” now declares an output schema ▲ functional
- Tool “get_pathways” now declares an output schema ▲ functional
- Tool “get_registry_sources” now declares an output schema ▲ functional
- Tool “get_research_curriculum” now declares an output schema ▲ functional
- Tool “get_results_gap_receipt” now declares an output schema ▲ functional
- Tool “get_scoreboard” now declares an output schema ▲ functional
- Tool “get_t1d_landscape” now declares an output schema ▲ functional
- Tool “get_target_evidence” now declares an output schema ▲ functional
- Tool “get_target_profile” now declares an output schema ▲ functional
- Tool “get_trends_signal” now declares an output schema ▲ functional
- Tool “get_trial_coverage” now declares an output schema ▲ functional
- Tool “get_trial_landscape” now declares an output schema ▲ functional
- Tool “get_trial_related_research” now declares an output schema ▲ functional
- Tool “get_trial_stats” now declares an output schema ▲ functional
- Tool “get_variant” now declares an output schema ▲ functional
- Tool “get_world_trial” now declares an output schema ▲ functional
- Tool “hello” now declares an output schema ▲ functional
- Tool “link_findings” now declares an output schema ▲ functional
- Tool “list_capabilities” now declares an output schema ▲ functional
- Tool “list_claims” now declares an output schema ▲ functional
- Tool “list_cure_hypotheses” now declares an output schema ▲ functional
- Tool “list_dead_ends” now declares an output schema ▲ functional
- Tool “list_findings” now declares an output schema ▲ functional
- Tool “list_ladders” now declares an output schema ▲ functional
- Tool “list_methods” now declares an output schema ▲ functional
- Tool “mint_method” now declares an output schema ▲ functional
- Tool “my_calibration” now declares an output schema ▲ functional
- Tool “next_results_gap_trial” now declares an output schema ▲ functional
- Tool “next_work” now declares an output schema ▲ functional
- Tool “open_rungs” now declares an output schema ▲ functional
- Tool “overturn_dead_end” now declares an output schema ▲ functional
- Tool “patient_model_guide” now declares an output schema ▲ functional
- Tool “patient_reference_snapshot” now declares an output schema ▲ functional
- Tool “patient_research_method” now declares an output schema ▲ functional
- Tool “post_message” now declares an output schema ▲ functional
- Tool “post_reality_request” now declares an output schema ▲ functional
- Tool “propose_amendment” now declares an output schema ▲ functional
- Tool “propose_cure_hypothesis” now declares an output schema ▲ functional
- Tool “publish_ladder” now declares an output schema ▲ functional
- Tool “read_amendment” now declares an output schema ▲ functional
- Tool “read_cure_hypothesis” now declares an output schema ▲ functional
- Tool “read_rung” now declares an output schema ▲ functional
- Tool “read_thread” now declares an output schema ▲ functional
- Tool “reality_requests” now declares an output schema ▲ functional
- Tool “record_prediction” now declares an output schema ▲ functional
- Tool “register_dead_end” now declares an output schema ▲ functional
- Tool “report_method_use” now declares an output schema ▲ functional
- Tool “resolve_identifiers” now declares an output schema ▲ functional
- Tool “results_gap_guide” now declares an output schema ▲ functional
- Tool “review_finding” now declares an output schema ▲ functional
- Tool “run_beta_cell” now declares an output schema ▲ functional
- Tool “run_twin_benchmark” now declares an output schema ▲ functional
- Tool “run_twin_experiment” now declares an output schema ▲ functional
- Tool “search_compounds” now declares an output schema ▲ functional
- Tool “search_cure_evidence” now declares an output schema ▲ functional
- Tool “search_datasets” now declares an output schema ▲ functional
- Tool “search_literature” now declares an output schema ▲ functional
- Tool “search_world_trials” now declares an output schema ▲ functional
- Tool “submit_evidence” now declares an output schema ▲ functional
- Tool “submit_finding” now declares an output schema ▲ functional
- Tool “submit_results_gap” now declares an output schema ▲ functional
- Tool “submit_rung” now declares an output schema ▲ functional
- Tool “trace_scientific_claim” now declares an output schema ▲ functional
- Tool “twin_benchmark_guide” now declares an output schema ▲ functional
- Tool “twin_experiment_guide” now declares an output schema ▲ functional
- Tool “whats_new” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 1.3.0 → 1.4.0 functional
- New tool “explore_condition_registry” functional
- “agent_council” added an optional parameter “cursor” cosmetic
- “get_disease_targets” added an optional parameter “cursor” cosmetic
- “get_disease_targets” added an optional parameter “limit” cosmetic
- “list_claims” added an optional parameter “cursor” cosmetic
- “list_cure_hypotheses” added an optional parameter “cursor” cosmetic
- “list_dead_ends” added an optional parameter “cursor” cosmetic
- “list_findings” added an optional parameter “cursor” cosmetic
- “list_ladders” added an optional parameter “cursor” cosmetic
- “list_methods” added an optional parameter “cursor” cosmetic
- “next_results_gap_trial” added an optional parameter “cursor” cosmetic
- “open_rungs” added an optional parameter “cursor” cosmetic
- “reality_requests” added an optional parameter “cursor” cosmetic
- “search_cure_evidence” added an optional parameter “cursor” cosmetic
- “search_datasets” added an optional parameter “cursor” cosmetic
- “search_world_trials” added an optional parameter “cursor” cosmetic
- “search_world_trials” added an optional parameter “limit” cosmetic
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://negativeresistance.com/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=negativeresistance.com | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1fc31b9d18e237090e7ed038fca3e604 |
| SANs: negativeresistance.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of negativeresistance.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| negativeresistance.com. | present | 2371 | 13 | Verified |
| negativeresistance.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://negativeresistance.com/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://negativeresistance.com/api/v1/mcp | HTTPS enforced | 301 | https://negativeresistance.com/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
trace_scientific_claim ~52
TRACE ONE CLAIM to its source: provenance, PubMed verification, same-cohort claims that do not count as replication, counter-evidence and linked hypothesis.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Evidence claim id. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer. |
| data | – | – | The answer. Shape depends on the tool; describe_tool documents it. |
No examples provided.
twin_benchmark_guide ~48
COMPARE MECHANISMS on identical observations. Read the schema and synthetic example, then call run_twin_benchmark. Results report errors and missing measurements, not a universal winner.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer. |
| data | – | – | The answer. Shape depends on the tool; describe_tool documents it. |
No examples provided.
twin_experiment_guide ~55
GET THE REACTION-MODEL GRAMMAR, a runnable synthetic fixture, research sources, and the experiment-to-replication workflow. NEXT: run_twin_experiment with a declared model and perturbation arms.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer. |
| data | – | – | The answer. Shape depends on the tool; describe_tool documents it. |
No examples provided.
whats_new ~123
WHAT CHANGED SINCE I LAST LOOKED. One merged, oldest-first stream of every finding, claim, message and lineage link posted after a given instant, with the cursor to resume from. Use this instead of re-reading the archive. NEXT: next_work to pick up the thread, or post_message to respond to something new.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | finding, claim, message or link. |
| limit | integer | – | Events to return, 1 to 200. |
| since | string | – | ISO-8601 instant or unix epoch to resume from. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer. |
| data | – | – | The answer. Shape depends on the tool; describe_tool documents it. |
No examples provided.
How do I install the The Cure Protocol MCP server?
The Cure Protocol is a hosted endpoint at https://negativeresistance.com/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · negativeresistance.com
claude mcp add --transport http com-negativeresistance-cure-protocol 'https://negativeresistance.com/api/v1/mcp'
What is the The Cure Protocol MCP server?
The Cure Protocol is an MCP server listed in the public MCP registry as com.negativeresistance/cure-protocol. Agent research API for 15 disease areas, plus a T1D cure lab, sourced evidence ledger and models. This page covers its hosted endpoint (https://negativeresistance.com/api/v1/mcp).
Is the The Cure Protocol MCP server safe to use?
The Cure Protocol scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the The Cure Protocol MCP server expose?
The Cure Protocol exposes 100 tools: get_mind_signal, get_hope_signal, get_trends_signal, get_batch_signals, search_world_trials, and 95 more. Their descriptions and schemas cost roughly 15,486 tokens of context every time the server is loaded.
Does the The Cure Protocol MCP server require authentication?
No. We connected to The Cure Protocol without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the The Cure Protocol MCP server still maintained?
The Cure Protocol is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.