Other · Remote MCP server
TeleQuick Platform
Tenant-scoped control plane over the TeleQuick platform's full API surface.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.telequick/portal- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-19
- Updated
- 2026-08-19
- Publisher
- dev.telequick
- Namespace
- Namespace verified by the MCP Registry via the domain telequick.dev · how
- Website
- docs.telequick.dev/concepts/coding-agents
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://portal.telequick.dev/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect TeleQuick Platform
TeleQuick Platform is a remote MCP server: there is nothing to install. Its endpoint is https://portal.telequick.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, docs.telequick.dev, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| Telegram MCP ServerLocal-first TDLib Telegram MCP server with 115 tools, account isolation and production guardrails. | Local · stdio |
| TeleKashOracle MCP-SERVERPrediction market probability oracle. 500+ markets from Kalshi, Polymarket & Metaculus. | Local · stdio |
| TelememLong-term and multimodal memory for AI agents - character-aware, mem0-compatible, fully-local option. | Local · stdio |
| TeleprompterRead and write your Teleprompter.com scripts and folders: list, create, update, and organize. | Remote · HTTPLive check: sign-in required |
| TelerivetSend, automate, and orchestrate SMS, WhatsApp, Viber, IVR, and USSD messaging in 150+ countries. | Remote · HTTPLive check: sign-in required |
| Telesherpa Ontology PlatformOntology platform for field service: AI agents observe, connect and act on business objects. | Remote · HTTPLive check: sign-in required |
| Telethon PlusSelf-hosted MCP server: Telegram userbot control (Telethon) via HTTP and MCP. | Local · HTTP |
| TellseedCreate surveys, feedback and classification campaigns. Collect human answers and export results. | Remote · HTTPLive check: sign-in required |