Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"fonto-docs": {
"url": "https://fonto-docs.elliat.nl/mcp",
"type": "http"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP server that makes the Fonto XML documentation accessible to AI tools like Claude Code, Cursor, and Claude Desktop. Live at fonto-docs.elliat.nl.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
fonto://catalogAll ~2000 pages with real titles, product grouping, and ancestry paths
fonto://catalog
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / writing
Dynamic problem-solving through sequential thought chains
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Persistent memory using a knowledge graph
An autonomous agent that conducts deep research on any data using any LLM providers
MCP Security Weekly
Get CVE alerts and security updates for io.github.DrRataplan/fonto-docs and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that makes the Fonto XML documentation accessible to AI tools like Claude Code, Cursor, and Claude Desktop. Live at fonto-docs.elliat.nl.
The Fonto docs are rendered by a JavaScript SPA, which makes them impossible for AI to read directly. This server fetches the underlying XML and converts it to clean, readable Markdown on demand.
MCP (Model Context Protocol) is a standard way to give AI assistants access to external tools. Once you connect this server to your AI tool, it gains access to these tools and resources:
| Tool | What it does |
|---|---|
search_fonto_docs | Search by keyword — returns matching pages with titles, descriptions, and slugs |
get_fonto_page | Fetch the full content of a page by its slug |
list_pages | List all pages matching a keyword, with full section hierarchy — useful for discovery |
| Resource | What it contains |
|---|---|
fonto://catalog | All ~2000 pages with real titles, product grouping, and ancestry paths |
You can then ask things like "How does addDocumentChangeCallback work?" and the AI will look it up in the live Fonto docs.
The server is already running at https://fonto-docs.elliat.nl/mcp — you just need to point your tool at it.
claude mcp add --transport http fonto-docs https://fonto-docs.elliat.nl/mcp
Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):
{
"mcpServers": {
"fonto-docs": {
"type": "http",
"url": "https://fonto-docs.elliat.nl/mcp"
}
}
}
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"fonto-docs": {
"type": "http",
"url": "https://fonto-docs.elliat.nl/mcp"
}
}
}
Once connected, ask your AI assistant:
The server also exposes a plain HTTP API if you want to use it without MCP:
GET /search?q={query} — search pages by keywordGET /page/{slug} — fetch a page as MarkdownGET /catalog — full page catalog grouped by section; add ?section={keyword} to filterThe Fonto documentation site stores its content as XML at predictable URLs under /static/xml/. This server fetches those XML files directly and converts them to Markdown, bypassing the JavaScript rendering. Page content is never cached — every get_fonto_page call goes to documentation.fontoxml.com live. The page catalog (used by list_pages and fonto://catalog) is fetched once from the Fonto search index on first use and held in memory for the lifetime of the process.
npm install
npm start # runs on port 8080 by default
PORT=3000 npm start
PRs welcome. The XML-to-Markdown conversion in src/fonto.js handles two formats:
<topic>, <body>, <section> structure<type>, <members>, <description> structureIf you find pages that don't convert well, open an issue with the slug.
MIT