---
title: "Mcp Usage"
method: GET
path: "/api/admin/mcp-usage"
tags: ["Admin"]
---

# Mcp Usage

`GET /api/admin/mcp-usage`

## Request

- Base URL: `https://pegarex.com.br` (the document declares no server; this is the origin it was published from)
- URL: `https://pegarex.com.br/api/admin/mcp-usage`
- Auth: HTTP bearer

Use of the public MCP server (/api/mcp), from mcp_calls (migration 049):
totals, calls per day, per tool, per client and user-agent, and the latest
calls. Tool errors are read from the reply, because MCP answers a failed tool
with HTTP 200; rate-limited requests are the 429s. What went wrong is split
three ways (see _MCP_FAIL and below), because one "errors" number counted
every crawler that used the protocol wrong as a failure of ours.

## Query parameters

- `days` integer

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/pegarex/apis/pegarex-api.md) · [All operations](https://skmtc.dev/pegarex/apis/pegarex-api/llms.txt) · [OpenAPI document](https://skmtc.dev/pegarex/apis/pegarex-api/revisions/8c789c9bd72d?raw)