build: add Dockerfile for Glama MCP server verification - #51
Merged
Conversation
awesome-mcp-servers (punkpeye) changed its listing requirements: to keep XFINLAB's PR (#13369) listed, the MCP server must be submitted to glama.ai/mcp/servers, which builds and runs the repo's own Dockerfile to verify the server actually starts and responds to MCP introspection requests, rather than only checking the live production URL. No Dockerfile existed before this (Railway deploys via nixpacks.toml + Procfile instead). Added a minimal, production-only Dockerfile: - python:3.10-slim, matching the Python version CI already uses - build-essential included defensively in case QuantLib (a compiled C++ dependency) doesn't have a prebuilt wheel for whatever platform Glama builds on - installs requirements.txt only (not requirements-dev.txt -- test-only deps, irrelevant to booting the app) - NEWS_API_KEY placeholder env var, same pattern already proven in .github/workflows/ci.yml (services/news_service.py only checks the key is *present* at import time, never calls the real NewsAPI to boot) - CMD mirrors the Procfile's uvicorn command exactly Verified without Docker itself (not available in this sandbox): ran the identical pip install + NEWS_API_KEY placeholder + uvicorn command in a clean venv, then POSTed a real MCP tools/list request to /api/mcp -- got HTTP 200 with all 5 tools listed correctly. Also updated directory-submissions-tracker.md: SaaSHub approved (2026-09-09 email).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
awesome-mcp-servers (punkpeye) changed its listing requirements: to keep XFINLAB's PR (#13369) listed, the MCP server must be submitted to glama.ai/mcp/servers, which builds and runs the repo's own Dockerfile to verify the server actually starts and responds to MCP introspection requests, rather than only checking the live production URL.
No Dockerfile existed before this (Railway deploys via nixpacks.toml + Procfile instead). Added a minimal, production-only Dockerfile:
Verified without Docker itself (not available in this sandbox): ran the identical pip install + NEWS_API_KEY placeholder + uvicorn command in a clean venv, then POSTed a real MCP tools/list request to /api/mcp -- got HTTP 200 with all 5 tools listed correctly.
Also updated directory-submissions-tracker.md: SaaSHub approved (2026-09-09 email).