modelcontextprotocol / modelcontextprotocol/csharp-sdk
Tool Call Failed: Request timed out
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.5k
- Forks
- 814
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 4
Description
@modelcontextprotocol/inspector successfully connected to the server but tool call failed as the request timed out. It's a simple Echo tool. There is no log both in the application and the @modelcontextprotocol/inspector Log tab. The MCP server is ASP.Net Core 10 deployed and run on local k8s.
When I try from Postman, connection is successful but there is no tool found on the server.
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 by reproducing the failed Echo tool call with @modelcontextprotocol/inspector against the ASP.Net Core 10 server running in local Kubernetes, then compare it with the Postman connection attempt. Check the available server and application logs while reproducing the timeout and missing-tool behavior; done means identifying a reproducible cause or a clearly documented missing configuration or protocol detail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, kubernetes, postman
- Domain
- api, backend, devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100