
Runtime Support Mcp
io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 30, 2026
Summarize runtime declarations across local manifests and CI files without returning versions,...
Overview
Local MCP server that summarizes which runtime families appear across a project's manifests, Docker files and CI configuration, returning counts only.
- What you can do
- Inspect runtime support for a project inside a configured root directory
- Summarize how many runtime families appear across local manifests, Docker files and CI configuration
- Report counts and runtime family signals to spot mixed toolchains before a release
- Withhold versions, dependency names, paths, source text and environment values from the output
- When to use it
- Useful when you want a quick, privacy-preserving overview of a project's toolchain mix, for example to check for mixed runtime families before a release, without exposing dependency details or file contents.
- Requirements
- Runs as a local stdio process installed from the npm package runtime-support-mcp (Node.js). The project to inspect must sit inside the directory named by the RUNTIME_SUPPORT_ROOT environment variable. No authentication or API keys are declared.
Installation
In SourceWeft
- Open Runtime Support Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
runtime-support-mcp
Runtime Support summarizes how many runtime families appear across local manifests, Docker files, and CI configuration. It helps identify mixed toolchains before a release.
Quick start
Use inspect_runtime_support with a project inside RUNTIME_SUPPORT_ROOT.
Limits
The output contains counts and runtime family signals only. Versions, dependency names, paths, source text, and environment values are suppressed.
Source: README.md at commit 90d3e69
Tools
0Version history
1- v1.0.0LatestSep 22, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.