# Frontier: evidence-scored science breakthroughs (remote · frontierresearch.co)

New papers from Nature, Science, Cell, NEJM and other top journals, scored on evidence and novelty.

- Trust score: 88/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `frontierresearch.co`: 88/100 (this document), [markdown](https://verifymcp.io/servers/co-frontierresearch-frontier/api-mcp.md), [page](https://verifymcp.io/servers/co-frontierresearch-frontier/api-mcp)

## Channel facts

- Endpoint: `https://frontierresearch.co/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http co-frontierresearch-frontier 'https://frontierresearch.co/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-frontierresearch-frontier": {
      "url": "https://frontierresearch.co/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-frontierresearch-frontier": {
      "type": "http",
      "url": "https://frontierresearch.co/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-frontierresearch-frontier]
url = "https://frontierresearch.co/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-frontierresearch-frontier": {
      "type": "remote",
      "url": "https://frontierresearch.co/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-frontierresearch-frontier --url 'https://frontierresearch.co/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-frontierresearch-frontier:
    url: "https://frontierresearch.co/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-frontierresearch-frontier": {
      "Transport": "http",
      "Url": "https://frontierresearch.co/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-frontierresearch-frontier -t streamable-http -u 'https://frontierresearch.co/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-frontierresearch-frontier": {
      "type": "http",
      "url": "https://frontierresearch.co/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 88, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 88, +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.

### 2026-11-03 (score 87, +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.

### 2026-11-01 (score 86, +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.

### 2026-10-30 (score 85, +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.

### 2026-10-28 (score 84, +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.

### 2026-10-26 (score 83, +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.

### 2026-10-24 (score 82, +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.

## MCP tools (5)

### `search_breakthroughs` (~164 tokens)

Search scored breakthroughs

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.

Input parameters:

- `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.

### `latest_breakthroughs` (~99 tokens)

Latest scored breakthroughs

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.

Input parameters:

- `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).

### `get_breakthrough` (~107 tokens)

One entry in full

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.

Input parameters:

- `id` (string, required): OpenAlex work id, entry slug, or Frontier entry URL.

### `list_fields` (~26 tokens)

Fields in the index

The research fields Frontier covers, with how many entries each holds and its median Frontier Score.

### `explain_frontier_score` (~34 tokens)

How the Frontier Score works

The Frontier Score method: its three pillars and what each measures, recency, the integrity rule, tiers and confidence.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-frontierresearch-frontier/api-mcp#diagnostics

## Score history

- 2026-11-06: 88
- 2026-11-05: 88
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 86
- 2026-11-01: 86
- 2026-10-31: 85
- 2026-10-30: 85
- 2026-10-29: 84
- 2026-10-28: 84
- 2026-10-27: 83
- 2026-10-26: 83
- 2026-10-25: 82
- 2026-10-24: 82
- 2026-10-23: 81
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 80
- 2026-10-19: 80
- 2026-10-18: 79
- 2026-10-17: 79
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 77
- 2026-10-13: 77
- 2026-10-12: 76
- 2026-10-11: 76
- 2026-10-10: 75
- 2026-10-07: 74

## Common questions

### 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 6 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.

## Links

- Remote endpoint: https://frontierresearch.co/api/mcp
- Website: https://frontierresearch.co/
- Changelog RSS feed: https://verifymcp.io/servers/co-frontierresearch-frontier/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-frontierresearch-frontier/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-frontierresearch-frontier/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-frontierresearch-frontier/api-mcp