Shinzo TsSAFE
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.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
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.
Explore the docs »
Installation
pnpm add @shinzolabs/instrumentation-mcp
Usage
For the simplest configuration, just pass in the server name, version, and exporter endpoint:
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js"
import { instrumentServer, Telemed56014c61bfcOBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add instrumentation-mcp --env OTEL_AUTH_TOKEN=${OTEL_AUTH_TOKEN} -- npx -y @shinzolabs/[email protected]{
"mcpServers": {
"instrumentation-mcp": {
"command": "npx",
"args": [
"-y",
"@shinzolabs/[email protected]"
],
"env": {
"OTEL_AUTH_TOKEN": "${OTEL_AUTH_TOKEN}"
}
}
}
}Exposed tools (7)
5 read · 2 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
add_numbers | write | Adds a list of numbers together |
calculator | read | Performs basic arithmetic operations |
create_story | write | Creates a short story using provided words like madlibs |
echo | read | Echoes back the input |
failing-tool | read | Always fails for testing error handling |
random_wait | read | Waits for a random number of seconds between 0 and 3, then returns the duration |
slow-operation | read | Simulates a slow operation |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (4)
.DS_Store
.eslintrc.js
.DS_Store
@opentelemetry/auto-instrumentations-node, @opentelemetry/core, @opentelemetry/exporter-metrics-otlp-http, @opentelemetry/exporter-trace-otlp-grpc, @opentelemetry/exporter-trace-otlp-http, @openteleme
Gates applied: no_behavioural_pass.
d56014c61bfcfull audit observations/trust-audit/mcp-server/shinzo-labs__shinzo-ts.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | d56014c61bfc | SAFE | B | 89 | first audit |
Questions
What is the @shinzolabs/instrumentation-mcp MCP server?
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.
What tools does @shinzolabs/instrumentation-mcp expose?
7 in total: 5 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is @shinzolabs/instrumentation-mcp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does @shinzolabs/instrumentation-mcp need?
It reads OTEL_AUTH_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does @shinzolabs/instrumentation-mcp run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @shinzolabs/instrumentation-mcp at 1.1.0.
How current is this page?
The grade is for one exact copy of the source (d56014c61bfc), read on 2026-10-12. The repository is watched and re-audited when it changes.