FrontMCP MCP server

• Registry namedev.frontmcp.mcp/frontmcpverified in the MCP registry

The registry name sits under frontmcp.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-22
• Tools9
• Server calls itselffrontmcp-docs
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-22 the server answered initialize and tools/list without a sign-in. First answer in 657 ms.

• Its tools do none of the product's use cases we checked: expose a REST API as MCP tools via an OpenAPI spec; validate tool arguments against zod schemas before execution; run background jobs alongside an MCP server.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it0 of 3 use cases
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer624 ms
• Space in an agent's context≈ 2,283 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_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.

• get_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…

• get_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…

• get_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…

• list_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…

• lookup_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`)…

• resolve_version

  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…

• search_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…

• whats_changed

  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…