kyde score
REMOTE · SCORE.KYDE.COM
Behavioral drift scores for AI agents from OpenTelemetry: create a key, send OTLP, read scores.
Available components
Last scanned (3 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (rebaseline). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 526 tokens (~105/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 3 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −1
- Stability: 0.07 → fail ▼ security
- “set_webhook” changed the type of “webhook_url”: string → string|null ▼ functional
- Tool coverage: 56% → 67% ▲ functional
- Server version: 0.7.0 → 0.7.1 functional
- “set_webhook” reworded the description of “webhook_url” cosmetic
- 4 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- New tool “rebaseline”, which the server declares destructive security
- Tool “set_webhook” rewrote its description, which is the text the model reads security
- Tool coverage: 67% → 56% ▼ functional
- Schema quality: 83 → 102 ▼ functional
- Server version: 0.2.6 → 0.7.0 functional
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 2026.10.27-0 → 0.2.6 functional
- 2 Nov 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://score.kyde.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=score.kyde.com | CN=YE1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 56557dfef5a91ec2bcca673c548b5621ef2 |
| SANs: score.kyde.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of score.kyde.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kyde.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://score.kyde.com/mcp | Verified | 200 | |
| http (plaintext) | http://score.kyde.com/mcp | HTTPS enforced | 301 | https://score.kyde.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_key Create scoring key ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_url | string | – | Optional https URL notified on band changes. |
No output schema declared.
No examples provided.
get_scores Get drift scores ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | Scoring key; omit when sent as x-kyde-key header. |
No output schema declared.
No examples provided.
rebaseline Reset agent baseline ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | – |
| key | string | – | Scoring key; omit when sent as x-kyde-key header. |
| service_name | string | yes | – |
No output schema declared.
No examples provided.
revoke_key Revoke key and delete data ~53
Revoke the key and permanently delete all data stored under it. Requires confirm=true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | – |
| key | string | – | Scoring key; omit when sent as x-kyde-key header. |
No output schema declared.
No examples provided.
set_webhook Set alert webhook ~103
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).
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | Scoring key; omit when sent as x-kyde-key header. |
| webhook_url | string|null | yes | https URL, or null to remove the webhook (the key becomes poll-only). |
No output schema declared.
No examples provided.
How do I install the kyde score MCP server?
kyde score is a hosted endpoint at https://score.kyde.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · score.kyde.com
claude mcp add --transport http com-kyde-score 'https://score.kyde.com/mcp'
What is the kyde score MCP server?
kyde score is an MCP server listed in the public MCP registry as com.kyde/score. Behavioral drift scores for AI agents from OpenTelemetry: create a key, send OTLP, read scores. This page covers its hosted endpoint (https://score.kyde.com/mcp).
Is the kyde score MCP server safe to use?
kyde score scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the kyde score MCP server expose?
kyde score exposes 5 tools: create_key, get_scores, set_webhook, rebaseline, revoke_key. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.
Does the kyde score MCP server require authentication?
No. We connected to kyde score without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the kyde score MCP server still maintained?
kyde score is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.