_ registry / mcp http-sse · checked 55m ago

frontmcp-docs

https://mcp.frontmcp.dev

Registry code: 3667f0b755a77593

api record

FrontMCP's documentation, from frontmcp.dev, for one FrontMCP release: the latest at https://mcp.frontmcp.dev, or the release in the URL, like https://mcp.frontmcp.dev/1.9.4. FrontMCP changes between releases, so prefer these docs over what you remember. When you can read the project, call resolve_version with its package.json or lockfile first, and pass the version it gives to the other tools. Find an API, option or error code by name with lookup_api, anything else with search_docs, and read the section with get_page. get_example returns runnable code, whats_changed what an upgrade changes,…

endpoint
https://mcp.frontmcp.dev/
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is frontmcp-docs live?
Yes — it answered the hub's last check (checked 55m ago). It answered 100% of checks over the last 30 days.
Is frontmcp-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does frontmcp-docs have?
9 tools: get_example, get_page, lookup_api, resolve_version, search_docs, whats_changed, get_skill, get_versions, ….
Is frontmcp-docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
735ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
3 open 6 never probed 3 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_skill open 55m ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "file": {
      "type": "string",
      "maxLength": 300,
      "description": "One of the skill's reference files, as listed, like \"references/create-tool.md\"."
    },
    "name": {
      "type": "string",
      "maxLength": 100,
      "description": "A skill, like \"frontmcp-development\"."
    }
  }
}
    arguments 16 lines
  • get_versions open 55m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_pages open 55m ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "section": {
      "enum": [
        "learn",
        "reference",
        "examples",
        "compare"
      ],
      "type": "string",
      "description": "Only this part of the docs."
    },
    "version": {
      "type": "string",
      "maxLength": 20,
      "description": "A documented FrontMCP version, like \"1.9.4\", or a minor, like \"1.9\", for its newest patch. Defaults to the version this endpoint serves."
    }
  }
}
    arguments 21 lines
  • get_example unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "maxLength": 500,
      "minLength": 1,
      "description": "The page, like /reference/sdk/tool or a frontmcp.dev URL."
    },
    "index": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "Which Playground on the page, from 1."
    },
    "version": {
      "type": "string",
      "maxLength": 20,
      "description": "A documented FrontMCP version, like \"1.9.4\", or a minor, like \"1.9\", for its newest patch. Defaults to the version this endpoint serves."
    }
  }
}
    arguments 26 lines
  • get_page unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "maxLength": 500,
      "minLength": 1,
      "description": "The page: /reference/sdk/tool, https://frontmcp.dev/learn/your-first-tool#declaring-a-tool, or an old docs.agentfront.dev URL."
    },
    "section": {
      "type": "string",
      "maxLength": 200,
      "description": "A section's anchor, like \"options\". Overrides an anchor in `path`."
    },
    "version": {
      "type": "string",
      "maxLength": 20,
      "description": "A documented FrontMCP version, like \"1.9.4\", or a minor, like \"1.9\", for its newest patch. Defaults to the version this endpoint serves."
    }
  }
}
    arguments 25 lines
  • lookup_api unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "symbol"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 8,
      "maximum": 30,
      "minimum": 1,
      "description": "How many entries to return."
    },
    "symbol": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1,
      "description": "The name, with or without `@`, `this.` or parentheses."
    },
    "version": {
      "type": "string",
      "maxLength": 20,
      "description": "A documented FrontMCP version, like \"1.9.4\", or a minor, like \"1.9\", for its newest patch. Defaults to the version this endpoint serves."
    }
  }
}
    arguments 27 lines
  • resolve_version unknown never probed

    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; the part about @frontmcp/sdk is enough), or a version range. A lockfile gives the installed version; package.json only the range it allows. Call it first when you can read the project.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "range": {
      "type": "string",
      "maxLength": 100,
      "description": "A version or range, like \"1.9.4\" or \"^1.9.0\"."
    },
    "lockfile": {
      "type": "string",
      "maxLength": 200000,
      "description": "The project's lockfile, or the lines about @frontmcp/sdk."
    },
    "packageJson": {
      "type": "string",
      "maxLength": 100000,
      "description": "The project's package.json, as it is."
    }
  }
}
    arguments 21 lines
  • search_docs unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 8,
      "maximum": 20,
      "minimum": 1,
      "description": "How many sections to return."
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Words to look for, like \"rate limit\", \"deploy to cloudflare\" or \"elicit\"."
    },
    "section": {
      "enum": [
        "learn",
        "reference",
        "examples",
        "compare"
      ],
      "type": "string",
      "description": "Only this part of the docs."
    },
    "version": {
      "type": "string",
      "maxLength": 20,
      "description": "A documented FrontMCP version, like \"1.9.4\", or a minor, like \"1.9\", for its newest patch. Defaults to the version this endpoint serves."
    }
  }
}
    arguments 36 lines
  • whats_changed unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "from"
  ],
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 20,
      "description": "A documented FrontMCP version, like \"1.9.4\", or a minor, like \"1.9\", for its newest patch. Defaults to the version this endpoint serves."
    },
    "from": {
      "type": "string",
      "maxLength": 20,
      "description": "The older release, like \"1.9.2\" or \"1.8\"."
    },
    "limit": {
      "type": "integer",
      "default": 100,
      "maximum": 300,
      "minimum": 1,
      "description": "How many notes to return, newest first."
    },
    "section": {
      "enum": [
        "learn",
        "reference",
        "examples",
        "compare"
      ],
      "type": "string",
      "description": "Only notes from this part of the docs."
    }
  }
}
    arguments 36 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3667f0b755a77593.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3667f0b755a77593/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3667f0b755a77593/badge.svg)](https://brick.blue/agent/3667f0b755a77593?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.