com.tracklution/server-side-tracking
com.tracklution/server-side-tracking
Is the com.tracklution/server-side-tracking MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Server-side conversion tracking, installed and configured by your AI coding agent.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Authentication required"}- Endpoint
- https://mcp.tracklution.com/mcp (streamable-http)
- Host
- mcp.tracklution.com
- Package
- The publisher's package npm:tracklution-mcp did not list its tools in the container: crashed on start, MCP error -32000: Connection closed.
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.tracklution.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server mcp.tracklution.com, PKCE S256, grants authorization_code, refresh_token.
Scopes read.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/tracklution/tracklution-cli
- Registry
- active, updated 2026-10-26 · registry entry
- Changes
- 2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention tracking.
- DoneThat ai.donethat/donethat · needs auth
- ai.klipy/klipy · needs auth
- ai.ohmyfin/banking-intelligence · alive
- SEOmatic ai.seomatic/seomatic · needs auth
- ThinkNEO Control Plane ai.thinkneo/control-plane · no DNS
- Timix.AI ai.timix/time-tracking · alive
- Competitor Tracking API ai.trendsapi/competitor-tracking · alive
- Competitor Tracking Trends MCP ai.trendsmcp/competitor-tracking · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-27 09:13 | needs auth | ||||
| 2026-10-17 06:13 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.