_ registry / mcp http-sse · checked 2h ago

TelemetryDeck

https://mcp-builder.de

Registry code: 67f73c84e7eb0870

api record

TelemetryDeck analytics via TQL (TelemetryDeck Query Language). Before constructing any query you MUST:

1. Call `get_tql_guide` for the query language reference.

endpoint
https://mcp-builder.de/telemetry/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
104ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
2 open 4 never probed 2 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_apps open 2h ago

    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} objects.

    mcp-tool

    {
  "type": "object",
  "title": "list_appsArguments",
  "properties": {}
}
    arguments 5 lines
  • get_tql_guide open 2h ago

    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, experiment), filters, aggregations, intervals, and granularity.

    mcp-tool

    {
  "type": "object",
  "title": "get_tql_guideArguments",
  "properties": {}
}
    arguments 5 lines
  • login unknown never probed

    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 calls. Args: email: Your TelemetryDeck account email. password: Your TelemetryDeck account password.

    mcp-tool

    {
  "type": "object",
  "title": "loginArguments",
  "required": [
    "email",
    "password"
  ],
  "properties": {
    "email": {
      "type": "string",
      "title": "Email"
    },
    "password": {
      "type": "string",
      "title": "Password"
    }
  }
}
    arguments 18 lines
  • get_app_structure unknown never probed

    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-level keys: `appId`, `appName`, `description`, `exportDate`, `events`, `parameters`. Args: app_id: The TelemetryDeck app ID (from `list_apps`).

    mcp-tool

    {
  "type": "object",
  "title": "get_app_structureArguments",
  "required": [
    "app_id"
  ],
  "properties": {
    "app_id": {
      "type": "string",
      "title": "App Id"
    }
  }
}
    arguments 13 lines
  • run_query unknown never probed

    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, groupBy, funnel, retention, scan, experiment. Args: bearer_token: Your TelemetryDeck bearer token (from dashboard or login). app_id: The TelemetryDeck app ID to query. query: Full TQL query object as a dict.

    mcp-tool

    {
  "type": "object",
  "title": "run_queryArguments",
  "required": [
    "bearer_token",
    "app_id",
    "query"
  ],
  "properties": {
    "query": {
      "type": "object",
      "title": "Query",
      "additionalProperties": true
    },
    "app_id": {
      "type": "string",
      "title": "App Id"
    },
    "bearer_token": {
      "type": "string",
      "title": "Bearer Token"
    }
  }
}
    arguments 24 lines
  • get_insight_query unknown never probed

    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 TelemetryDeck bearer token. app_id: The TelemetryDeck app ID. insight_id: The UUID of the saved insight. days_back: Number of days to look back (default 30).

    mcp-tool

    {
  "type": "object",
  "title": "get_insight_queryArguments",
  "required": [
    "bearer_token",
    "app_id",
    "insight_id"
  ],
  "properties": {
    "app_id": {
      "type": "string",
      "title": "App Id"
    },
    "days_back": {
      "type": "integer",
      "title": "Days Back",
      "default": 30
    },
    "insight_id": {
      "type": "string",
      "title": "Insight Id"
    },
    "bearer_token": {
      "type": "string",
      "title": "Bearer Token"
    }
  }
}
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/67f73c84e7eb0870/badge.svg)](https://brick.blue/agent/67f73c84e7eb0870)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.