# FrontMCP docs (remote · mcp.frontmcp.dev)

FrontMCP's docs for coding agents: search, pages, APIs, examples and upgrades, by FrontMCP release.

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

## Components

- remote · `mcp.frontmcp.dev`: 85/100 (this document), [markdown](https://verifymcp.io/servers/dev-frontmcp-mcp-frontmcp/mcp.md), [page](https://verifymcp.io/servers/dev-frontmcp-mcp-frontmcp/mcp)

## Channel facts

- Endpoint: `https://mcp.frontmcp.dev/`
- 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-05.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1851 tokens (~205/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 FrontMCP docs MCP server?

FrontMCP docs is a hosted endpoint at https://mcp.frontmcp.dev/, 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 dev-frontmcp-mcp-frontmcp 'https://mcp.frontmcp.dev/'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-frontmcp-mcp-frontmcp": {
      "url": "https://mcp.frontmcp.dev/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-frontmcp-mcp-frontmcp": {
      "type": "http",
      "url": "https://mcp.frontmcp.dev/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-frontmcp-mcp-frontmcp]
url = "https://mcp.frontmcp.dev/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-frontmcp-mcp-frontmcp": {
      "type": "remote",
      "url": "https://mcp.frontmcp.dev/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-frontmcp-mcp-frontmcp --url 'https://mcp.frontmcp.dev/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-frontmcp-mcp-frontmcp:
    url: "https://mcp.frontmcp.dev/"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-frontmcp-mcp-frontmcp": {
      "Transport": "http",
      "Url": "https://mcp.frontmcp.dev/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-frontmcp-mcp-frontmcp -t streamable-http -u 'https://mcp.frontmcp.dev/'
```

### Other

```json
{
  "mcpServers": {
    "dev-frontmcp-mcp-frontmcp": {
      "type": "http",
      "url": "https://mcp.frontmcp.dev/"
    }
  }
}
```

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-05 (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-11-02 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 81, +1)

- [functional] New prompt “migrate_from_fastmcp”
- [functional] New prompt “migrate_from_typescript_sdk”

### 2026-10-25 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 79, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “resolve_version” rewrote its description, which is the text the model reads
- [cosmetic] “resolve_version” added an optional parameter “installedVersion”
- [cosmetic] “resolve_version” added an optional parameter “workspace”
- [cosmetic] “resolve_version” reworded the description of “lockfile”
- [cosmetic] “search_docs” reworded the description of “section”

### 2026-10-22 (score 78, +2)

- [security improvement] HSTS header: fail → pass

## MCP tools (9)

### `get_example` (~158 tokens)

Get a page's example

Returns a runnable example from a FrontMCP docs page: the files of one of its Playgrounds, with their tests, as the docs run them. Without `index`, lists the page's Playgrounds (numbered from 1, in page order) with their section and files.

Input parameters:

- `index` (integer): Which Playground on the page, from 1.
- `path` (string, required): The page, like /reference/sdk/tool or a frontmcp.dev URL.
- `version` (string): A documented FrontMCP version, like "1.9.4", or a minor, like "1.9", for its newest patch. Pass the version resolve_version found for the project. Defaults to the version this endpoint serves.

### `get_page` (~245 tokens)

Read a docs page

Returns a FrontMCP docs page as Markdown, or one section of it. `path` is a path (/reference/sdk/tool), a frontmcp.dev URL, or an old docs.agentfront.dev URL, which is mapped to its page here; a #anchor in it, or `section`, picks the section. A very long page comes back as its introduction and its sections, to read one at a time. Use it once search_docs, lookup_api or list_pages has given a path, or for a docs URL you already have. The page is the one documented for `version`.

Input parameters:

- `path` (string, required): The page: /reference/sdk/tool, https://frontmcp.dev/learn/your-first-tool#declaring-a-tool, or an old docs.agentfront.dev URL.
- `section` (string): A section's anchor, like "options". Overrides an anchor in `path`.
- `version` (string): A documented FrontMCP version, like "1.9.4", or a minor, like "1.9", for its newest patch. Pass the version resolve_version found for the project. Defaults to the version this endpoint serves.

### `get_skill` (~158 tokens)

Read a FrontMCP skill

FrontMCP's skills catalog (@frontmcp/skills): instructions for building with FrontMCP, from setting up a project to production readiness. Without `name`, lists the skills. With `name`, returns its SKILL.md and the reference files beside it; with `file` too, that file. Skills are step-by-step guides written for coding agents: for the docs themselves use search_docs or get_page, and for runnable code get_example. The catalog is the newest FrontMCP release's, so the tool takes no version.

Input parameters:

- `file` (string): One of the skill's reference files, as listed, like "references/create-tool.md".
- `name` (string): A skill, like "frontmcp-development".

### `get_versions` (~63 tokens)

List the documented versions

Lists the FrontMCP releases these docs cover, newest first, each with its release notes and the endpoint that pins it (https://mcp.frontmcp.dev/<version>). Says which version this endpoint serves. To find the version a project uses, call resolve_version.

### `list_pages` (~170 tokens)

List the docs pages

Lists the FrontMCP docs as the site's sidebar has them, in reading order: Learn (lessons), Reference (APIs, options, deployment), Examples and Compare, each in groups of pages with their titles and paths. Use it to browse, or to find a page by topic when you don't know its name; to find something specific, search_docs or lookup_api is faster. Read a page it lists with get_page. The pages are those of `version`.

Input parameters:

- `section` (string): Only this part of the docs.
- `version` (string): A documented FrontMCP version, like "1.9.4", or a minor, like "1.9", for its newest patch. Pass the version resolve_version found for the project. Defaults to the version this endpoint serves.

### `lookup_api` (~183 tokens)

Look up an API

Finds a FrontMCP API by name in the Reference pages: a decorator (`@Tool`), function or method (`createFetchHandler`, `this.elicit`), option (`inputSchema`, `throttle`), error code (`TOOL_NOT_FOUND`), CLI command or flag (`--target`). Returns the matching entries, most relevant first, each with what the docs say, its page and anchor. Read more with get_page.

Input parameters:

- `limit` (integer): How many entries to return.
- `symbol` (string, required): The name, with or without `@`, `this.` or parentheses.
- `version` (string): A documented FrontMCP version, like "1.9.4", or a minor, like "1.9", for its newest patch. Pass the version resolve_version found for the project. Defaults to the version this endpoint serves.

### `resolve_version` (~257 tokens)

Find the docs version for a project

Says which documented FrontMCP version a project should read, and the endpoint that pins it. Pass the project's package.json, its lockfile (package-lock.json, yarn.lock or pnpm-lock.yaml, including relevant importers and all SDK resolutions), or a version range. An unambiguous lockfile identifies an installation; package.json only the range it allows. If several installations exist, select an npm/pnpm workspace or pass an exact installedVersion read from the resolved SDK package. Call it first when you can read the project.

Input parameters:

- `installedVersion` (string): Exact release read from this project's resolved @frontmcp/sdk/package.json. Takes precedence over a shared lockfile; never guess it from a range.
- `lockfile` (string): The project's lockfile, including the selected importer and all SDK resolutions. A truncated fragment must preserve that context.
- `packageJson` (string): The project's package.json, as it is.
- `range` (string): A version or range, like "1.9.4" or "^1.9.0".
- `workspace` (string): Workspace/importer path in an npm or pnpm lockfile, for example "." or "packages/api". Required when installations are ambiguous.

### `search_docs` (~197 tokens)

Search the docs

Full-text search over the FrontMCP docs, by section: page titles, section headings and prose. Returns up to `limit` sections, best first, each with its page, heading, path (with the #anchor) and the start of its text. Read one with get_page. For an API, option or error code by name, lookup_api is more precise.

Input parameters:

- `limit` (integer): How many sections to return.
- `query` (string, required): Words to look for, like "rate limit", "deploy to cloudflare" or "elicit".
- `section` (string): Only this part of the docs. Choose blog explicitly for dated articles.
- `version` (string): A documented FrontMCP version, like "1.9.4", or a minor, like "1.9", for its newest patch. Pass the version resolve_version found for the project. Defaults to the version this endpoint serves.

### `whats_changed` (~215 tokens)

What changed between two releases

What changed in FrontMCP after `from` up to `to` (the endpoint's version by default): each release's notes, every note the docs make about a change ("Changed in 1.9.5: before, …"), with its page and section, and, when both versions are documented, which pages changed. `from` can be any release, documented or not. Use it to upgrade a project, or to check whether docs for one version hold for another.

Input parameters:

- `from` (string, required): The older release, like "1.9.2" or "1.8".
- `limit` (integer): How many notes to return, newest first.
- `section` (string): Only notes from this part of the docs.
- `to` (string): A documented FrontMCP version, like "1.9.4", or a minor, like "1.9", for its newest patch. Pass the version resolve_version found for the project. Defaults to the version this endpoint serves.

## Diagnostics

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

## Score history

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

## Common questions

### What is the FrontMCP docs MCP server?

FrontMCP docs is an MCP server listed in the public MCP registry as dev.frontmcp.mcp/frontmcp. FrontMCP's docs for coding agents: search, pages, APIs, examples and upgrades, by FrontMCP release. This page covers its hosted endpoint (https://mcp.frontmcp.dev/).

### Is the FrontMCP docs MCP server safe to use?

FrontMCP docs 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 FrontMCP docs MCP server expose?

FrontMCP docs exposes 9 tools: get_example, get_page, get_skill, get_versions, list_pages, and 4 more. Their descriptions and schemas cost roughly 1,646 tokens of context every time the server is loaded.

### Does the FrontMCP docs MCP server require authentication?

No. We connected to FrontMCP docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FrontMCP docs MCP server still maintained?

FrontMCP docs 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.

## Links

- Remote endpoint: https://mcp.frontmcp.dev/
- Website: https://frontmcp.dev/learn/docs-for-your-agent
- Changelog RSS feed: https://verifymcp.io/servers/dev-frontmcp-mcp-frontmcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-frontmcp-mcp-frontmcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-frontmcp-mcp-frontmcp/mcp