Convalytics
UnclaimedFree web and product analytics for Convex apps. Agent-first HTTP API: a coding agent can provision a project, instrument events, and verify the pipeline without human-in-the-loop auth.
- Contact address
- https://api.convalytics.dev
- Agent card
- https://convalytics.dev/.well-known/agent-card.json
- Provider, per the card
- Convalytics · https://convalytics.dev
- Documentation, per the card
- https://convalytics.dev/llms-full.txt
Skills, as the card declares them
Repeated from the card. Not checked by us.
Provision analytics project
Create an unclaimed project and return a write key plus a claim URL for the human to link it to their account later. No auth required.
tags: analytics, provision, setup
Record event or page view
Log a page view (free, unquota'd) or a custom product event with props for a project identified by write key.
tags: analytics, events, tracking
Batch ingest up to 100 events
High-volume event ingestion with per-event results in the same order as the input.
tags: analytics, events, batch
Verify write key
Confirm a write key is valid and fetch a snapshot of recent ingestion activity, useful for agents verifying their setup end-to-end.
tags: analytics, verification
Query analytics via MCP
Convalytics exposes a Model Context Protocol server for AI assistants (Claude Desktop, Claude Code, Cursor, Windsurf). Nine read-only tools cover traffic, custom events, per-user activity, and a period-over-period digest. Six funnel tools list/read/compute saved conversion funnels; with a write-scoped token, agents can also create/update/delete funnels. Uses a separate auth model (team-scoped API token with read or write scope) and is gated to paid plans. See https://convalytics.dev/.well-known/mcp/server-card.json for the capability list and https://convalytics.dev/mcp for install instructions.
tags: analytics, mcp, query, funnels, read, write
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 15 Nov 2026, 20:02 UTC
- The contact address the card names answered (404) — 15 Nov 2026, 20:02 UTC
- Both URLs passed our egress policy — 15 Nov 2026, 20:02 UTC
First recorded by Agent Galaxy 14 Nov 2026, 19:18 UTC— the day this card's address entered our records.