Repository navigation
Keep catalogue resource identifiers consistent with MCP names #440
Description
🤖 Generated by the Agentic Engineer
Problem
A valid MCP server key containing an underscore passes the MCP configuration contract but cannot match the same name in the catalogue. The catalogue parser recognizes only lowercase alphanumeric/hyphen resource tokens, which is narrower than the supported named-server map.
Proposed direction
Define and apply a faithful catalogue representation for supported resource identifiers. Accept representable MCP names and fail explicitly for names that cannot be represented, rather than silently dropping tokens.
Acceptance criteria
- Matching underscore, dotted and Unicode server identifiers validate when faithfully represented.
- A genuinely missing or extra catalogue resource fails.
- Delimiter-bearing or ambiguous identifiers receive an explicit refusal.
- The existing canonical resource catalogue remains unchanged and valid.
Size: S. Part of #38.
Activity
chore: agent-claim #440 nonce=2f2cce0e0702211cfee4fcb5b0b5006d
devantler commentedon Oct 4, 2026
Implemented by #443, now merged. Read back on main 2ca8f56: all 24 package-discovery regressions and complete package validation pass. The corresponding negative fixture refuses and valid consumer resources retain their identities and selections.