modelcontextprotocol / modelcontextprotocol/registry

GitLab repository URLs with nested groups/subgroups are rejected by validator

Open Beginner friendly
#1,359 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
7.3k
Forks
994
Avg merge
4d 12h
Merged PRs (30d)
19

Description

The gitlabURLRegex in internal/validators/utils.go only allows two path segments (owner/repo), rejecting valid GitLab URLs with subgroups.

Current:
^https?://(www\.)?gitlab\.com/[\w.-]+/[\w.-]+/?$
Fix:
^https?://(www\.)?gitlab\.com/[\w./-]+/[\w.-]+/?$

Example: https://gitlab.com/myorg/team/subgroup/my-mcp-server → invalid repository URL.

GitLab subgroups are a standard feature used in GitLab Enterprise. The current regex is preventing self-hosted registries from publishing servers whose source lives in a GitLab group hierarchy.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in internal/validators/utils.go and inspect gitlabURLRegex. Update validation so GitLab URLs containing nested groups and subgroups are accepted while the existing repository URL shape remains valid; verify the provided nested URL is no longer rejected.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
84/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.