ZeroCrew directory
REMOTE · ZEROCREW.AI
Find the AI agents and tools behind every business job, curated for zero-employee founders.
Available components
Last scanned (2 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 663 tokens (~165/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool “get_tool” rewrote its description, which is the text the model reads security
- Tool “list_job” rewrote its description, which is the text the model reads security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
- Tool “get_tool” rewrote its description, which is the text the model reads security
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://zerocrew.ai/api/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zerocrew.ai | CN=YR2,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | RSA 2048 | SHA256-RSA | 560a8e9f17691203f1becef52fe27bdb412 |
| SANs: zerocrew.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of zerocrew.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| zerocrew.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zerocrew.ai/api/mcp/public | Verified | 200 | |
| http (plaintext) | http://zerocrew.ai/api/mcp/public | HTTPS enforced | 308 | https://zerocrew.ai/api/mcp/public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_tool Get a tool's page ~127
Get one tool's public page from the ZeroCrew directory by its slug (from search_tools or list_job): what it does, its website, pricing, MCP server address if it has one, platforms, how many ZeroCrew Developers use it now and rate it a must use, Developers' published reviews (verdict, how they use it, what they like, what can be improved, and the maker's reply), its zerocrew.ai page, and up to 4 alternatives from the same role.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The tool's slug, like "retell-ai". |
No output schema declared.
No examples provided.
list_job List the tools for a job ~152
List the tools for one job in the ZeroCrew directory, like role "support" and job "ai-receptionists", A to Z by default. ZeroCrew doesn't rank them. Set sort to "must_use" or "using_now" to order them by how many ZeroCrew Developers rate a tool a must use or use it now; the answer says which order it used. Returns up to 50 tools. list_roles shows every role and job.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | yes | The job's slug in that role, like "ai-receptionists". |
| role | string | yes | The business role, like "support". |
| sort | string | – | az (default), must_use, or using_now. |
No output schema declared.
No examples provided.
list_roles List roles and jobs ~74
List every role in the ZeroCrew directory (customer support, sales, engineering, and more), the jobs inside each role, and how many live tools each has, with their zerocrew.ai pages. Use it to see what the directory covers, or to find the role and job slugs for search_tools and list_job.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_tools Search the ZeroCrew directory ~251
Search the ZeroCrew directory of AI agents, apps, and models that founders use to run a company. Use it when someone needs a tool for a job, like "customer interviews", "ai receptionist", or "bookkeeping". Matches the words against each tool's name, maker, description, and its role and job. Returns up to 20 tools, best match first, each with its zerocrew.ai page. Narrow it with role, job, kind, or mcp. Call get_tool for one tool's full page.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | – | Only tools for this job, by its slug, like "ai-receptionists". list_roles shows every job. |
| kind | string | – | Only agents, apps, or models. "agent" also finds apps with an agent built in. |
| limit | integer | – | How many tools to return, 1 to 20. Default 20. |
| mcp | boolean | – | true for only tools that have an MCP server. |
| query | string | yes | What the tool should do, in plain words. Up to 200 characters. |
| role | string | – | Only tools for this business role. list_roles shows every role. |
No output schema declared.
No examples provided.
How do I install the ZeroCrew directory MCP server?
ZeroCrew directory is a hosted endpoint at https://zerocrew.ai/api/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · zerocrew.ai
claude mcp add --transport http zerocrewai-zerocrew-directory 'https://zerocrew.ai/api/mcp/public'
What is the ZeroCrew directory MCP server?
ZeroCrew directory is an MCP server listed in the public MCP registry as io.github.zerocrewai/zerocrew-directory. Find the AI agents and tools behind every business job, curated for zero-employee founders. This page covers its hosted endpoint (https://zerocrew.ai/api/mcp/public).
Is the ZeroCrew directory MCP server safe to use?
ZeroCrew directory scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ZeroCrew directory MCP server expose?
ZeroCrew directory exposes 4 tools: search_tools, get_tool, list_roles, list_job. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.
Does the ZeroCrew directory MCP server require authentication?
No. We connected to ZeroCrew directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ZeroCrew directory MCP server still maintained?
ZeroCrew directory is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.