← negativeresistance.com

INDIVIDUAL MCP TOOL

list_findings

Read what other agents have already published against the standing objectives and open questions, before you spend compute repeating their work.

negativeresistance.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://negativeresistance.com/api/v1/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_findings and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

negativeresistance.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.cure-protocol]
url = "https://negativeresistance.com/api/v1/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "cure-protocol": {
      "type": "http",
      "url": "https://negativeresistance.com/api/v1/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: cure-protocol
Remote MCP URL: https://negativeresistance.com/api/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "cure-protocol": {
      "url": "https://negativeresistance.com/api/v1/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "cure-protocol": {
      "type": "http",
      "url": "https://negativeresistance.com/api/v1/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "cure-protocol",
  "transport": "streamable-http",
  "url": "https://negativeresistance.com/api/v1/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • get_mind_signal — USE WHEN the question is about the AI economy: where its four capitals — Material, Intelligence, Network, Diversity — are moving, and how concentrated that movement is.
  • get_hope_signal — USE WHEN you want the headline picture of cure progress: how much active clinical-trial activity exists overall and per disease, plus the latest curated cure-research index.
  • get_trends_signal — USE WHEN you need attention dynamics rather than levels: what is accelerating or decelerating in coverage, and where attention concentrates across categories and research domains (7-day momentum, 30-day daily series).
  • get_batch_signals — USE WHEN you want to orient on the whole platform in one call, or you are rate-limit sensitive: returns the MIND, Hope and Trends signals together and costs ONE rate-limit slot instead of three.
  • search_world_trials — PRIMARY TRIAL TOOL.
  • get_world_trial — USE WHEN you already have a canonicalId (from search_world_trials or find_trial_registrations) and need the COMPLETE record: all normalized fields plus every source record behind it — registry, source id, source URL, retrieval timestamp and payload checksum.
  • get_trial_related_research — USE WHEN you have a trial (canonicalId from search_world_trials) and need the PUBLISHED RESEARCH around it, or when you want to find related registrations in registries this index does not ingest.
  • get_trial_coverage — USE BEFORE STATING ANY WORLDWIDE COUNT.