API quickstart remote MCP example uses a retired endpoint that returns 404
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What is the type of issue?
Example code is not working
What is the issue?
Problem
The remote MCP quickstart example points to https://dmcp-server.deno.dev/mcp, which no longer serves its deployment. This prevents the documented “Roll 2d4+1” example from working.
The same URL appears across the language examples.
Reproduction
curl -i https://dmcp-server.deno.dev/mcp
Verified September 10, 2026:
HTTP/2 404
404: Not Found (DEPLOYMENT_NOT_FOUND)
The requested deployment does not exist. Deno Deploy Classic was sunset on July 20, 2026 and no longer serves deployments. See https://deno.com/deploy for the new Deno Deploy.
An MCP initialize POST request also returns the same 404.
Expected behavior
The quickstart should use a working MCP endpoint so users can successfully run the example.
Suggested fix
- Point all language examples to a maintained, publicly accessible MCP endpoint.
- Update the server description and prompt if the replacement endpoint provides different tools.
- Verify the example end to end through the Responses API.
Where did you find it?
The same URL appears across the language examples.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked remote MCP quickstart and search the language examples for dmcp-server.deno.dev/mcp. Test a maintained replacement with the curl and MCP initialize requests described in the issue, then verify the example end to end through the Responses API. Done means every language example uses a working endpoint and its server description and prompt match the replacement tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100