uk.exatoshi/autosearch
REMOTE · EXATOSHI.UK · SCANNED SEP 21
PRISMA 2020 systematic reviews as MCP tools - verified citations, IMRAD papers
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 273 tokens (~45/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the uk.exatoshi/autosearch MCP server?
uk.exatoshi/autosearch is a hosted endpoint at https://exatoshi.uk/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 · exatoshi.uk
claude mcp add --transport http uk-exatoshi-autosearch 'https://exatoshi.uk/mcp'
{
"mcpServers": {
"uk-exatoshi-autosearch": {
"url": "https://exatoshi.uk/mcp"
}
}
} {
"servers": {
"uk-exatoshi-autosearch": {
"type": "http",
"url": "https://exatoshi.uk/mcp"
}
}
} [mcp_servers.uk-exatoshi-autosearch] url = "https://exatoshi.uk/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"uk-exatoshi-autosearch": {
"type": "remote",
"url": "https://exatoshi.uk/mcp",
"enabled": true
}
}
} openclaw mcp add uk-exatoshi-autosearch --url 'https://exatoshi.uk/mcp' --transport streamable-http
mcp_servers:
uk-exatoshi-autosearch:
url: "https://exatoshi.uk/mcp" {
"McpServers": {
"uk-exatoshi-autosearch": {
"Transport": "http",
"Url": "https://exatoshi.uk/mcp"
}
}
} assistant mcp add uk-exatoshi-autosearch -t streamable-http -u 'https://exatoshi.uk/mcp'
{
"mcpServers": {
"uk-exatoshi-autosearch": {
"type": "http",
"url": "https://exatoshi.uk/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 21 Sept 2026 · Probed https://exatoshi.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=exatoshi.uk | CN=YR1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | RSA 2048 | SHA256-RSA | 6eb36fb14ef39f1a77fb8a75546a7da26da |
| SANs: exatoshi.uk, www.exatoshi.uk | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of exatoshi.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | present | 43876 | 8 | Verified |
| exatoshi.uk. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: https://accounts.google.com https://js.stripe.com https://esm.sh https://cdn.jsdelivr.net https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https:; media-src 'self' blob: https://*.elevenlabs.io wss://*.elevenlabs.io; connect-src 'self' https://accounts.google.com https://api.elevenlabs.io https://*.elevenlabs.io wss://*.elevenlabs.io https://esm.sh https://www.googletagmanager.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com; frame-src https://checkout.stripe.com https://accounts.google.com; form-action 'self' https://exatoshi.uk https://accounts.google.com; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), autoplay=(self) |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://exatoshi.uk/mcp | Verified | 200 | |
| http (plaintext) | http://exatoshi.uk/mcp | HTTPS enforced | 301 | https://exatoshi.uk/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 →
autosearch_get_run_paper ~48
Get the generated paper for a completed run. Returns markdown, JSON metadata, or PDF download URL.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| run_id | string | yes | – |
No output schema declared.
No examples provided.
autosearch_get_run_status ~42
Get the current status of a research run. Returns status, frontier_score, n_experiments, summary.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | – |
No output schema declared.
No examples provided.
autosearch_list_my_runs ~32
List the authenticated user latest research runs with status and frontier score.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
autosearch_run_research ~49
Launch an AI scientific research run. Returns run_id immediately. Use get_run_status to poll.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | – |
| prompt | string | yes | Research question or topic |
No output schema declared.
No examples provided.
autosearch_search_evidence ~54
Search peer-reviewed evidence across academic sources without launching a full research run. Returns top N papers with metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| sources | array | – | – |
No output schema declared.
No examples provided.
autosearch_verify_doi ~48
Verify a DOI via Crossref. Returns validity, title, authors, year, journal.
| Name | Type | Req | Description |
|---|---|---|---|
| doi | string | yes | DOI string with or without https://doi.org/ prefix |
No output schema declared.
No examples provided.
What is the uk.exatoshi/autosearch MCP server?
uk.exatoshi/autosearch is an MCP server listed in the public MCP registry as uk.exatoshi/autosearch. PRISMA 2020 systematic reviews as MCP tools - verified citations, IMRAD papers. This page covers its hosted endpoint (https://exatoshi.uk/mcp).
Is the uk.exatoshi/autosearch MCP server safe to use?
uk.exatoshi/autosearch scores 85 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 uk.exatoshi/autosearch MCP server expose?
uk.exatoshi/autosearch exposes 6 tools: autosearch_run_research, autosearch_get_run_status, autosearch_get_run_paper, autosearch_verify_doi, autosearch_search_evidence, autosearch_list_my_runs. Their descriptions and schemas cost roughly 273 tokens of context every time the server is loaded.
Does the uk.exatoshi/autosearch MCP server require authentication?
Yes. uk.exatoshi/autosearch asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the uk.exatoshi/autosearch MCP server still maintained?
uk.exatoshi/autosearch is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.