MCP server · Telesign

Telesign developer portal MCP server (ReadMe-hosted)

developer.telesign.com is a ReadMe-hosted portal and serves ReadMe's MCP endpoint at /mcp under Telesign's own documentation domain. An unauthenticated JSON-RPC tools/list is refused with "Authorization required", so the live tool schemas could not be read. Telesign publishes no MCP documentation and no tool table, and no /.well-known/oauth-protected-resource or oauth-authorization-server document is served on this host, so the authorization server an agent should use is not discoverable from the endpoint. This is a platform feature of the docs host rather than a server Telesign engineered; it is recorded as the provider's MCP surface because it is served from a host Telesign controls.

Open endpoint → Telesign provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Telesign Type: Hosted endpoint Transport: streamable-http Host: developer.telesign.com

Endpoint

https://developer.telesign.com/mcp

Hosted endpoint · transport streamable-http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "telesign": { "url": "https://developer.telesign.com/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "telesign": { "command": "npx", "args": ["-y", "mcp-remote", "https://developer.telesign.com/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://developer.telesign.com/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for mcp servers

4 MCP tools reach this
  • find_mcpBrowse and filter every MCP server in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This MCP server 
curl "https://apis.io/api/v1/mcp/telesign-developer-portal-mcp-server-readme-hosted"
All mcp servers 
curl "https://apis.io/api/v1/mcp?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.