You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: GitHub MCP Structural Analysis (discussion #57431) confirmed across 5 measured days (2026-08-25 to 2026-08-31) that every non-wrapper GitHub MCP tool response carries a fixed ~2.2-2.8k-character base64 icon block in _meta.serverInfo, which often outweighs the actual payload for small lookups (e.g. get_label: ~30 tokens of real data vs. ~630 tokens total; search_users, list_discussions similarly dominated by this fixed overhead). Wrapper-style tools that omit this field (e.g. the list_workflows mcpscripts wrapper, 150 tokens, 5/5 rated) are consistently more token-efficient than the equivalent raw GitHub MCP tool call.
Expected Impact: Reducing or stripping this fixed per-call overhead (or preferring/adding more mcpscripts-style wrappers for small, frequently-called GitHub MCP tools like get_label, search_users, list_discussions) would cut token cost on every one of these calls repo-wide, compounding across the many agentic workflows that call the GitHub MCP server directly.
Suggested Agent: New investigation (MCP tooling / mcpscripts)
Estimated Effort: Medium (1-4 hours)
Data Source: DeepReport analysis 2026-08-31, sourced from discussion #57431 (GitHub MCP Structural Analysis)
Warning
Firewall blocked 2 domains
The following domains were blocked by the firewall during workflow execution:
api.anthropic.com
api.github.com
[!TIP] api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:
tools:
github:
mode: gh-proxy
See GitHub Tools for more information on gh-proxy mode.
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
Description: GitHub MCP Structural Analysis (discussion #57431) confirmed across 5 measured days (2026-08-25 to 2026-08-31) that every non-wrapper GitHub MCP tool response carries a fixed ~2.2-2.8k-character base64 icon block in
_meta.serverInfo, which often outweighs the actual payload for small lookups (e.g.get_label: ~30 tokens of real data vs. ~630 tokens total;search_users,list_discussionssimilarly dominated by this fixed overhead). Wrapper-style tools that omit this field (e.g. thelist_workflowsmcpscripts wrapper, 150 tokens, 5/5 rated) are consistently more token-efficient than the equivalent raw GitHub MCP tool call.Expected Impact: Reducing or stripping this fixed per-call overhead (or preferring/adding more mcpscripts-style wrappers for small, frequently-called GitHub MCP tools like
get_label,search_users,list_discussions) would cut token cost on every one of these calls repo-wide, compounding across the many agentic workflows that call the GitHub MCP server directly.Suggested Agent: New investigation (MCP tooling / mcpscripts)
Estimated Effort: Medium (1-4 hours)
Data Source: DeepReport analysis 2026-08-31, sourced from discussion #57431 (GitHub MCP Structural Analysis)
Warning
Firewall blocked 2 domains
The following domains were blocked by the firewall during workflow execution:
api.anthropic.comapi.github.com[!TIP]
api.github.comis blocked because GitHub API access uses the built-in GitHub tools by default. Instead of addingapi.github.comtonetwork.allowed, usetools.github.mode: gh-proxyfor direct pre-authenticated GitHub CLI access without requiring network access toapi.github.com:See GitHub Tools for more information on
gh-proxymode.To allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.