mcpbeat Sign in

kyde score MCP Server

answering

kyde score is answering right now. Last checked 8 min ago. It exposes 6 tools.

Agent observability via OpenTelemetry: drift, loop and hijack alerts, e.g. after a prompt injection.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
124 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 22

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 November 2026. No other catalogue keeps this.

6 Nov a tool changed version4 times that day
6 Nov a tool changed the parameters it asks for create_key
5 Nov a tool changed version4 times that day
5 Nov a tool changed the parameters it asks for claim_key
5 Nov a tool appeared claim_key
4 Nov a tool changed version6 times that day
4 Nov 2 tool descriptions were rewritten rebaseline, set_webhook
4 Nov a tool appeared rebaseline
4 Nov a tool changed the parameters it asks for set_webhook
3 Nov a tool changed version
and 11 more, back to 3 November 2026

Nothing serious here today

Today is the operative word: we check kyde score every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add score --transport http https://score.kyde.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://score.kyde.com/mcp
~/.codex/config.toml
[mcp_servers.score]
url = "https://score.kyde.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "score": {
      "url": "https://score.kyde.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "score": {
      "type": "http",
      "url": "https://score.kyde.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

claim
claim_key
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.
key
create_key
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.
rebaseline
rebaseline
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.
revoke
revoke_key
Revoke the key and permanently delete all data stored under it. Requires confirm=true.
scores
get_scores
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.
webhook
set_webhook
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).

Endpoints

URLTransportStateLatencyChecked
https://score.kyde.com/mcp streamable-http answering 157 ms 8 min ago

Alternatives to kyde score

same job, measured the same way
The Context Company
by the-context-company

AI agent observability for production traces, natural-language insights, and improvement loops.

answering
lu
by adelaidasofia

lu.ma events MCP server with draft+confirm safety, audit logging, and prompt-injection scrubbing.…

local only
Datawatch
by cloudcorprecords

Data observability: alerts, freshness checks and schema drift for your data assets.

286 installs/wk local only
Rius
by glassflow

Query your AI agents' traces, errors, cost and alerts in Rius, the agent observability platform.

answering
MCP Observability
by infoinlet-marketplace

Observability for incident agents — query Loki (LogQL), Prometheus (PromQL), Elasticsearch.

44 installs/wk local only
Sable Platform + HyperDX Observability
by sable-inc

Manage Sable AI voice agents, query HyperDX logs and metrics, and deploy — all from your IDE

local only
Monte Carlo
by monte-carlo-data

Data + AI observability — monitor and troubleshoot production-grade agents and the context they use.

answering
NestJS Observe
by nestjs

Production telemetry for NestJS apps: traces, errors, regressions, jobs and alerts.

answering

kyde score — questions

Answers built from our own checks of this server.

What can kyde score do?
It exposes 6 tools, read directly from the server on our last check. Among them: claim_key, create_key, get_scores, rebaseline, revoke_key, set_webhook. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is kyde score working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 124 ms. The bar chart above shows every period we have measured.
How do I connect kyde score?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does kyde score need an API key?
No. kyde score completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is kyde score?
It answers our handshake in 124 ms on average, which is faster than 90% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.