Deaddit

Methodology

Every score on Deaddit traces to a fleet run ID. The rubric below is versioned, public, and applied by automation with no override path. If the fleet didn't measure it, we don't print it.

Rubric v1.0

Deaddit MCP Server Quality Rubric

Life States

• alive — Score >= 70 and no critical failures
• ailing — Score 40-69 or intermittent failures
• dead — Fails install/start on 3 consecutive cycles
• resurrected — Previously dead, now passing

Thresholds

• alive_min: 70
• ailing_min: 40
• dead_consecutive_failures: 3

Raw Rubric JSON

{
  "version": "1.0",
  "name": "Deaddit MCP Server Quality Rubric",
  "axes": [
    {
      "id": "install_success",
      "weight": 15,
      "description": "Package installs without fatal errors"
    },
    {
      "id": "clean_startup",
      "weight": 10,
      "description": "Server starts without crashing or hanging"
    },
    {
      "id": "handshake_conformance",
      "weight": 15,
      "description": "MCP initialize/initialized handshake completes correctly"
    },
    {
      "id": "tool_schema_validity",
      "weight": 15,
      "description": "tools/list returns valid JSON Schema for each tool"
    },
    {
      "id": "readme_accuracy",
      "weight": 10,
      "description": "Declared tools in README match actual tools/list output"
    },
    {
      "id": "auth_hygiene",
      "weight": 10,
      "description": "No plaintext secrets demanded, no wildcard scopes"
    },
    {
      "id": "stability_under_load",
      "weight": 10,
      "description": "Handles N sequential + M concurrent benign tool calls without crash"
    },
    {
      "id": "maintenance_pulse",
      "weight": 10,
      "description": "Commit recency and issue responsiveness"
    },
    {
      "id": "dependency_health",
      "weight": 5,
      "description": "No critical vulnerabilities in direct dependencies"
    }
  ],
  "life_states": {
    "alive": "Score >= 70 and no critical failures",
    "ailing": "Score 40-69 or intermittent failures",
    "dead": "Fails install/start on 3 consecutive cycles",
    "resurrected": "Previously dead, now passing"
  },
  "thresholds": {
    "alive_min": 70,
    "ailing_min": 40,
    "dead_consecutive_failures": 3
  }
}

Probe Process

1. Discover candidate MCP servers via GitHub search, registries, npm, PyPI.
2. Launch each in an isolated container (no LAN access, no credentials, resource caps).
3. Attempt install → start → MCP handshake → tools/list → schema validation → light load.
4. Score against the rubric above. Append-only run records.
5. Publish. Corrections in place with visible changelog.

Third-party content (READMEs, tool descriptions) is treated as untrusted data, never executed as instructions.