io.github.pablo-albaladejo/kaiord
REMOTE · KAIORD.COM · 2 COMPONENTS
Convert, validate, and inspect workout files (FIT, TCX, ZWO, Garmin Connect) for AI agents.
Available components
Last scanned (3 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 679 tokens (~61/item across 11 items; 8 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 62
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://kaiord.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kaiord.com | CN=YE2,O=Let's Encrypt,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 56ad4ecce2912331bed0a2bec24268db40c |
| SANs: *.kaiord.com, kaiord.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 secure
Validation of kaiord.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kaiord.com. | present | 2371 | 13 | Verified |
| kaiord.com. | Verified address RRset verified with the apex keys |
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://kaiord.com/mcp | Verified | 200 | |
| http (plaintext) | http://kaiord.com/mcp | Inconclusive | 405 |
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 →
kaiord_convert ~146
Convert between fitness data formats (FIT, TCX, ZWO, GCN, KRD). FIT output is returned as base64 text unless output_file is given. On the remote endpoint, ZWO input is checked for well-formedness only, not against the XSD, and only structured workouts are accepted.
| Name | Type | Req | Description |
|---|---|---|---|
| ftp | number | – | Athlete FTP in watts. Required for GCN output when the workout has %FTP power targets (resolved to watts) |
| input_content | string | – | Inline content (text or base64 for binary) |
| input_format | string | – | Input format (auto-detected from extension) |
| output_format | string | yes | Target output format |
No output schema declared.
No examples provided.
kaiord_diff ~99
Compare two fitness files and show differences
| Name | Type | Req | Description |
|---|---|---|---|
| content1 | string | – | Inline content of the first input (text or base64 for binary) |
| content2 | string | – | Inline content of the second input (text or base64 for binary) |
| format1 | string | – | Format of the first input (auto-detected from file1) |
| format2 | string | – | Format of the second input (auto-detected from file2) |
No output schema declared.
No examples provided.
kaiord_extract_workout ~55
Extract the structured workout from a fitness file as JSON
| Name | Type | Req | Description |
|---|---|---|---|
| input_content | string | – | Inline content (text or base64 for binary) |
| input_format | string | – | Input format (auto-detected from extension) |
No output schema declared.
No examples provided.
kaiord_get_format_spec ~28
Get the KRD format specification. Call this before creating or editing KRD documents.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kaiord_inspect ~54
Inspect a fitness file and return a human-readable summary
| Name | Type | Req | Description |
|---|---|---|---|
| input_content | string | – | Inline content (text or base64 for binary) |
| input_format | string | – | Input format (auto-detected from extension) |
No output schema declared.
No examples provided.
kaiord_list_formats ~19
List all supported fitness data formats with capabilities
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kaiord_round_trip_validate ~43
Validate round-trip FIT conversion (FIT → KRD → FIT) and report tolerance violations
| Name | Type | Req | Description |
|---|---|---|---|
| input_content | string | – | Base64-encoded FIT file |
No output schema declared.
No examples provided.
kaiord_validate ~61
Validate a KRD JSON document against the schema On the remote endpoint, ZWO input is checked for well-formedness only, not against the XSD, and only structured workouts are accepted.
| Name | Type | Req | Description |
|---|---|---|---|
| input_content | string | – | Inline KRD JSON content |
No output schema declared.
No examples provided.
How do I install the io.github.pablo-albaladejo/kaiord MCP server?
io.github.pablo-albaladejo/kaiord is a hosted endpoint at https://kaiord.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 · kaiord.com
claude mcp add --transport http pablo-albaladejo-kaiord 'https://kaiord.com/mcp'
What is the io.github.pablo-albaladejo/kaiord MCP server?
io.github.pablo-albaladejo/kaiord is an MCP server listed in the public MCP registry as io.github.pablo-albaladejo/kaiord. Convert, validate, and inspect workout files (FIT, TCX, ZWO, Garmin Connect) for AI agents. This page covers its hosted endpoint (https://kaiord.com/mcp).
Is the io.github.pablo-albaladejo/kaiord MCP server safe to use?
io.github.pablo-albaladejo/kaiord scores 65 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 io.github.pablo-albaladejo/kaiord MCP server expose?
io.github.pablo-albaladejo/kaiord exposes 8 tools: kaiord_get_format_spec, kaiord_list_formats, kaiord_convert, kaiord_validate, kaiord_round_trip_validate, and 3 more. Their descriptions and schemas cost roughly 505 tokens of context every time the server is loaded.
Does the io.github.pablo-albaladejo/kaiord MCP server require authentication?
No. We connected to io.github.pablo-albaladejo/kaiord without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.pablo-albaladejo/kaiord MCP server still maintained?
io.github.pablo-albaladejo/kaiord 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.