_ registry / mcp http-sse · checked 48m ago

telnyx_api

https://api.telnyx.com

Registry code: 5ae7f3195868ffc8

api record

Telnyx MCP is served over Streamable HTTP at https://api.telnyx.com/v2/mcp. Public discovery methods are initialize, tools/list, resources/list, and resources/read; notifications/initialized is also accepted during startup. Calling tools/call requires Authorization: Bearer <TELNYX_API_KEY>. Use the dynamic API flow list_api_endpoints -> get_api_endpoint_schema -> invoke_api_endpoint to discover and call Telnyx APIs. MCP Apps are available as UI resources via resources/list and resources/read.

endpoint
https://api.telnyx.com/v2/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is telnyx_api live?
Yes — it answered the hub's last check (checked 48m ago). It answered 99% of checks over the last 30 days.
Is telnyx_api free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does telnyx_api have?
6 tools: list_api_endpoints, open_usage_cost_explorer, get_api_endpoint_schema, invoke_api_endpoint, open_number_intelligence, open_voice_monitor.
Is telnyx_api safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.5%

90 days 98%· all time 98%

latency
243ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 396 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· HTTP 503
  • degraded → live
_ what it is for
used for
  • find telnyx api endpoints
  • call a telnyx api endpoint
  • look up phone number intelligence
  • explore telnyx usage and cost
takes → gives
data → data
tools
5 reads1 effect unclear
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 auth-required 6 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_api_endpoints reads auth-required 17h ago

    List or search for all endpoints in the Telnyx TypeScript API

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [],
      "properties": {
        "search_query": {
          "type": "string",
          "description": "An optional search query to filter the endpoints by. Provide a partial name, resource, operation, or tag to filter the endpoints returned."
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • open_usage_cost_explorer reads auth-required 17h ago

    Open the Telnyx Usage & Cost Explorer MCP App for usage and cost analysis.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [],
      "properties": {
        "action": {
          "enum": [
            "open"
          ],
          "type": "string",
          "default": "open",
          "description": "Optional no-op app opener action; omit to open the app."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • get_api_endpoint_schema reads auth-required 10h ago

    Get the schema for an endpoint in the Telnyx TypeScript API. You can use the schema returned by this tool to invoke an endpoint with the `invoke_api_endpoint` tool.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "endpoint"
      ],
      "properties": {
        "endpoint": {
          "type": "string",
          "description": "The name of the endpoint to get the schema for."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • invoke_api_endpoint auth-required never probed

    Invoke an endpoint in the Telnyx TypeScript API. Note: use the `list_api_endpoints` tool to get the list of endpoints and `get_api_endpoint_schema` tool to get the schema for an endpoint.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "endpoint_name",
        "args"
      ],
      "properties": {
        "args": {
          "type": "object",
          "description": "The arguments to pass to the endpoint. This must match the schema returned by the `get_api_endpoint_schema` tool.",
          "additionalProperties": {}
        },
        "endpoint_name": {
          "type": "string",
          "description": "The name of the endpoint to invoke."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • open_number_intelligence reads auth-required 17h ago

    Open the Telnyx Number Intelligence MCP App for phone number lookup, validation, and enrichment workflows.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [],
      "properties": {
        "action": {
          "enum": [
            "open"
          ],
          "type": "string",
          "default": "open",
          "description": "Optional no-op app opener action; omit to open the app."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • open_voice_monitor reads auth-required 10h ago

    Open the Telnyx Voice Monitor MCP App for observing and troubleshooting voice traffic.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [],
      "properties": {
        "action": {
          "enum": [
            "open"
          ],
          "type": "string",
          "default": "open",
          "description": "Optional no-op app opener action; omit to open the app."
        }
      },
      "additionalProperties": false
    }
    arguments 16 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5ae7f3195868ffc8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5ae7f3195868ffc8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5ae7f3195868ffc8/badge.svg)](https://brick.blue/agent/5ae7f3195868ffc8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ 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.

_ also on telnyx.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.