Durable Agent Directory
REMOTE · AGENTS.NEXTELEVEN.DEV
Read-only MCP server for the Durable Agent Directory: search and compare agent-infrastructure tools.
Available components
Last scanned (23 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 395 tokens (~65/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 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.
- 16 Nov 26 +7
- Authorization: unverified → partial ▲ security
- Server version: 0.1.0 → 0.1.1 functional
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 63
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 21 Nov 2026 · Probed https://agents.nexteleven.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agents.nexteleven.dev | CN=YR1,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | RSA 2048 | SHA256-RSA | 579007ad7aba7ca7f297aff8870a608a8ea |
| SANs: agents.nexteleven.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 agents.nexteleven.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| nexteleven.dev. | No DS | 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 |
|---|---|
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; img-src 'self' data: https:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://plausible.io https://pagead2.googlesyndication.com https://partner.googleadservices.com https://tpc.googlesyndication.com; connect-src 'self' https://plausible.io https://pagead2.googlesyndication.com https://googleads.g.doubleclick.net; frame-src https://googleads.g.doubleclick.net https://tpc.googlesyndication.com https://pagead2.googlesyndication.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agents.nexteleven.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://agents.nexteleven.dev/api/mcp | HTTPS enforced | 301 | https://agents.nexteleven.dev/api/mcp |
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 →
compare_tools ~42
The six-criteria comparison matrix for two listings, side by side.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | First listing slug. |
| b | string | yes | Second listing slug. |
No output schema declared.
No examples provided.
get_criteria ~41
The six criteria every listing is marked against, with definitions and the support values (native = Built in, pattern = Documented pattern, none = Not claimed).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_listing ~46
Full structured record for one listing: criteria marks with notes, cost label, evidence and source links, boundaries.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Listing slug, e.g. "deadbolt". |
No output schema declared.
No examples provided.
get_submission_status ~67
Receipt status for a submission made to POST /api/lead, by its submission_id (UUID v4). Reports receipt metadata only (received, when, intent, sandbox or real) — never the inquiry contents.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_id | string | yes | The UUID v4 used when submitting. |
No output schema declared.
No examples provided.
pre_check ~92
Free mechanical pre-check before a paid verification review: given a claims object mapping each criterion key (approvalGates, restartRecovery, evidenceTrail, killSwitch, policyControls, isolation) to a public documentation URL, reports which criteria have documentation linked and which are missing. It checks that links were supplied, never that the documentation proves the claim.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | object | yes | Map of criterion key to public documentation URL. |
No output schema declared.
No examples provided.
search_listings ~67
Keyword search over the directory catalog (names, descriptions, tags, criteria marks). Returns matching listings with scores and what matched. This is keyword matching, not semantic search.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Question-shaped or keyword query, e.g. "self-hosted tool with approval gates". |
No output schema declared.
No examples provided.
How do I install the Durable Agent Directory MCP server?
Durable Agent Directory is a hosted endpoint at https://agents.nexteleven.dev/api/mcp, 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 · agents.nexteleven.dev
claude mcp add --transport http dev-nexteleven-durable-agent-directory 'https://agents.nexteleven.dev/api/mcp'
What is the Durable Agent Directory MCP server?
Durable Agent Directory is an MCP server listed in the public MCP registry as dev.nexteleven/durable-agent-directory. Read-only MCP server for the Durable Agent Directory: search and compare agent-infrastructure tools. This page covers its hosted endpoint (https://agents.nexteleven.dev/api/mcp).
Is the Durable Agent Directory MCP server safe to use?
Durable Agent Directory scores 73 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 Durable Agent Directory MCP server expose?
Durable Agent Directory exposes 6 tools: search_listings, get_listing, get_criteria, compare_tools, get_submission_status, pre_check. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.
Does the Durable Agent Directory MCP server require authentication?
No. We connected to Durable Agent Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Durable Agent Directory MCP server still maintained?
Durable Agent Directory is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Durable Agent Directory MCP server?
VerifyMCP ran 13 checks on Durable Agent Directory, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.