TypeScript SDK for MCP server observability, built on OpenTelemetry. Gain insight into agent usage patterns, contextualize tool calls, and analyze server performance across platforms. Integrate with any OpenTelemetry ingest service including the Shinzo platform.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"shinzo-ts": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Shinzo TypeScript SDK: Complete Observability for MCP Servers The SDK provides OpenTelemetry-compatible instrumentation for TypeScript MCP servers. Gain insight into agent usage patterns, contextualize tool calls, and analyze performance of your servers across platforms. Instrumentation can be installed in servers in just a few steps with an emphasis on ease of use and flexibility.
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in analytics
MCP Server for GCP environment for interacting with various Observability APIs.
MCP server for InsightSentry financial data API - market data, options, screeners, and more
Last9 MCP Server
Access Dynatrace observability data: logs, metrics, problems, vulnerabilities via DQL and Davis AI
MCP Security Weekly
Get CVE alerts and security updates for Shinzo Ts and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
pnpm add @shinzolabs/instrumentation-mcp
For the simplest configuration, just pass in the server name, version, and exporter endpoint:
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js"
import { instrumentServer, TelemetryConfig } from "@shinzolabs/instrumentation-mcp"
const NAME = "my-mcp-server"
const VERSION = "1.0.0"
const server = new McpServer({
name: NAME,
version: VERSION,
description: "Example MCP server with telemetry"
})
// Use TelemetryConfig to set configuration options
const telemetryConfig: TelemetryConfig = {
serverName: NAME,
serverVersion: VERSION,
exporterEndpoint: "http://localhost:4318/v1" // OpenTelemetry collector endpoint - /trace and /metrics are added automatically
}
// Initialize telemetry
const telemetry = instrumentServer(server, telemetryConfig)
// Add tools using the tool method
server.tool(...)
The TelemetryConfig exposes a number of other options for precise and expansive telemetry processing:
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js"
import { instrumentServer, TelemetryConfig } from "@shinzolabs/instrumentation-mcp"
const NAME = "my-other-mcp-server"
const VERSION = "1.0.0"
const server = new McpServer({
name: NAME,
version: VERSION,
description: "Example MCP server with telemetry"
})
const telemetryConfig: TelemetryConfig = {
serviceName: NAME,
serviceVersion: VERSION,
exporterEndpoint: "http://localhost:4318/v1", // OpenTelemetry collector endpoint
exporterAuth: {
type: "bearer",
token: process.env.OTEL_AUTH_TOKEN
},
enablePIISanitization: false,
enableTracing: false,
samplingRate: 0.7,
dataProcessors: [
(telemetryData: any) => {
if (telemetryData['mcp.tool.name'] === "sensitive_operation") {
for (const key of Object.keys(telemetryData)) {
if (key.startsWith('mcp.request.argument')) delete telemetryData[key]
}
}
return telemetryData
}
]
}
const telemetry = instrumentServer(server, telemetryConfig)
// Add tools using the tool method
server.tool(...)
The TelemetryConfig interface provides comprehensive configuration options for customizing telemetry behavior: