Tool Call Failed: Request timed out

Open
#1,785 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp, kubernetes, postman
Domain
api, backend, devops, networking

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.

Description

bug help wanted needs repro P3

@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.

Dominant language
C#
Stars
4.5k
Forks
814
Avg merge
9d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/csharp-sdk

All issues in modelcontextprotocol/csharp-sdk

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.