81ef52ca01
Directory listings (Glama, and awesome-mcp-servers via its bot) refuse to list a server they cannot build and start. Both files exist for that gate: - mcp-server/Dockerfile packages ONLY mcp-server/, not the RCLL backend. The five tools register at module load, before any HTTP call, so introspection succeeds with no backend reachable — verified by building the image and running an initialize + tools/list handshake over stdio (5 tools, stdout clean of anything but protocol frames; the startup banner goes to stderr). - glama.json names geratron as maintainer, which is how Glama grants the claim needed to attach the Dockerfile on their side. Not a deployment artifact: no image is pushed to any registry, and the compose stack at the repo root is still the way to run the backend.
6 lines
99 B
JSON
6 lines
99 B
JSON
{
|
|
"$schema": "https://glama.ai/mcp/schemas/server.json",
|
|
"maintainers": [
|
|
"geratron"
|
|
]
|
|
}
|