USusenotra
GEO

Get MCP server analytics

Changed on

Usage of your own MCP server, as reported by the @usenotra/geo SDK: request and error totals against the previous window, per-tool latency and errors, clients, models, intents, recent failures and tools that were never called. Captured arguments, responses and end-user IDs are not returned.

get/v1/projects/{projectId}/geo/traffic/mcp

Request

Path parameters

projectIdstring required
Example:b1f2c3d4-0000-4000-8000-000000000000

Query parameters

daysinteger

Rolling window size in days. Ignored when from/to are set.

fromstring
Example:2026-01-31
tostring
Example:2026-01-31

Response

MCP analytics fetched successfully

configuredboolean required

False when the traffic backend is not configured for this deployment; the payload is then empty rather than an error.

Changes