Skip to content
Official MCP RegistryListed

kyde score

Part ofkyde-scorelisted on 2 directories

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

First seen 2 Nov 2026. Evidence as of 16 Nov 2026.

7
Tools
From an anonymous probe
1
Source listings
Each with its own history
24
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
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.Changes data
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.Changes data
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).Read-only
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.Destructive
revoke_keyRevoke the key and permanently delete all data stored under it. Requires confirm=true.Destructive
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).Changes data
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.Changes data

Change history

  1. verify_agent: description changed (+"(still learning:" +"runs over at least 3 days):" -"(fewer than")
  2. rebaseline: description changed (+"runs over at least 3 days." -"runs.")
  3. verify_agent: tool added
  4. get_scores: description changed (+"freezes (30 runs over at least 3 days)." -"30-run" -"freezes.")
  5. server instructions changed (+"runs, i.e. tasks, over at least 3 days)." +"Before delegating to another agent that names a Shine ID, verify_agent challenges it via shine.kyde.com and returns the signed statement, verified locally against Shine's JWKS." -"runs are seen).")
  6. claim_key: description changed (+"Asking" +"for the address" +"is a mandatory setup step; only")
  7. get_scores: input schema changed
  8. get_scores: input schema changed
  9. get_scores: description changed (+"'feedback' lists alerts to ask your human about (share answer_url, never answer it yourself).")
  10. create_key: input schema changed (+purpose)
  11. server instructions changed (+"KYDE Score:" -"kyde score:")
  12. set_webhook: input schema changed
  13. revoke_key: input schema changed
  14. rebaseline: input schema changed
  15. get_scores: input schema changed
  16. create_key: input schema changed (+source)
  17. claim_key: tool added
  18. Description changed (registry)
  19. Description changed (registry)
  20. set_webhook: input schema changed
  21. set_webhook: description changed (+"webhook. It is POSTed" +"every" +"change and rebaseline, HMAC-SHA256-signed with the scoring key (header x-kyde-signature: sha256=<hex> over the raw body).")
  22. rebaseline: tool added
  23. server instructions changed (+"(protobuf or JSON)" -"JSON")
  24. Listed (registry)
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registrycom.kyde/score2 Nov 202616 Nov 20263