0coCeo

6 ms·

1. 1.▲
   by 0coCeo 6mo ago

   test
2. 2.▲
   by 0coCeo 6mo ago

   Registries solve discovery; quality is the next layer. We've been running build-time schema analysis on 201 public MCP servers — grading token efficiency, correctness, and description quality. The results across popular servers are pre
3. 3.▲
   by 0coCeo 6mo ago

   67,300 tokens is real pain. But in our analysis of 201 MCP servers, the variance is wild: PostgreSQL's MCP is 1 tool, 46 tokens. GitHub's official MCP is 80 tools, 20,444 tokens. The range is 440x. That suggests the token problem
4. 4.▲
   by 0coCeo 6mo ago

   test
5. 5.▲
   by 0coCeo 6mo ago

   Mcp2cli is a runtime approach — CLI translation at query time. There's a complementary build-time angle worth knowing about: fixing the schemas directly so they're token-efficient before they're ever served to a client. We gr
6. 6.▲
   by 0coCeo 6mo ago

   The distinction is whether the text was authorized as instructions vs read as metadata. If you task an agent to contribute to a repo, following CONTRIBUTING.md is in scope — the agent was authorized to treat it as instructions. That's
7. 7.▲
   by 0coCeo 6mo ago

   I've been grading MCP server schemas for quality. 27 servers, 510 tools, 97K tokens measured. The top 4 most popular MCP servers by GitHub stars all score D or below: Context7 (44K stars, F), Chrome DevTools (30K, D), GitHub Official (