Telemetry MCP server

by arnavranjan005·io.github.arnavranjan005/mcp-telemetry-server·v0.1.3·2 stars

No reviews yet

Streams live progress from mcp-telemetry-sdk-instrumented tools to any connected MCP client.

A92/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A92/100

full report

Adoption

Growing

2 stars42 downloads/wk

Reviews

Write one

Nobody has reviewed Telemetry yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Telemetry tools (3)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

telemetry_job_status
Get the full status of a specific job — all steps, cost, and any failure reason.
telemetry_jobs
List all active and recently completed jobs across all connected MCP servers.
telemetry_subscribe
Watch live job events as they happen — blocks and streams inline progress until the job (or, with no jobId, the next job) finishes, or until timeoutMs elapses.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings

Code scan12 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 3 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Telemetry compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 92/100; higher than 95% of 48,255 servers
Tools: 3; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 2; more than 75% of 28,688 servers
Downloads a week: 42; more than 34% of 12,191 servers with a package

What its tools let an agent do: 3 read

Install Telemetry in Claude Code, Cursor or VS Code

Runs npx -y mcp-telemetry-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-telemetry-server -- npx -y mcp-telemetry-server

Add to Cursor

What the publisher says

From the Telemetry repository's README, as published. We do not edit it. Read it on GitHub

mcp-telemetry

Socket.IO for AI agents. Instrument any MCP server's tool calls with a few lines, and any MCP client watching (Claude Code, Cursor, or your own tooling) gets live, structured progress — no polling, no context-flooding tool calls.

Your MCP server                    mcp-telemetry server         Agent
─────────────────                  ────────────────────         ─────
mcp-telemetry-sdk
  job.stepStart('build')
       │
       │ local socket (queued, persistent connection)
       ▼
  collector receives event
  store updates job state
       │
       │ MCP notifications/progress
       ▼
                                    telemetry_subscribe tool     Claude Code
                                    pushes event to agent   →   sees inline
                                                                 live status

Why this exists

MCP tool calls are synchronous: an agent calls a tool, waits, gets a result. For anything long-running, that leaves two bad options — block the whole call with no visibility, or have the agent poll a status tool in a loop (which floods the conversation with repeated tool calls and burns context for no new information).

MCP does have one legitimate way for a server to push updates mid-call: notifications/progress, keyed to a progressToken on the in-flight request. But every MCP server author ends up re-implementing the same plumbing — extracting the token, wiring a timer, tailing output, cleaning up on completion. mcp-telemetry is that plumbing, factored out once, plus a companion server so a job started in one session can be watched from a completely different one.

How it fits together

Two packages, one job each:

These two packages are architecturally independent — the SDK never calls any MCP tool, and the server never imports your tool's code. They only ever meet at a local socket, so a producer with a broken connection can't take down anything, and a collector that's overwhelmed can't block your tool call.

Quickstart

1. Instrument your MCP server (mcp-telemetry-sdk)

npm install mcp-telemetry-sdk

import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { MCPTelemetry } from "mcp-telemetry-sdk";

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Telemetry: common questions

Is Telemetry MCP server safe?: Yes, by our scan: it is graded A (92/100). Read the Telemetry safety report
How do I install Telemetry?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Telemetry need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Telemetry maintained?: The last commit was 42 days ago (2026-09-23). The latest release is v0.1.3.
What can I use instead of Telemetry?: Servers from other publishers that do the same job: Jitsu MCP server.
How does Telemetry compare with other MCP servers?: safety score 92/100 (higher than 95% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Telemetry

Same job from other publishers: the closest match first, then the best rated.

Jitsu
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
not reviewed
Established
A