Koskamo

Kyde Score MCP

An official MCP server for Kyde Score that allows AI agents to manage their behavioral observability keys and query their drift, loop, and hijack detection scores. It supports creating keys, setting webhooks, rebasing baselines, and revoking access, enabling agents to self-monitor their operational integrity against deterministic statistical baselines.

Visit Kyde

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Kyde Score MCP logo, by KydeVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Kyde
You need:Configure the key as an `x-kyde-key` (or `Authorization: Bearer`) header, or pass it as the `key` tool argument.
MCP endpoint (Streamable HTTP)
https://score.kyde.com/mcp
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (1)

Can change data (5)

6 of 6 have a description · 6 of 6 declare behavior hints · 4 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to kyde.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Create a new API key for agent telemetry
  • Query current behavioral scores for all agents
  • Set or update the webhook URL for alerts
  • Revoke an existing API key and delete data

Source and maintenance

Vendor evidenceRegistry 0.8.24
mcp-registry: com.kyde/score@0.8.24Project website

Protocol and capabilities

Server
kyde-score 0.8.9
MCP protocol negotiated in check
2025-06-18
Tools
6 advertised
Resources
2 advertised
Resource templates
0 advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

kyde score: behavioral drift scoring for AI agents. Typical flow: create_key once (save the key; webhook_url optional), point an OTLP/HTTP exporter (protobuf or JSON) at https://score.kyde.com with header x-kyde-key, then get_scores to read 0-100 drift scores per agent (status is 'learning' until 30 runs are seen). Recommend set_webhook so band changes reach a human even when nobody polls.

Tools

6 advertised

create_key — Create scoring key
Advertised by the server during the last successful anonymous check.

Create a scoring key (no signup). One key covers all agents, identified by OTel service.name. webhook_url (https) is optional but recommended: it receives an HMAC-signed POST when any agent's score changes band.

create_key input schema
{
  "type": "object",
  "properties": {
    "source": {
      "type": "string",
      "description": "Optional: where you found kyde score (e.g. skill, llms.txt, registry, website). Aggregate adoption stats only."
    },
    "webhook_url": {
      "type": "string",
      "description": "Optional https URL notified on band changes."
    }
  },
  "additionalProperties": false
}
create_key output schema
{
  "type": "object",
  "required": [
    "key",
    "method_version",
    "webhook",
    "next_steps"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "The scoring key — shown once."
    },
    "webhook": {
      "type": [
        "string",
        "null"
      ]
    },
    "next_steps": {
      "type": "string"
    },
    "method_version": {
      "type": "string"
    }
  }
}
create_key annotations
{
  "title": "Create scoring key",
  "readOnlyHint": false,
  "openWorldHint": false,
  "destructiveHint": false
}
get_scores — Get drift scores
Advertised by the server during the last successful anonymous check.
Advertised read-only

Current drift score per agent under the key: 0-39 deviating, 40-69 watch, 70-100 normal; status 'learning' until the 30-run baseline freezes.

get_scores input schema
{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "Scoring key; omit when sent as x-kyde-key header."
    }
  },
  "additionalProperties": false
}
get_scores output schema
{
  "type": "object",
  "required": [
    "service_version",
    "method_version",
    "claimed",
    "agents",
    "webhook"
  ],
  "properties": {
    "agents": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "service_name",
          "status",
          "score",
          "band",
          "runs_seen",
          "runs_needed",
          "method_version"
        ],
        "properties": {
          "band": {
            "type": [
              "string",
              "null"
            ],
            "description": "deviating (0-39) | watch (40-69) | normal (70-100); null while learning."
          },
          "score": {
            "type": [
              "integer",
              "null"
            ],
            "description": "0-100; null while learning."
          },
          "alarms": {
            "type": "array",
            "items": {
              "type": "object"
            }
          },
          "status": {
            "enum": [
              "learning",
              "scored"
            ],
            "type": "string"
          },
          "runs_seen": {
            "type": "integer"
          },
          "runs_needed": {
            "type": "integer"
          },
          "alarms_total": {
            "type": "integer"
          },
          "service_name": {
            "type": "string"
          },
          "method_version": {
            "type": "string"
          },
          "n_live_records": {
            "type": "integer"
          },
          "rebaselined_at": {
            "type": [
              "string",
              "null"
            ]
          },
          "n_baseline_records": {
            "type": "integer"
          },
          "baseline_fingerprint": {
            "type": [
              "string",
              "null"
            ]
          }
        }
      }
    },
    "claimed": {
      "type": "boolean"
    },
    "webhook": {
      "type": [
        "string",
        "null"
      ]
    },
    "degraded": {
      "type": "object",
      "properties": {
        "reason": {
          "type": [
            "string",
            "null"
          ]
        },
        "dropped_today": {
          "type": "integer"
        }
      },
      "description": "Present only when records were dropped today (quota/limits)."
    },
    "method_version": {
      "type": "string"
    },
    "service_version": {
      "type": "string"
    }
  }
}
get_scores annotations
{
  "title": "Get drift scores",
  "readOnlyHint": true,
  "openWorldHint": false
}
set_webhook — Set alert webhook
Advertised by the server during the last successful anonymous check.

Add or change the https webhook. It is POSTed on every band change and rebaseline, HMAC-SHA256-signed with the scoring key (header x-kyde-signature: sha256=<hex> over the raw body).

set_webhook input schema
{
  "type": "object",
  "required": [
    "webhook_url"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "Scoring key; omit when sent as x-kyde-key header."
    },
    "webhook_url": {
      "type": [
        "string",
        "null"
      ],
      "description": "https URL, or null to remove the webhook (the key becomes poll-only)."
    }
  },
  "additionalProperties": false
}
set_webhook output schema
{
  "type": "object",
  "required": [
    "webhook"
  ],
  "properties": {
    "webhook": {
      "type": [
        "string",
        "null"
      ]
    }
  }
}
set_webhook annotations
{
  "title": "Set alert webhook",
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
claim_key — Attach a human to the key
Advertised by the server during the last successful anonymous check.
Open-world

Attach your human's email to the key (double opt-in: Kyde mails a confirmation link). Once confirmed, the key is claimed: the human gets the management dashboard, and rebaseline, webhook changes and revocation work only for them — no agent, including you, can reset its own score. Ask the human once for the address; never invent or guess one; skip when get_scores already shows claimed: true.

claim_key input schema
{
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "Scoring key; omit when sent as x-kyde-key header."
    },
    "email": {
      "type": "string",
      "description": "The human's email address, given by them."
    },
    "product_updates": {
      "type": "boolean",
      "description": "Separate, optional consent: may Kyde send occasional product updates to this address? Ask as its own question; pass true only on an explicit yes. Default false; revocable in the dashboard."
    }
  },
  "additionalProperties": false
}
claim_key output schema
{
  "type": "object",
  "required": [
    "claim",
    "email_sent",
    "next"
  ],
  "properties": {
    "next": {
      "type": "string"
    },
    "claim": {
      "type": "string"
    },
    "email_sent": {
      "type": "boolean"
    }
  }
}
claim_key annotations
{
  "title": "Attach a human to the key",
  "readOnlyHint": false,
  "openWorldHint": true,
  "destructiveHint": false
}
rebaseline — Reset agent baseline
Advertised by the server during the last successful anonymous check.
Advertised destructive

Forget one agent's learned baseline and score and relearn from its next 30 runs. For intended behavior changes (new model, new task) that left the agent permanently deviating. The reset is permanently visible: records and alarms stay stored, the agent carries rebaselined_at, and the reset itself is recorded as a rebaseline alarm naming the score/band it erased. Requires confirm=true and the human's explicit go-ahead.

rebaseline input schema
{
  "type": "object",
  "required": [
    "service_name",
    "confirm"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "Scoring key; omit when sent as x-kyde-key header."
    },
    "confirm": {
      "type": "boolean"
    },
    "service_name": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
rebaseline output schema
{
  "type": "object",
  "required": [
    "service_name",
    "status",
    "rebaselined_at"
  ],
  "properties": {
    "status": {
      "type": "string"
    },
    "runs_seen": {
      "type": "integer"
    },
    "runs_needed": {
      "type": "integer"
    },
    "service_name": {
      "type": "string"
    },
    "method_version": {
      "type": "string"
    },
    "rebaselined_at": {
      "type": "string"
    }
  }
}
rebaseline annotations
{
  "title": "Reset agent baseline",
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": true
}
revoke_key — Revoke key and delete data
Advertised by the server during the last successful anonymous check.
Advertised destructive

Revoke the key and permanently delete all data stored under it. Requires confirm=true.

revoke_key input schema
{
  "type": "object",
  "required": [
    "confirm"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "Scoring key; omit when sent as x-kyde-key header."
    },
    "confirm": {
      "type": "boolean"
    }
  },
  "additionalProperties": false
}
revoke_key output schema
{
  "type": "object",
  "required": [
    "revoked"
  ],
  "properties": {
    "revoked": {
      "type": "boolean"
    }
  }
}
revoke_key annotations
{
  "title": "Revoke key and delete data",
  "readOnlyHint": false,
  "openWorldHint": false,
  "destructiveHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

2 advertised

llms.txt — kyde score — service reference

Advertised by the server during the last successful anonymous check.

The whole service, machine-readable: endpoints, integration steps, score bands, limits, privacy.

llms.txt URI
https://score.kyde.com/llms.txt

MIME type: text/plain

skill.md — kyde-score agent skill

Advertised by the server during the last successful anonymous check.

Step-by-step integration skill for Claude Code and compatible harnesses: key, exporter env vars, verification, MCP setup.

skill.md URI
https://score.kyde.com/skill.md

MIME type: text/markdown

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1039 ms
95th percentile latency
1039 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1039 ms · metadata changed · 6 tool(s), 2 resource(s), 0 resource template(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http kyde-score-mcp https://score.kyde.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add kyde-score-mcp --url https://score.kyde.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable kyde-score-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "kyde-score-mcp": {
      "url": "https://score.kyde.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "kyde-score-mcp": {
      "type": "streamableHttp",
      "url": "https://score.kyde.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start kyde-score-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "kyde-score-mcp": {
      "type": "http",
      "url": "https://score.kyde.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http kyde-score-mcp https://score.kyde.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://score.kyde.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "kyde-score-mcp": {
      "serverUrl": "https://score.kyde.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Kyde Score MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,557

Do you run Kyde Score MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing