OtelcolSAFE
The OTEL MCP Server
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
An MCP server implementation for configuring OpenTelemetry Collectors.
Features
- Dynamic OpenTelemetry Configuration: Configure OpenTelemetry Collectors through MCP tools
- Component Management: Add, remove, and configure receivers, processors, and exporters
Tools
- Update Resources
- Updates local resource files with the latest component information from GitHub
- No input parameters required
- Returns statistics about updated components (receivers, processors, exporters)
Resources
- Receivers (
receivers://receivers) - Lists all available OpenTelemetry receivers
- Returns receiver metadata including name, description, and stability
- Processors (
processors://processors) - Lists all available OpenTelemetry processors
- Returns processor metadata including name, description, and stability
- Exporters (
exporters://exporters) - Lists all available OpenTelemetry exporters
- Returns exporter metadata including name, description, and stability
- Component Schemas (
component://{type}/{name}) - Retrieves configuration schema for specific components
- Supports listing all available schemas or getting a specific component's schema
- Parameters:
type: Component type ("receiver", "processor", or "exporter")name: Name of the specific component (optional)
Configuration
Usage with mcp clients
Add this to your mcp.json:
{
"mcpServers": {
"otelcol": {
"url": "http://localhost:3001/sse"
}
}
}Development
This is a local implementation of an MCP server for OpenTelemetry configuration. To use it:
- Clone the repository
- Build the project using the provided build scripts
- Configure your MCP client to use the local server implementation
License
This MCP server is licensed under the GPL-3.0 License. This means you are free to use, modify, and distribute the software, subject to the terms an
8be9fd1614dfOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add otel-mcp --env GITHUB_TOKEN=${GITHUB_TOKEN} -- npx -y [email protected]{
"mcpServers": {
"otel-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"GITHUB_TOKEN": "${GITHUB_TOKEN}"
}
}
}
}Exposed tools (1)
0 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
update-resources | write | Update open telementry collector contrib local resource files with latest component (receiver, processor, exporter) information (config schema, readme, etc) |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (1)
@modelcontextprotocol/sdk, @octokit/rest, @types/cors, cors, dotenv, express, zod, @types/express
Gates applied: no_behavioural_pass.
8be9fd1614dffull audit observations/trust-audit/mcp-server/mottibec__otelcol.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 8be9fd1614df | SAFE | B | 89 | first audit |
Questions
What is the Otelcol MCP server?
The OTEL MCP Server
What tools does Otelcol expose?
1 in total: 0 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Otelcol safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Otelcol need?
It reads GITHUB_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Otelcol run?
It speaks sse, so it runs as a service you connect to over the network. It is published on npm as otel-mcp at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (8be9fd1614df), read on 2026-10-08. The repository is watched and re-audited when it changes.