
Ambolt MCP server
Which MCP servers are Ambolt's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry namedev.ambolt/amboltverified in the MCP registry
The registry name sits under ambolt.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools1
- Server calls itselfambolt
- Server version0.2.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 588 ms.
- Its tools do Tell dead pages from pages behind bot protection, but not Fix or unlink broken links inside WordPress.
- Checked on 4 of the 7 days it takes to judge reliability.
Once connected
- For "Tell dead pages from pages behind bot protection", the likely first call is check_page_links.
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: 4 so far
- What an agent can do with it1 of 2 use cases
- Use24 npm downloads a week
- Answeredmeasuring4 of the 7 daily checks it takes to print a share
- Median first answer554 ms
- Space in an agent's context≈ 162 tokensthe definitions of all its tools (1), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 1 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · Find broken links across a website
- can do · Tell dead pages from pages behind bot protection
- cannot · Fix or unlink broken links inside WordPress
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
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 (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). 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 →
check_page_linksChecks every link on one public web page (up to 60 unique links) and reports which are broken, which redirect and which sit behind bot protection. Bot walls (403, 429, Cloudflare and similar challenges) are reported as "blocked", never as…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"ambolt": {
"type": "http",
"url": "https://api.ambolt.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http ambolt https://api.ambolt.dev/mcpclaude.ai, ChatGPT and other clients: add https://api.ambolt.dev/mcp as a custom connector in the settings.
Also shipped through: npm
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.