v1.0.1 — bridge gate, badge, attribution

No change to the server or its catalogue — the hosted endpoint at https://mcp.kyrodata.com/mcp is what it was. This release carries what landed in the repository around it.

• The stdio bridge gets a CI gate. bridge/test_server.py drives server.py as a subprocess against a fake upstream, and asserts the transport it promises.
• The Glama badge renders. It pointed at a connector badge their image proxy refuses; it now points at the listing's own score badge.
• Links to /developers say where they came from, so a visit from this README is attributable.

Since 2026-09-11 the server answers discovery without a key — initialize, tools/list, ping — so any client can see the 15 tools before creating one. Calling a tool still needs a key from https://kyrodata.com/user/api-keys.

v1.0.0 — stdio bridge

The stdio bridge to the Kyrodata MCP server, at the exact commit Glama built and published as release v1.0.0.

The real server is remote — https://mcp.kyrodata.com/mcp — and any client that speaks remote HTTP should point straight at it: one hop fewer and nothing to install. This image exists for two cases only: a client that can only launch a local command, and a directory that scores what it can build, start and introspect itself.

It implements no tool. initialize, tools/list and tools/call are forwarded unchanged, so there is no second catalogue in here that can drift from the server's (15 read-only tools, catalogue 1.0.10). Python standard library only — no requirements file, no pip layer.

Needs KYRODATA_API_KEY at runtime and outbound HTTPS. The key never goes in the image:

docker run -i --rm -e KYRODATA_API_KEY=kd_live_... <image>