Remove namespace match validation for websiteUrl and remote URL (mode…

…lcontextprotocol#769)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->

Resolve modelcontextprotocol#768 and
modelcontextprotocol#494.

Require HTTPS for remote URLs. Currently all remote URLs on the MCP
Registry are HTTPS.
Also fix a test bug when running on Windows (bad temp path).

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

Unit tests.
Published a server.json locally with a website URL not matching the
server name.

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [x] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [x] My code follows the repository's style guidelines
- [x] New and existing tests pass locally
- [x] I have added appropriate error handling
- [ ] ~I have added or updated documentation as needed~ N/A

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->

docs(community): Add Awesome MCP Registry project link (modelcontextp…

…rotocol#734)

<!-- Provide a brief summary of your changes -->

Added **Awesome MCP Registry** to the Featured Projects list — a
community project that extends the MCP Registry with **API-based MCP
execution**, **private deployment**, and **secure sandbox isolation**.

---

## Motivation and Context

Most existing MCP Registry projects primarily serve as directories —
they list available MCP servers but do not support actual invocation or
interaction.
**Awesome MCP Registry** bridges this gap by enabling **direct API
execution of MCPs** within a **sandboxed** and **self-hostable**
environment.
This allows developers and enterprises to safely run, test, and
integrate MCP servers in **private infrastructure** while maintaining
full control over data and execution.

---

## How Has This Been Tested?

The project has been validated in private and local deployments using
various MCP servers.
API execution, sandbox isolation, and registry synchronization have been
tested successfully in both development and production-like
environments.

---

## Breaking Changes

No breaking changes — documentation update only.

---

## Types of changes

* [x] Documentation update

---

## Checklist

* [x] I have read the [[MCP
Documentation](https://modelcontextprotocol.io/)](https://modelcontextprotocol.io)
* [x] The project description follows the repository’s style guidelines
* [x] The project link and summary are verified and accurate
* [x] The addition aligns with the MCP community contribution standards

---

## Additional context

This addition highlights a project that **extends the traditional MCP
Registry model** by introducing **execution capabilities**, making it a
practical foundation for **secure, private, and automated MCP
workflows**.

---------

Co-authored-by: Radoslav Dimitrov <radoslav@stacklok.com>

Fix the image tag to strip the v prefix (modelcontextprotocol#726)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
We forgot to strip the v prefix when we made the switch to ko so this PR
fixes it.

Once we merge it we'll cut a new release so we can apply this change 👍 

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] 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
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] 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
<!-- Add any other context, implementation notes, or design decisions
-->

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>

Implement --token and MCP_GITHUB_TOKEN login support (modelcontextpro…

…tocol#705)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The following PR implements the missing support for logging in via
`--token` or `MCP_GITHUB_TOKEN`

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] 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
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] 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
<!-- Add any other context, implementation notes, or design decisions
-->
Fixes: modelcontextprotocol#698

---------

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>

Clarify the docs around _meta publisher extensions (modelcontextproto…

…col#695)

build(deps): bump github.com/pulumi/pulumi-kubernetes/sdk/v4 from 4.1…

…8.2 to 4.23.0 in /deploy (modelcontextprotocol#701)

Bumps
[github.com/pulumi/pulumi-kubernetes/sdk/v4](https://github.com/pulumi/pulumi-kubernetes)
from 4.18.2 to 4.23.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pulumi/pulumi-kubernetes/releases">github.com/pulumi/pulumi-kubernetes/sdk/v4's
releases</a>.</em></p>
<blockquote>
<h2>v4.23.0</h2>
<h3>Changed</h3>
<ul>
<li>Updated Kubernetes schemas and libraries to v1.33.0. (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3619">pulumi/pulumi-kubernetes#3619</a>)</li>
</ul>
<h2>v4.22.2</h2>
<h3>Fixed</h3>
<ul>
<li>Fix panic when <code>valueYamlFiles</code> field in
<code>helm.v3.Release</code> resources are nil (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3601">pulumi/pulumi-kubernetes#3601</a>)</li>
</ul>
<h2>v4.22.1</h2>
<h3>Fixed</h3>
<ul>
<li>Fix race condition in Deleted condition (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3550">pulumi/pulumi-kubernetes#3550</a>)</li>
</ul>
<h2>v4.22.0</h2>
<h3>Changed</h3>
<ul>
<li>Update Pulumi dependency to v3.153.1 (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3534">pulumi/pulumi-kubernetes#3534</a>)</li>
<li>Update ESC dependency to v0.13.0 (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3551">pulumi/pulumi-kubernetes#3551</a>)</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fix race condition in Deleted condition. (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3550">pulumi/pulumi-kubernetes#3550</a>)</li>
</ul>
<h2>v4.21.1</h2>
<h3>Added</h3>
<ul>
<li>Windows executable releases are now signed. (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3455">pulumi/pulumi-kubernetes#3455</a>)</li>
</ul>
<h2>v4.21.0</h2>
<h3>Changed</h3>
<ul>
<li>Upgrade <code>pulumi-java</code> to version <code>v1.0.0</code> (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3436">pulumi/pulumi-kubernetes#3436</a>)</li>
</ul>
<h2>v4.20.0</h2>
<h3>Added</h3>
<ul>
<li>Added support for autonaming configuration specified by the engine.
(<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3363">pulumi/pulumi-kubernetes#3363</a>)</li>
</ul>
<h2>v4.19.0</h2>
<h3>Changed</h3>
<ul>
<li>Updated Kubernetes schemas and libraries to v1.32.0. (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3343">pulumi/pulumi-kubernetes#3343</a>)</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/pulumi/pulumi-kubernetes/blob/master/CHANGELOG.md">github.com/pulumi/pulumi-kubernetes/sdk/v4's
changelog</a>.</em></p>
<blockquote>
<h2>4.23.0 (May 1, 2025)</h2>
<h3>Changed</h3>
<ul>
<li>Updated Kubernetes schemas and libraries to v1.33.0. (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3619">pulumi/pulumi-kubernetes#3619</a>)</li>
</ul>
<h2>4.22.2 (April 15, 2025)</h2>
<h3>Fixed</h3>
<ul>
<li>Fix panic when <code>valueYamlFiles</code> field in
<code>helm.v3.Release</code> resources are nil (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3601">pulumi/pulumi-kubernetes#3601</a>)</li>
</ul>
<h2>4.22.1 (March 14, 2025)</h2>
<h3>Fixed</h3>
<ul>
<li>Fix race condition in Deleted condition (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3550">pulumi/pulumi-kubernetes#3550</a>)</li>
</ul>
<h2>4.22.0 (March 13, 2025)</h2>
<h3>Changed</h3>
<ul>
<li>Update Pulumi dependency to v3.153.1 (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3534">pulumi/pulumi-kubernetes#3534</a>)</li>
<li>Update ESC dependency to v0.13.0 (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3551">pulumi/pulumi-kubernetes#3551</a>)</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fix race condition in Deleted condition. (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3550">pulumi/pulumi-kubernetes#3550</a>)</li>
</ul>
<h2>4.21.1 (January 27, 2025)</h2>
<h3>Added</h3>
<ul>
<li>Windows executable releases are now signed. (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3455">pulumi/pulumi-kubernetes#3455</a>)</li>
</ul>
<h2>4.21.0 (January 16, 2025)</h2>
<h3>Changed</h3>
<ul>
<li>Upgrade <code>pulumi-java</code> to version <code>v1.0.0</code> (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/pull/3436">pulumi/pulumi-kubernetes#3436</a>)</li>
</ul>
<h2>4.20.0 (January 14, 2025)</h2>
<h3>Added</h3>
<ul>
<li>Added support for autonaming configuration specified by the engine.
(<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3363">pulumi/pulumi-kubernetes#3363</a>)</li>
</ul>
<h2>4.19.0 (December 11, 2024)</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/7bad5eb56fd9913ba010634287a6aaca4dee551a"><code>7bad5eb</code></a>
Prepare for v4.23.0 release (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3625">#3625</a>)</li>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/681b76759f59ba33d787faafd4691a69f5c68f88"><code>681b767</code></a>
Update first-party Pulumi dependencies (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3610">#3610</a>)</li>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/2a39f29265772662bd80dfb26ac4f9260343a18f"><code>2a39f29</code></a>
Upgrade Kubernetes schema and client libraries to v1.33 (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3619">#3619</a>)</li>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/771d0b13ea4dc72c2b6029646640469d73a621e6"><code>771d0b1</code></a>
Bump golangci-lint to 1.64.8 (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3622">#3622</a>)</li>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/9bcb460455c8dfe60b3aa8c1f2d7a9331ff47ec5"><code>9bcb460</code></a>
Move location of YAML tests (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3616">#3616</a>)</li>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/d584e9046202ae3c127899f053ad519ded5e0c1b"><code>d584e90</code></a>
Bump node to 18 and regenerate SDK (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3613">#3613</a>)</li>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/84e2d286baf27ad1719ed6cbe9237decd143f25f"><code>84e2d28</code></a>
comments to explain why we have the aws and gcp options set</li>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/810bcc49e4a28500cb15578ed70eb21c58ce6ae6"><code>810bcc4</code></a>
add .ci-mgmt.yaml</li>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/33cb1e1be989b08cfd1e5bfe106e6ae706a84a2b"><code>33cb1e1</code></a>
Update first-party Pulumi dependencies (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3596">#3596</a>)</li>
<li><a
href="https://github.com/pulumi/pulumi-kubernetes/commit/69bd1474c1aba15c46012ec40af61791f9393379"><code>69bd147</code></a>
Update GitHub Actions workflows. (<a
href="https://redirect.github.com/pulumi/pulumi-kubernetes/issues/3592">#3592</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/pulumi/pulumi-kubernetes/compare/v4.18.2...v4.23.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/pulumi/pulumi-kubernetes/sdk/v4&package-manager=go_modules&previous-version=4.18.2&new-version=4.23.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Make mcpb package version optional and fix schema validation (modelco…

…ntextprotocol#686)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The following PR:
* Makes mcpb package version property optional
* Bumps the schema and reflects that in the code
* Makes sure the publisher tests are being covered by doing `make check`

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] 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
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] 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
<!-- Add any other context, implementation notes, or design decisions
-->

---------

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>

Pass ldflags to the Dockerfile (modelcontextprotocol#681)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The following fixes an issue where the ldflags were not passed to the
Dockerfile, so the binary cannot populate its version-related variables
accordingly

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] 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
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] 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
<!-- Add any other context, implementation notes, or design decisions
-->

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>

Introduce a /version API (modelcontextprotocol#667)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The following PR introduces a `/version` API that serves the build
details along with the version of the API server being served. The
`/version` endpoint allows users to programmatically query which exact
version of the registry is running in production for debugging.
~~auditing, and compatibility checks~~.

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] 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
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] 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
<!-- Add any other context, implementation notes, or design decisions
-->

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>

Add the rest of the tag descriptions (modelcontextprotocol#661)

<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] 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
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] 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
<!-- Add any other context, implementation notes, or design decisions
-->

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>