Skip to content

[deep-report] Add pagination wrapper for list_code_scanning_alerts MCP tool #66139

Description

@github-actions

Description

Today's GitHub MCP Structural Analysis (discussion #66120) found list_code_scanning_alerts blows past the MCP 25,000-token response limit (134,672 chars / ~33.7K tokens) even with the required state=open, severity=critical,high filters applied — the tool currently has no perPage/head_limit escape hatch, so any repo with many matching alerts fails the call outright (rated 1/5, worst of 10 tools tested). This mirrors the existing list_workflows wrapper already built in the mcpscripts CLI specifically to solve this same class of problem for Actions data.

Fix

Add a thin mcpscripts-style wrapper (or extend the existing MCP proxy config) for list_code_scanning_alerts that supports perPage/head_limit pagination, following the same pattern already proven for list_workflows.

Expected Impact

Makes code-scanning-alert queries usable on repos with many open alerts instead of failing outright — directly removes the worst-rated, highest-token-cost MCP tool call in the fleet's daily structural analysis.

Suggested Agent

General coding agent familiar with the mcpscripts wrapper pattern (.github/skills/github-mcp-server/SKILL.md).

Estimated Effort

Medium (2-4 hours)

Data Source

DeepReport Intelligence Briefing (2026-10-06, incremental cycle) — sourced from GitHub MCP Structural Analysis discussion #66120 (2026-10-06).

Generated by 🔬 Deep Report · claude · agent · 207.7 AIC · ⌖ 7.97 AIC · ⊞ 7.1K · ◷

  • expires on Oct 8, 2026, 4:50 AM UTC-08:00

Activity

  1. github-actions commented on Oct 8, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-08T12:50:47.471Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions