PulseAugur
EN
LIVE 09:06:44

AI Client Test Reveals Server Communication Failures and Token Discrepancies

A recent test involving 90 trials of the Model Context Protocol (MCP) revealed that one client failed to reach the server for most of its calls, mimicking a model that performed poorly. While 87 out of 90 trials completed successfully, the failures highlighted differences in how Claude Code and Gemini CLI handled tasks and negotiated protocol revisions. Notably, one GitHub task resulted in a significant token count discrepancy between the two clients, with Claude Code receiving 1,561 tokens for a response while Gemini CLI received only 161. AI

IMPACT Highlights potential issues in AI agent communication protocols and token usage, suggesting areas for improvement in reliability and efficiency.

RANK_REASON The item details a technical experiment and its findings regarding AI client-server communication and performance, fitting the research category. [lever_c_demoted from research: ic=1 ai=1.0]

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

AI Client Test Reveals Server Communication Failures and Token Discrepancies

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Roshan Singh ·

    I put a proxy on the MCP pipe for 90 trials. Most of one client's calls never reached the server

    <p>In <a href="https://dev.to/lopster568/i-measured-what-14-mcp-servers-cost-a-context-window-claude-counts-them-64-higher-than-tiktoken-10pj">the last post</a>, on 2026-08-18, I published what 14 MCP servers cost a context window before an agent does any work, and said the next …