expose Server URL

[maorfr]

Motivation and Context

the URL field is documented but does not exist.

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[tadasant]

@maorfr there is no Server.url field - were you looking at something else?

I think you are looking for Repository.url.

Or maybe you would advocate for addition of some sort of learn_more_url or marketing_url on Server. Which is a reasonable discussion to have, however that is not in the documentation yet, so we'd need to start there. Do you have a use case?

[maorfr]

examples of existing url:

• registry/internal/docs/swagger.yaml

  Line 222 in 6b22cf0

  url:

• registry/README.md

  Line 120 in 6b22cf0

  "url": "https://example.com/mcp",

[tadasant]

Thanks for flagging - the spec and examples in docs are the source of truth, so we should remove those errant examples unless we agree to add the field to the source of truth.

[maorfr]

i think a server url makes a lot of sense, to answer the question -
where can you find a running instance of this MCP server? (think of a registry running within an org)

[tadasant]

where can you find a running instance of this MCP server?

This would be the Remote.url field.

The use case that makes sense to me would be a "landing page URL" like https://zapier.com/mcp.

We should discuss what the right naming would be for this, as url is clearly too ambiguous (that is evident even from just this conversation). Some options:

• landing_page_url
• marketing_url
• learn_more_url
• more_information
• canonical_url

And maybe we would require this URL to match the reverse DNS verification in name.

[jonathanhefner]

We should discuss what the right naming would be for this, as url is clearly too ambiguous (that is evident even from just this conversation). Some options:

Another option is homepage. That's what NPM (example) and RubyGems (example) use, at least when displayed.

And maybe we would require this URL to match the reverse DNS verification in name.

This might be too onerous a requirement. I can imagine someone wanting to switch to a new domain after the fact. (Gotta grab that new .ai TLD! 🔥)