Skip to content

fix(mcp): report server identity as sudo-proxy, not rmcp - #51

Merged
cuihtlauac merged 1 commit into
mainfrom
fix-serverinfo-name
Sep 22, 2026
Merged

cuihtlauac merged 1 commit into
mainfrom
fix-serverinfo-name

Conversation

@cuihtlauac

Copy link
Copy Markdown
Member

get_info() left server_info to default, which rmcp fills from its own build env (Implementation::from_build_env), so initialize advertised rmcp 0.15.0. Some MCP directory sites display that name. Set server_info explicitly to this crate's name + env!("CARGO_PKG_VERSION").

Verified locally: an initialize probe now reports serverInfo: sudo-proxy 1.1.0. Introspection test passes; no test hard-codes the old name.

No version bump / no release — rides the next release.

🤖 Generated with Claude Code

get_info() left server_info to default, which rmcp fills from its own build
env (Implementation::from_build_env → CARGO_CRATE_NAME/CARGO_PKG_VERSION of
the rmcp crate), so initialize advertised "rmcp 0.15.0". Some MCP directory
sites display that name. Set server_info explicitly to this crate's name and
version (env!("CARGO_PKG_VERSION")).

Verified: an initialize probe now reports serverInfo "sudo-proxy 1.1.0".

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cuihtlauac
cuihtlauac merged commit 96409a9 into main Sep 22, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant