Durable Agent Directory

Read-only MCP server for the Durable Agent Directory: search and compare agent-infrastructure tools.

Should I use this

Quality & Safety

A
Description quality
97%
Schema completeness
88%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~702Tokens (tool definitions)
~506 BTypical response size
Moderate attention impact (0.55% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "durable-agent-directory": {
      "url": "https://agents.nexteleven.dev/api/mcp"
    }
  }
}

Remote endpoints

https://agents.nexteleven.dev/api/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_listings(query)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Question-shaped or keyword query, e.g. \"self-hosted tool with approval gates\"."
    }
  },
  "required": [
    "query"
  ]
}
🟢get_listing(slug)

Full structured record for one listing: criteria marks with notes, cost label, evidence and source links, boundaries.

Input Schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Listing slug, e.g. \"deadbolt\"."
    }
  },
  "required": [
    "slug"
  ]
}
🟢get_criteria

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

{
  "type": "object",
  "properties": {}
}
🟢compare_tools(a, b)

The six-criteria comparison matrix for two listings, side by side.

Input Schema

{
  "type": "object",
  "properties": {
    "a": {
      "type": "string",
      "description": "First listing slug."
    },
    "b": {
      "type": "string",
      "description": "Second listing slug."
    }
  },
  "required": [
    "a",
    "b"
  ]
}
🟢get_submission_status(submission_id)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "submission_id": {
      "type": "string",
      "description": "The UUID v4 used when submitting."
    }
  },
  "required": [
    "submission_id"
  ]
}
🟢pre_check(claims)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "claims": {
      "type": "object",
      "description": "Map of criterion key to public documentation URL.",
      "properties": {
        "approvalGates": {
          "type": "string"
        },
        "restartRecovery": {
          "type": "string"
        },
        "evidenceTrail": {
          "type": "string"
        },
        "killSwitch": {
          "type": "string"
        },
        "policyControls": {
          "type": "string"
        },
        "isolation": {
          "type": "string"
        }
      }
    }
  },
  "required": [
    "claims"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools