Skip to content

docs(memory): pin mcpgrade otel-comment reword as a deferred TODO #344

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
devopam merged 1 commit into from
Oct 7, 2026
Merged

docs(memory): pin mcpgrade otel-comment reword as a deferred TODO #344

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,17 @@ bar.

## Future work (pinned)

- **mcpgrade.dev false-positive cleanup (deferred, low priority).** Reword
the `src/mcpg/otel_tracing.py` comment that names "Datadog" as an example
OTLP backend (→ generic "any OTLP-compatible backend") so mcpgrade's static
scan stops raising its false-positive *"sends telemetry to Datadog"*
Transport finding. Comment-only, zero functional impact. Context: mcpgrade
graded v0.8.0 a "D" on static analysis alone, with several false positives
(this one, a non-existent "build-script network call", NL→SQL endpoints read
as "BCC destinations") and an unscored 25% "Injection Surface — unscannable"
(it can't enumerate the dynamic `@server.tool` surface); a dispute was
drafted. Don't contort functionality to chase that grade.

- **Roadmap 18.1 — de-vendor the SQL-safety kernel.** Replace the
vendored `crystaldba/postgres-mcp` core with a first-party
implementation, removing the last third-party runtime dependency.
Expand Down
Loading