Frontier: evidence-scored science breakthroughs
REMOTE · FRONTIERRESEARCH.CO
New papers from Nature, Science, Cell, NEJM and other top journals, scored on evidence and novelty.
Available components
Last scanned (23 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 624 tokens (~124/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://frontierresearch.co/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=frontierresearch.co | CN=YR2,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 57362bd8ee43110636e9e0bc2405df51b15 |
| SANs: frontierresearch.co | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 frontierresearch.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| frontierresearch.co. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://platform.twitter.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com; worker-src 'self' blob:; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com; frame-ancestors 'self' http://localhost:* https://o-mega.ai https://*.o-mega.ai https://founden.ai https://*.founden.ai https://*.founden.co https://*.e2b.app https://*.vercel.app; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://frontierresearch.co/api/mcp | Verified | 200 | |
| http (plaintext) | http://frontierresearch.co/api/mcp | HTTPS enforced | 308 | https://frontierresearch.co/api/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 →
explain_frontier_score How the Frontier Score works ~34
The Frontier Score method: its three pillars and what each measures, recency, the integrity rule, tiers and confidence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_breakthrough One entry in full ~107
Everything Frontier holds on one entry: the plain-language summary, why it matters and what to watch, authors and institutions, the full Frontier Score breakdown (each pillar and what drives it, recency and confidence) and the sources behind each figure. Accepts an OpenAlex work id (e.g. W7214802080), an entry slug, or a frontierresearch.co entry URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | OpenAlex work id, entry slug, or Frontier entry URL. |
No output schema declared.
No examples provided.
latest_breakthroughs Latest scored breakthroughs ~99
What Frontier added most recently: the entries listed in the last N days (the index adds a few new papers from the top journals every day), newest first, optionally within one field.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How far back to look, in days (1 to 60). |
| field | string | – | Limit to one field (see list_fields). |
| limit | integer | – | How many entries to return (1 to 20). |
No output schema declared.
No examples provided.
list_fields Fields in the index ~26
The research fields Frontier covers, with how many entries each holds and its median Frontier Score.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_breakthroughs Search scored breakthroughs ~164
Search Frontier's evidence-scored index of new research from the top scientific journals. Matches the query against titles, plain-language summaries, authors and topics, optionally within one field, and returns the matching entries ranked by Frontier Score (or newest paper first), each with its summary, score, Frontier URL and DOI. Leave the query empty to browse a field.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | Limit to one field (see list_fields). |
| limit | integer | – | How many entries to return (1 to 20). |
| query | string | – | Free text, e.g. 'CRISPR', 'obesity drug', 'quantum error correction'. |
| sort | string | – | 'score' ranks by Frontier Score; 'newest' by paper publication date. |
No output schema declared.
No examples provided.
How do I install the Frontier: evidence-scored science breakthroughs MCP server?
Frontier: evidence-scored science breakthroughs is a hosted endpoint at https://frontierresearch.co/api/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 · frontierresearch.co
claude mcp add --transport http co-frontierresearch-frontier 'https://frontierresearch.co/api/mcp'
What is the Frontier: evidence-scored science breakthroughs MCP server?
Frontier: evidence-scored science breakthroughs is an MCP server listed in the public MCP registry as co.frontierresearch/frontier. New papers from Nature, Science, Cell, NEJM and other top journals, scored on evidence and novelty. This page covers its hosted endpoint (https://frontierresearch.co/api/mcp).
Is the Frontier: evidence-scored science breakthroughs MCP server safe to use?
Frontier: evidence-scored science breakthroughs scores 88 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 Frontier: evidence-scored science breakthroughs MCP server expose?
Frontier: evidence-scored science breakthroughs exposes 5 tools: search_breakthroughs, latest_breakthroughs, get_breakthrough, list_fields, explain_frontier_score. Their descriptions and schemas cost roughly 430 tokens of context every time the server is loaded.
Does the Frontier: evidence-scored science breakthroughs MCP server require authentication?
No. We connected to Frontier: evidence-scored science breakthroughs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Frontier: evidence-scored science breakthroughs MCP server still maintained?
Frontier: evidence-scored science breakthroughs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Frontier: evidence-scored science breakthroughs MCP server?
VerifyMCP ran 13 checks on Frontier: evidence-scored science breakthroughs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.