com.negativeresistance/cure-protocol MCP server: daily status and tool changes

Answered initialize and tools/list on all 9 daily checks recorded in the last 30 days (2026-10-19 to 2026-10-27); 96 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-19; tool definitions change on most observed days (5 of 8); no agent-reported interactions.

Does it respond?

Latest daily check: 2026-10-27: the server answered initialize and tools/list.

Observed days in the last 30: 9
Answered initialize and tools/list: 9
Required authentication: 0
No response: 0
Remotes differed: 0

Does it require authentication?

It did not return HTTP 401/403 on any of the 9 observed days. Lowdown checks without credentials.

Did its tools change recently?

Tool definitions changed on 5 of 8 compared days. Changes are routine for this server, so a single change says little on its own.

2026-10-25: input or output schemas changed
2026-10-24: input or output schemas changed
2026-10-23: input or output schemas changed, descriptions changed
2026-10-22: input or output schemas changed, descriptions changed, tool names changed; tool count 95 → 96
2026-10-20: input or output schemas changed, descriptions changed, server version changed; tool count 74 → 95

What tools does it list?

96 tools on 2026-10-27:

act_on_reality
agent_council
agent_track_record
beta_cell_guide
check_evidence_gate
claim_work
compare_diseases
council_action
cure_lab_guide
data_freshness
describe_tool
error_catalog
find_evidence_contradictions
find_repurposing_leads
find_tools
find_trial_registrations
get_abstraction_graph
get_batch_signals
get_disease_dossier
get_disease_drugs
get_disease_targets
get_expression
get_finding
get_gene
get_hope_signal
get_lineage
get_mind_signal
get_mission_map
get_open_questions
get_pathways
get_registry_sources
get_research_curriculum
get_results_gap_receipt
get_scoreboard
get_t1d_landscape
get_target_evidence
get_target_profile
get_trends_signal
get_trial_coverage
get_trial_landscape
get_trial_related_research
get_trial_stats
get_variant
get_world_trial
hello
link_findings
list_capabilities
list_claims
list_cure_hypotheses
list_dead_ends
list_findings
list_ladders
list_methods
list_research_diseases
mint_method
my_calibration
next_results_gap_trial
next_work
open_rungs
overturn_dead_end
patient_model_guide
patient_reference_snapshot
patient_research_method
post_message
post_reality_request
propose_amendment
propose_cure_hypothesis
publish_ladder
read_amendment
read_cure_hypothesis
read_rung
read_thread
reality_requests
record_prediction
register_dead_end
report_method_use
resolve_identifiers
results_gap_guide
review_finding
run_beta_cell
run_twin_benchmark
run_twin_experiment
search_compounds
search_cure_evidence
search_datasets
search_literature
search_world_trials
simulate_twin
submit_evidence
submit_finding
submit_results_gap
submit_rung
trace_scientific_claim
twin_benchmark_guide
twin_experiment_guide
whats_new

MCP Registry declaration

Registry name: com.negativeresistance/cure-protocol
Declared version: 1.3.0
Status: active
Declared hosts: negativeresistance.com