MCP 鉴权未知未评级已上架

Prism

A drop-in telemetry bridge that sits between any chat or agent and any MCP server, streaming OpenTelemetry spans for every JSON-RPC turn: tool calls, resource reads, prompts, progress events, errors, and latency. No SDK. No code changes. Point your client at Prism and you get distributed tracing. - **Every call becomes a span**: method, duration, status, payload size, session and trace correlation, redacted arguments - **Fan-out telemetry**: ship spans to Telinea (hosted dashboard, launching October 1st) or any OTLP endpoint: Jaeger, Honeycomb, Datadog, Grafana Tempo - **Transparent relay**: Streamable HTTP and legacy SSE pass through untouched; your server never knows Prism is there - **Session-aware**: spans group into traces per MCP session, so you see whole conversations, not isolated calls - **Safe by default**: secrets redacted at intake, SSRF-guarded upstreams, per-token rate limiting, dead-letter buffering so spans survive downstream outages When you set `telineaApiKey`, Prism delivers your spans to Telinea's dedicated OTLP ingest at `https://ingest.terradev.cloud/v1/traces` — a high-throughput endpoint built for binary protobuf telemetry, landing in your dashboard in real time. Already have OpenTelemetry producers like LangChain pipelines, CI/CD agents, vLLM servers? They can POST OTLP straight to the same ingest point, no Prism needed. One endpoint, one dashboard, all your spans. Telinea launches October 1st.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://prism--wolfendentheo.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "Prism": {
      "url": "https://prism--wolfendentheo.run.tools"
    }
  }
}

能力清单

工具	说明
prism_info	Returns Prism's service identity and runtime state: version, transport, public URL, capture default, and the number of MCP sessions currently being traced. Use this to confirm which Prism deployment you are talking to and whether it is healthy before configuring an upstream.
prism_ping	Returns {"pong": true, "time": <unix seconds>} plus an optional echo of the 'echo' argument. Use to verify connectivity through the gateway before pointing it at an upstream MCP server.
prism_metrics	Dumps Prism's in-process counters and gauges — spans shipped, upstream errors, rate-limit hits, queue depth. Two formats: 'prometheus' (default, scrape-ready text) or 'json' (a {"series{labels}": value} object). Use 'prefix' to narrow to a metric family, e.g. 'prism_spans'.
prism_sessions	Lists the MCP sessions Prism is currently tracing — session id prefix, upstream, client name, project, turn and error counts, and age in seconds. Use 'limit' to cap results (default 20, max 100) and 'upstream' to filter by upstream URL substring.
prism_config	Returns Prism's effective runtime configuration — upstream allowlist, rate limit, capture default, batching and queue tunables, public URL, and configured ingest endpoints. Secrets (admin token, destination credentials) are never exposed — only whether they are set.
prism_help	Returns connection instructions: how to set the upstream MCP server (X-Prism-Upstream header or ?upstream= query param), the query-param config keys for header-less clients, how destinations and the borrowed-token model work, and example client configs. Start here if you are an agent discovering Prism for the first time.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。