---
title: "Discussion on \"How I Found a Silent API Bug in a 3,548-Star MCP Server\" | Hashnode"
description: "Discussion on \"How I Found a Silent API Bug in a 3,548-Star MCP Server\". A valid HTTP request returning HTTP 200 with no results. Here's how I found a key name mismatch breaking the query endpoint in CodeGraphContext."
url: "https://hashnode.com/posts/how-i-found-a-silent-api-bug-in-a-3-548-star-mcp-server/6a420d4285d664dd0a012f6c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How I Found a Silent API Bug in a 3,548-Star MCP Server](https://eshaanaghashnodedev.hashnode.dev/how-i-found-a-silent-api-bug-in-a-3-548-star-mcp-server?utm_source=hashnode&utm_medium=feed)

A valid HTTP request returning HTTP 200 with no results. Here's how I found a key name mismatch breaking the query endpoint in CodeGraphContext.

Jun 29 · 6 min read · eshaanaghashnodedev.hashnode.dev  
Read the article

-   [#opensource](https://hashnode.com/tag/opensource)
-   [#python](https://hashnode.com/tag/python)
-   [#mcp](https://hashnode.com/tag/mcp)
-   [#gssoc2026](https://hashnode.com/tag/gssoc2026)
-   [#build-in-public](https://hashnode.com/tag/build-in-public)
-   [#100daysofcode](https://hashnode.com/tag/100daysofcode)
-   [#web-development](https://hashnode.com/tag/web-development)

## Written by

[Eshaan Agrawal](https://hashnode.com/@eshaanag)

@eshaanag · Bangalore, India

  
[View profile](https://hashnode.com/@eshaanag)

Open source contributor. Building in AI security and developer tooling.

## Responses 1

Markdown supported · ⌘↵ to post

[Opportunity Biz](https://hashnode.com/@opptybiz)

[Jun 29](https://hashnode.com/posts/how-i-found-a-silent-api-bug-in-a-3-548-star-mcp-server/6a420d4285d664dd0a012f6c/comment/6a426edadb3f93e8e454f341)

The interesting part isn't the bug — it's the failure signature. HTTP 200 + error-in-body is the worst possible shape for a defect like this because it looks like user error, not a routing mismatch. You'd blame your Cypher query, not the key name being passed between layers.

The structural fix that prevents the whole class: typed input at the tool handler boundary. execute\_cypher\_query should accept a validated schema (Pydantic, dataclass, whatever), not raw args.get('cypher\_query'). Then any caller passing the wrong key fails loudly at the call site instead of quietly downstream. Most MCP servers skip this because the happy path gets tested — the wrong-key path doesn't.
