Skip to content

autosearch MCP server

uk.exatoshi/autosearchexatoshi.ukstreamable-httpv1.0.0Scanned

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

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the autosearch MCP server can do

The autosearch MCP server is published by exatoshi.uk, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: autosearch_run_research and autosearch_verify_doi), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • autosearch_run_researchLaunch an AI scientific research run.No findings

    Why it is in this group

    • The name "autosearch_run_research" says "run": a word for a change.
    Description, as the server wrote it
    Launch an AI scientific research run. Returns run_id immediately. Use get_run_status to poll.
  • autosearch_verify_doiVerify a DOI via Crossref.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a DOI via Crossref. Returns validity, title, authors, year, journal.
Only reads 4Show 4 read-only tools
  • autosearch_get_run_paperGet the generated paper for a completed run.No findings

    Why it is in this group

    • The name "autosearch_get_run_paper" says "get": a word for reading.
    Description, as the server wrote it
    Get the generated paper for a completed run. Returns markdown, JSON metadata, or PDF download URL.
  • autosearch_get_run_statusGet the current status of a research run.No findings

    Why it is in this group

    • The name "autosearch_get_run_status" says "get": a word for reading.
    Description, as the server wrote it
    Get the current status of a research run. Returns status, frontier_score, n_experiments, summary.
  • autosearch_list_my_runsList the authenticated user latest research runs with status and frontier score.No findings

    Why it is in this group

    • The name "autosearch_list_my_runs" says "list": a word for reading.
    Description, as the server wrote it
    List the authenticated user latest research runs with status and frontier score.
  • autosearch_search_evidenceSearch peer-reviewed evidence across academic sources without launching a full research run.No findings

    Why it is in this group

    • The name "autosearch_search_evidence" says "search": a word for reading.
    Description, as the server wrote it
    Search peer-reviewed evidence across academic sources without launching a full research run. Returns top N papers with metadata.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:20 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
526
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 526.

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 526
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2024-11-05 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 526; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 526
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2024-11-05 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http autosearch https://exatoshi.uk/mcp --header 'x-api-key: <your-x-api-key>'
claude mcp add --transport http autosearch https://exatoshi.uk/mcp --header 'x-api-key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__autosearch__autosearch_get_run_status",
      "mcp__autosearch__autosearch_get_run_paper",
      "mcp__autosearch__autosearch_search_evidence",
      "mcp__autosearch__autosearch_list_my_runs"
    ],
    "ask": [
      "mcp__autosearch__autosearch_run_research",
      "mcp__autosearch__autosearch_verify_doi"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as autosearch. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/uk.exatoshi/autosearch/verify?hash=78291dba9d210d70e86e638bf161c4768143ff2bd1e57aee5f7a41c17c8ebf55" | jq -e '.changed == false'

Pinned hash 78291dba9d21, from Oct 21, 2026, 19:21 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/uk.exatoshi/autosearch/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for uk.exatoshi/autosearch
[![Anlyon Radar](https://radar.anlyon.com/badge/uk.exatoshi/autosearch.svg)](https://radar.anlyon.com/servers/uk.exatoshi/autosearch)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

autosearch MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the autosearch MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the autosearch MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the autosearch MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the autosearch MCP server have?

6 tools: 2 write, 4 read. autosearch_run_research, autosearch_verify_doi, autosearch_get_run_status, autosearch_get_run_paper, autosearch_search_evidence and autosearch_list_my_runs.

Does the autosearch MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the autosearch MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the autosearch MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.