Loading…
TelemetryDeck analytics API integration for querying app telemetry data with TQL.
Do not connect
A critical issue was found. Do not connect this server as-is.
Scanned 7 days ago Due for re-check
A server can change after it's graded. Re-run the automated scan to refresh this report.
This grade is deterministic and reproducible: the same server surface always yields the same grade under a given algorithm version. It is a real automated assessment computed by the MCPGrade engine from what the probe actually observed — not a fabricated or opinion score. It is not a manual human pentest, so it can miss context-specific risks.
Every signal below was measured directly by the automated probe. The grade is derived only from evidence like this — nothing is assumed.
The TelemetryDeck MCP server exposes 6 tools, focused primarily on database capabilities. Its published description reads: "TelemetryDeck analytics API integration for querying app telemetry data with TQL". It communicates over Streamable HTTP using the 2025-06-18 protocol revision, and does not require authorization to connect. MCPGrade currently rates TelemetryDeck F — a critical issue was found and the server should not be connected as-is. Its most notable findings include "Cross-tool shadowing" and "Tool input schema requests a secret". This report is a deterministic, reproducible automated assessment: the same observed surface always yields the same grade under a given algorithm version, and it is refreshed as new scans arrive and free to read — but it is not a substitute for a manual human security review. Always re-check TelemetryDeck's advertised tools, transport security, and authorization posture before connecting an autonomous agent or sharing sensitive context with it.
Add TelemetryDeck to an MCP client using the endpoint below. Review the grade and findings above before granting an autonomous agent access.
MCP endpoint
https://mcp-builder.de/telemetry/mcpStreamable HTTP transport. This is the MCP endpoint, not a website — paste it into your MCP client server list rather than a browser.
Captured passively during the read-only scan. Click any value to find servers that match it.
The tools this server advertises via tools/list — names, purposes, and the parameters each accepts, exactly as enumerated read-only.
Log in to TelemetryDeck and retrieve a bearer token. Use this tool first to authenticate before calling run_query or get_insight_query. The returned bearer token can be used for all subsequent API cal
Return the TQL (TelemetryDeck Query Language) reference guide. You MUST call this before constructing any query. The guide covers query types (timeseries, topN, groupBy, funnel, retention, scan, exper
List the apps available for querying. Call this to discover the `app_id` values you can pass to `run_query`, `get_insight_query`, and `get_app_structure`. Returns a JSON array of {appId, appName} obje
Return the StructuralData (events + parameters) for a given app. Call this after `list_apps` to learn which events and parameters are available for the app you want to query. The returned JSON has top
Sorted worst-first. Each finding shows its severity, what it means, its OWASP MCP Top-10 mapping, and a recommended fix — the check id links to the exact methodology row that produced it.
tool: login
A tool description tries to alter the model’s use of another tool.
before calling run_query or get_insight_query. The returned bearer tokenRecommendationDescriptions must describe only their own tool.
tool: login
The input schema declares a parameter that asks the caller to hand over a password, key, token, or other secret — a credential-harvest / token-passthrough risk. (Bare pagination `token` params are excluded.)
parameter "password"RecommendationNever pass secrets as tool arguments; authenticate out-of-band and remove credential parameters from the schema.
tool: get_tql_guide
The text tells the model WHEN to call this tool relative to others ("always call first", "before any other tool", "chain to X tool") — a toxic-flow injection that hijacks the agent’s orchestration rather than describing the tool.
nce guide. You MUST call this before constructing any query. The guide covers queryRecommendationTool metadata must describe only the tool, never sequence the agent’s calls.
tool: list_apps
A tool description tries to alter the model’s use of another tool.
ht_query`, and `get_app_structure`. Returns a JSON array of {appId, appName} objeRecommendationDescriptions must describe only their own tool.
tool: get_app_structure
A tool description tries to alter the model’s use of another tool.
all this after `list_apps` to learn which events and parameters are availRecommendationDescriptions must describe only their own tool.
tool: run_query
Tools that execute commands / write files / make arbitrary requests are exposed without annotations or guards.
run_query Execute a TQL query against TelemetryDeck. The query parameter isRecommendationAnnotate destructive tools and require human approval.
tool: run_query
A tool description tries to alter the model’s use of another tool.
om dashboard or login). app_id: The TelemetryDeck app ID to queryRecommendationDescriptions must describe only their own tool.
tool: run_query
The input schema declares a parameter that asks the caller to hand over a password, key, token, or other secret — a credential-harvest / token-passthrough risk. (Bare pagination `token` params are excluded.)
parameter "bearer_token"RecommendationNever pass secrets as tool arguments; authenticate out-of-band and remove credential parameters from the schema.
tool: get_insight_query
A tool description tries to alter the model’s use of another tool.
t or pass it to run_query to execute it. Args: bearer_token: Your TeRecommendationDescriptions must describe only their own tool.
tool: get_insight_query
The input schema declares a parameter that asks the caller to hand over a password, key, token, or other secret — a credential-harvest / token-passthrough risk. (Bare pagination `token` params are excluded.)
parameter "bearer_token"RecommendationNever pass secrets as tool arguments; authenticate out-of-band and remove credential parameters from the schema.
tool: (server instructions)
A tool description tries to alter the model’s use of another tool.
UST: 1. Call `get_tql_guide` for the query language reference. 2. Call `lRecommendationDescriptions must describe only their own tool.
The server accepts tool enumeration (and likely invocation) with no authentication.
RecommendationRequire OAuth 2.1 authorization for any server exposing non-public tools.
tool: run_query
The server advertises open-world / broadly-scoped capabilities.
no annotations on write-capable tool "run_query"RecommendationScope tools to the minimum needed.
tool: get_insight_query
The server advertises open-world / broadly-scoped capabilities.
no annotations on write-capable tool "get_insight_query"RecommendationScope tools to the minimum needed.
Vantaj uptime monitoring via MCP — manage monitors, heartbeats, incidents, and status pages.
Unified gateway to Algeria's TKAWEN ecosystem: commerce, certification, and AI tools.
Provides access to the Cohereon Doctrine AI safety framework with governance components, tiered access, and agent onboarding.
Agentic rails for complex workflows with receipts, fees, and MCP tool access.
Structural TC39 spec lookup for ECMA-262 and ECMA-402 in AI agents, SHA-pinned and offline-first.
Structural TC39 spec lookup for ECMA-262 and ECMA-402 in AI agents, SHA-pinned and offline-first.
Execute a TQL query against TelemetryDeck. The query parameter is a full TQL JSON object. Refer to the TQL guide in the server instructions for syntax details. Supported query types: timeseries, topN,
Get the TQL query object for a saved TelemetryDeck insight. Returns the TQL JSON that the insight would execute. You can inspect it or pass it to run_query to execute it. Args: bearer_token: Your Tele