modelcontextprotocol / modelcontextprotocol/registry

Validate provided repositories are publicly reachable (PGA golf server's github link is wrong)

Open
#395 8 comments 0 reactions 1 assignee View on GitHub

@Avish34 is already working on this.

Since Sep 10, 2025.

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

Description

I am not sure if this is the right way to report an issue with a specific server. I reviewed https://github.com/modelcontextprotocol/registry/blob/main/docs/guides/administration/moderation-guidelines.md and it does not explain how to report a problem with a server.

The com.pga/pga-golf entry has an invalid repository URL. It does not resolve - https://github.com/pgahq/mcp-pga-com.

Here's the full entry for what it's worth:

        {
            "$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
            "name": "com.pga/pga-golf",
            "description": "PGA's official MCP Server for all things golf-related. Find a coach, play golf, improve your game.",
            "status": "active",
            "repository": {
                "url": "https://github.com/pgahq/mcp-pga-com",
                "source": "github",
                "id": "1004564607"
            },
            "version": "latest",
            "remotes": [
                {
                    "type": "streamable-http",
                    "url": "https://mcp.pga.com/mcp"
                }
            ],
            "_meta": {
                "io.modelcontextprotocol.registry/official": {
                    "id": "0a62b274-571c-45e9-8b04-5a122e6cc4f5",
                    "published_at": "2025-09-09T15:22:49.722230578Z",
                    "updated_at": "2025-09-09T15:22:49.722230578Z",
                    "is_latest": true
                }
            }
        },

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.