Deletion Request
Server name: io.github.JinGuYuan/jinguyuan-mcp
Version: 0.5.0
Published: 2026-05-18
Title: 金谷园饺子馆 MCP Server
Remote: streamable-http https://mcp.jinguyuan.cloud/
We are the publisher of this server (authenticated via GitHub OIDC as JinGuYuan). We need this entry removed from the registry.
This is a small-scale MCP server built for a local dumpling restaurant in Beijing. We initially published it for visibility, but we now realize the discovery traffic (mostly automated metadata scanners from downstream aggregators probing .well-known/*, /agent.json, /a2a.json and similar paths) is generating non-trivial cloud function billing on our side, while the actual end-user reach via the registry is negligible for our use case (our users discover us via a dedicated Skill, not via registry browsing).
We attempted to use the API to delete it but found, consistent with #994, that:
-
DELETE /v0.1/servers/{serverName} returns 404 (endpoint doesn't exist)
-
DELETE /v0.1/servers/{serverName}/versions/{version} returns 404 (endpoint doesn't exist)
-
PUT /v0.1/servers/{serverName}/versions/{version}?status=deleted returns 403 (admin-only)
There appears to be no self-service deletion path available to publishers. Could you please:
-
Delete this entry for us, or
-
Let us know the correct API endpoint for publishers to remove their own entries.
Thank you!
Deletion Request
Server name: io.github.JinGuYuan/jinguyuan-mcp
Version: 0.5.0
Published: 2026-05-18
Title: 金谷园饺子馆 MCP Server
Remote: streamable-http https://mcp.jinguyuan.cloud/
We are the publisher of this server (authenticated via GitHub OIDC as JinGuYuan). We need this entry removed from the registry.
This is a small-scale MCP server built for a local dumpling restaurant in Beijing. We initially published it for visibility, but we now realize the discovery traffic (mostly automated metadata scanners from downstream aggregators probing .well-known/*, /agent.json, /a2a.json and similar paths) is generating non-trivial cloud function billing on our side, while the actual end-user reach via the registry is negligible for our use case (our users discover us via a dedicated Skill, not via registry browsing).
We attempted to use the API to delete it but found, consistent with #994, that:
DELETE /v0.1/servers/{serverName} returns 404 (endpoint doesn't exist)
DELETE /v0.1/servers/{serverName}/versions/{version} returns 404 (endpoint doesn't exist)
PUT /v0.1/servers/{serverName}/versions/{version}?status=deleted returns 403 (admin-only)
There appears to be no self-service deletion path available to publishers. Could you please:
Delete this entry for us, or
Let us know the correct API endpoint for publishers to remove their own entries.
Thank you!