Skip to content

fix(mcp): clarify ASCII-only requirement in server name validation error#24

Merged
echobt merged 1 commit intomasterfrom
fix/bounty-issue-1626
Jan 26, 2026
Merged

fix(mcp): clarify ASCII-only requirement in server name validation error#24
echobt merged 1 commit intomasterfrom
fix/bounty-issue-1626

Conversation

@echobt
Copy link
Contributor

@echobt echobt commented Jan 26, 2026

Summary

When users try to add an MCP server with unicode characters in the name (e.g., mcp add test-日本語), the error message was unclear about why the name was rejected.

Changes

  • Updated the error message in validate_server_name() to explicitly state that only ASCII characters are allowed
  • Changed from use letters, numbers, '-', '_' to use ASCII letters a-z/A-Z, digits 0-9, '-', or '_'

Related

Fixes PlatformNetwork/bounty-challenge#1626

Fixes bounty issue #1626

The validate_server_name function uses is_ascii_alphanumeric() but the error
message only mentioned 'letters, numbers' without specifying ASCII-only.
Users trying unicode names like 'test-日本語' received a generic error without
understanding why unicode characters were rejected.

Updated the error message to explicitly state 'ASCII letters a-z/A-Z,
digits 0-9' so users understand the limitation.
@echobt echobt merged commit fdff800 into master Jan 26, 2026
3 of 12 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.

[BUG] mcp add test-日本語 rejects unicode without explanation

2 participants