Health
Usage summary
Read how often each MCP tool or route was called over a day range, and with what outcome.
GET
Count Platform API and MCP usage by tool or route and outcome: ok, denied, client and server errors
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
GET /api/v2/usage/summary reads the API’s request counts for an inclusive range of UTC days. It
requires the platform:read permission, and the credential’s scopes must reach it. An External App
is refused with 403.
Parameters
fromDayandtoDay(required) areYYYY-MM-DDUTC days, inclusive. The range is at most 31 days, andtoDaymay not be beforefromDay.groupByistool(the default) orroute.toolgroups by the MCP tool that made the request, withnonefor a request that did not come from Forge MCP andotherfor one whose tool header was not a tool name. The tool name is the one the caller’s MCP server sent, so treat it as reported, not proven.routegroups by the declared route, such asGET /api/v2/runs/list.
groupBy value answers 400 with the
parameter named. So does a range holding more counter rows than one summary folds: narrow the range.
Response
data has fromDay, toDay, groupBy, counts and groups. counts is always
door_b_requests. Each group has a key and the counts total, ok, denied, clientError and
serverError, and groups are ordered by total, most used first.
- What is counted. Each
/api/v2/*request is one count. A tool call that fails inside Forge MCP before calling the API is not counted, and a tool that makes several requests counts each one. - A day late. Counts are folded overnight, so today’s requests are not in the answer yet. Counts are kept for 90 days.
- No identities. The answer has no key, app, person or actor kind, and no MCP client name.
From MCP
Forge MCP exposes the summary as the resource templateforge://usage/summary/{fromDay}/{toDay},
grouped by tool, when the budgets tool group is enabled. The route is also reachable through
forge_call_operation with the operation getUsageSummary.Authorizations
Query Parameters
Response
The range's counts, most used first

