
Otel Collector Drift Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.2Updated Nov 3, 2026
Finds the removed components and renamed attributes in an OpenTelemetry Collector config before the
Overview
Local MCP server that checks an OpenTelemetry Collector config for removed components and renamed attributes before upgrading.
- What you can do
- Inspect an OpenTelemetry Collector configuration for components that have been removed.
- Detect attributes that were renamed, so they can be updated before an upgrade.
- Report drift findings from the config so an assistant can explain what needs changing.
- No tool list is published, so the exact operations are not documented.
- When to use it
- Useful when preparing an OpenTelemetry Collector upgrade and you want an assistant to flag removed components and renamed attributes in an existing config before applying changes.
- Requirements
- Runs as a local stdio process, started with npx from the npm package @readystack/otel-collector-drift-lint, so Node.js and network access for the package are needed. Desktop client only; no authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Otel Collector Drift Lint 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
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
1- v1.0.2LatestSep 19, 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.