MCP server for the Telnyx API — billing, phone numbers, and messaging
MCP server for the Telnyx API — billing, phone numbers, and messaging. — Account balance, pending charges, credit limit — Get a specific invoice — Charges breakdown for a date range (max 60 days) — Charges summary for a date range — List all phone numbers on the account — Get details of a specific phone number — Search available numbers to purchase — Order/purchase a phone number — Send an SMS…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
MCP server for the Telnyx API — billing, phone numbers, and messaging. — Account balance, pending charges, credit limit — Get a specific invoice — Charges breakdown for a date range (max 60 days) — Charges summary for a date range — List all phone numbers on the account — Get details of a specific phone number — Search available numbers to purchase — Order/purchase a phone number — Send an SMS message — List sent and received messages — List messaging profiles Get your API key from…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.