Autosearch MCP Server

by exatoshi Your server? Claim it

not responding

Autosearch is listed as active in the registry but did not answer our last check. It exposes 6 tools.

PRISMA 2020 systematic reviews as MCP tools - verified citations, IMRAD papers

Uptime history 91 days of history · worst day 0%

91 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

299 ms

Response time

average over 24h

open, no key

Access

streamable-http

Autosearch does not always answer

Over the last week it answered 15.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add autosearch --transport http https://exatoshi.uk/mcp

Settings → Connectors → Add custom connector, then paste this address

https://exatoshi.uk/mcp

~/.codex/config.toml

[mcp_servers.autosearch]
url = "https://exatoshi.uk/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "autosearch": {
      "url": "https://exatoshi.uk/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "autosearch": {
      "type": "http",
      "url": "https://exatoshi.uk/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

autosearch

autosearch_get_run_paper

Get the generated paper for a completed run. Returns markdown, JSON metadata, or PDF download URL.

autosearch_get_run_status

Get the current status of a research run. Returns status, frontier_score, n_experiments, summary.

autosearch_list_my_runs

List the authenticated user latest research runs with status and frontier score.

autosearch_run_research

Launch an AI scientific research run. Returns run_id immediately. Use get_run_status to poll.

autosearch_search_evidence

Search peer-reviewed evidence across academic sources without launching a full research run. Returns top N papers with metadata.

autosearch_verify_doi

Verify a DOI via Crossref. Returns validity, title, authors, year, journal.

Endpoints

URL	Transport	State	Latency	Checked
https://exatoshi.uk/mcp	streamable-http	answering	299 ms	14 min ago

Alternatives to Autosearch

same job, measured the same way

prismAId MCP

by open-and-sustainable

MCP server for prismAId AI-assisted systematic reviews and protocol conformance checking.

local only

Semantic Scholar MCP Server

by smaniches

MCP server for the Semantic Scholar API: search 200M+ papers, citations, authors, recommendations.

2 529 installs/wk local only

Crystal

by erahq

Self-curating memory your AI tools share: provenance, verified citations, and trust tiers.

answering

revisia

by revisia

Systematic reviews from chat: PRISMA 2020 diagrams, risk-of-bias figures, kappa and AI screening.

26 tools answering

Psilocybin Research MCP — Papers, Trials and Research Data

by psilocybin-research

Read-only psilocybin literature, trial facts, citations and verified bibliographic datasets.

9 tools answering

Vivory Verification Gateway

by jayjodev

98 MCP tools for verifiable AI: citations, law, KYB, peer review, forecast, media provenance.

165 installs/wk local only

WireTensors

by wiretensors

Neutral, verified AI tool reviews — search, compare and get recommendations across 260+ tools.

6 tools answering

Bounded Tools MCP

by bounded-systems

Read-only MCP server over bounded.tools's Sigstore-verified static API (stdio).

34 installs/wk local only

Autosearch — questions

Answers built from our own checks of this server.

What can Autosearch do?

It exposes 6 tools, read directly from the server on our last check. Among them: autosearch_get_run_paper, autosearch_get_run_status, autosearch_list_my_runs, autosearch_run_research, autosearch_search_evidence, autosearch_verify_doi. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Autosearch working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 299 ms. The bar chart above shows every period we have measured.

The registry lists Autosearch as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Autosearch?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Autosearch need an API key?

No. Autosearch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.