
Z.Tools MCP server
Which MCP servers are Z.Tools'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-09
- Addresshttps://z.tools/mcpnot in the official registry: answered when asked
No entry in the official MCP registry names this server. It answered on z.tools when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.
- Stateanswerschecked 2026-10-26
- Tools7
- Server calls itselfZ.Tools MCP
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 203 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- Parameters are untyped or undescribed in 6 of 7 tools: check arguments before calling.
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
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer272 ms
- Space in an agent's context≈ 792 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsB · 86 of 100
- Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 6 of 7
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 →
get_tool_docRead the Markdown documentation file for a public Z.Tools tool when one exists.
get_websiteFetch one active curated website or tool by slug or id from the public catalog.
list_website_categoriesList public website directory categories and active website counts for the current locale.
list_websitesList active curated websites and tools with optional category, platform, pricing, and name filters.
recommend_toolRecommend the most relevant public Z.Tools tools for a natural-language user task.
search_toolsSearch the Z.Tools public tool catalog by name, description, slug, and category.
search_websitesSearch the curated website and tool directory by keyword and return active catalog matches.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"z": {
"type": "http",
"url": "https://z.tools/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http z https://z.tools/mcpclaude.ai, ChatGPT and other clients: add https://z.tools/mcp as a custom connector in the settings.
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.