kyde score
com.kyde/scoreVersion 0.11.18Agent observability via OpenTelemetry: drift, loop and hijack alerts, e.g. after a prompt injection.
Status
Responds156 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:04 UTC
- Latency
- 156 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://score.kyde.com/mcpResponds156 msNo sign-in
Claude Code
claude mcp add --transport http score https://score.kyde.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: score
Remote MCP server URL: https://score.kyde.com/mcpCursor
{
"mcpServers": {
"score": {
"url": "https://score.kyde.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"score","type":"http","url":"https://score.kyde.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
7 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
claim_keyAttach 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. Asking the human for the address once is a mandatory setup step; only the human may decline. Never invent or guess an address; skip only when get_scores already shows claimed: true. | No | No | Not declared | Yes |
create_keyCreate 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. | No | No | Not declared | No |
get_scoresCurrent drift score per agent under the key: 0-39 deviating, 40-69 watch, 70-100 normal; status 'learning' until the baseline freezes (30 runs over at least 3 days). 'feedback' lists alerts to ask your human about (share answer_url, never answer it yourself). | Not declared | Yes | Not declared | No |
rebaselineForget one agent's learned baseline and score and relearn from its next 30 runs over at least 3 days. 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. | Yes | No | Yes | No |
revoke_keyRevoke the key and permanently delete all data stored under it. Requires confirm=true. | Yes | No | Not declared | No |
set_webhookAdd 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). | No | No | Yes | No |
verify_agentProve who is on the other end before delegating work: challenges the Shine ID at shine.kyde.com, waits for the agent to confirm over its own authenticated connection, then verifies the Ed25519-signed statement against Shine's JWKS and compares the nonce hash. Needs no scoring key. The verified agent typically polls every 30 s, so a first call often answers 'pending' — call verify_agent again with the returned challenge_id, result_token and nonce to keep waiting. In the result, band 'learning' means identity confirmed but behavior not yet scored (still learning: 30 runs over at least 3 days): whether to delegate to a learning agent is the challenger's policy call. | No | No | Not declared | Yes |
Details
- Registry status
- Active
- Published
- Nov 14, 2026
- Updated
- Nov 14, 2026
- Repository
- Not given
- Categories (suggested)
- AI modelsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared