_ registry / mcp streamable-http · checked 3h ago

kaiord-mcp

https://kaiord.com

Registry code: a132ee19173fe457

api record

Kaiord is a fitness data framework. KRD is the canonical JSON format — all conversions go through KRD.

BEFORE creating or editing KRD documents, call the kaiord_get_format_spec tool to get the full specification.

endpoint
https://kaiord.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is kaiord-mcp live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is kaiord-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does kaiord-mcp have?
8 tools: kaiord_convert, kaiord_validate, kaiord_round_trip_validate, kaiord_inspect, kaiord_extract_workout, kaiord_diff, kaiord_get_format_spec, kaiord_list_formats.
Is kaiord-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
417ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • kaiord_get_format_spec open 3h ago

    Get the KRD format specification. Call this before creating or editing KRD documents.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • kaiord_list_formats open 3h ago

    List all supported fitness data formats with capabilities

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • kaiord_convert unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "output_format"
  ],
  "properties": {
    "ftp": {
      "type": "number",
      "description": "Athlete FTP in watts. Required for GCN output when the workout has %FTP power targets (resolved to watts)",
      "exclusiveMinimum": 0
    },
    "input_format": {
      "enum": [
        "fit",
        "tcx",
        "zwo",
        "gcn",
        "krd"
      ],
      "type": "string",
      "description": "Input format (auto-detected from extension)"
    },
    "input_content": {
      "type": "string",
      "description": "Inline content (text or base64 for binary)"
    },
    "output_format": {
      "enum": [
        "fit",
        "tcx",
        "zwo",
        "gcn",
        "krd"
      ],
      "type": "string",
      "description": "Target output format"
    }
  },
  "additionalProperties": false
}
    arguments 41 lines
  • kaiord_validate unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "input_content": {
      "type": "string",
      "description": "Inline KRD JSON content"
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • kaiord_round_trip_validate unknown never probed

    Validate round-trip FIT conversion (FIT → KRD → FIT) and report tolerance violations

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "input_content": {
      "type": "string",
      "description": "Base64-encoded FIT file"
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • kaiord_inspect unknown never probed

    Inspect a fitness file and return a human-readable summary

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "input_format": {
      "enum": [
        "fit",
        "tcx",
        "zwo",
        "gcn",
        "krd"
      ],
      "type": "string",
      "description": "Input format (auto-detected from extension)"
    },
    "input_content": {
      "type": "string",
      "description": "Inline content (text or base64 for binary)"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • kaiord_extract_workout unknown never probed

    Extract the structured workout from a fitness file as JSON

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "input_format": {
      "enum": [
        "fit",
        "tcx",
        "zwo",
        "gcn",
        "krd"
      ],
      "type": "string",
      "description": "Input format (auto-detected from extension)"
    },
    "input_content": {
      "type": "string",
      "description": "Inline content (text or base64 for binary)"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • kaiord_diff unknown never probed

    Compare two fitness files and show differences

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "format1": {
      "enum": [
        "fit",
        "tcx",
        "zwo",
        "gcn",
        "krd"
      ],
      "type": "string",
      "description": "Format of the first input (auto-detected from file1)"
    },
    "format2": {
      "enum": [
        "fit",
        "tcx",
        "zwo",
        "gcn",
        "krd"
      ],
      "type": "string",
      "description": "Format of the second input (auto-detected from file2)"
    },
    "content1": {
      "type": "string",
      "description": "Inline content of the first input (text or base64 for binary)"
    },
    "content2": {
      "type": "string",
      "description": "Inline content of the second input (text or base64 for binary)"
    }
  },
  "additionalProperties": false
}
    arguments 37 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a132ee19173fe457.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a132ee19173fe457/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a132ee19173fe457/badge.svg)](https://brick.blue/agent/a132ee19173fe457?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.