Track MCP Server

by katrinalaszlo Your server? Claim it

answering

Track is answering right now. Last checked 11 min ago.

Read which AI agents call your API, which paths convert, and which journeys pay.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

229 ms

Response time

average over 24h

authentication required

Access

streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add track --transport http https://alg.katrinalaszlo.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://alg.katrinalaszlo.com/mcp

~/.codex/config.toml

[mcp_servers.track]
url = "https://alg.katrinalaszlo.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "track": {
      "url": "https://alg.katrinalaszlo.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "track": {
      "type": "http",
      "url": "https://alg.katrinalaszlo.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://alg.katrinalaszlo.com/mcp	streamable-http	needs auth	250 ms	11 min ago

Alternatives to Track

same job, measured the same way

Pickrate

by pickrate

Agent analytics: which AI agents read your site, drove signups, and pick you over competitors.

4 tools answering

Chief

by chiefisnext

Many agents. One Chief. Plan, track, and manage all your AI agents in one place.

answering

repomap

by sylphxai

A map of your codebase for AI agents: code graph, search, call paths and change impact. No API key.

234 installs/wk local only

Agent Trace Check

by openkrill

Read a tool-call log from an AI agent run and see which calls failed, looped or were slow.

4 tools answering

Liquid

by ertad-family

Connect your AI agent to anything — APIs, databases, and agents; read and write, auto-discovered.

100 installs/wk local only

Agentaddress

by zkarimi22

Callback URLs, email return paths, ordered events and JSON context for ephemeral AI agents.

8 tools answering

Paigy

by paigy-ai

Lets your AI agents call you when they need a decision, and hear your answer.

389 installs/wk local only

Server Side Tracking

by tracklution

Server-side conversion tracking, installed and configured by your AI coding agent.

answering

Track — questions

Answers built from our own checks of this server.

Why is there no tool list for Track?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Track working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 229 ms. The bar chart above shows every period we have measured.

Is Track still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Track?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Track need an API key?

Yes. Every time we knock, Track answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Track?

It answers our handshake in 229 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.