Search / io.github.Shreyas-Profile/telegram-mcp
telegram-mcp
not classifiedTelegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
v0.4.0 · active · repository · descriptor JSON · versions
Search / io.github.Shreyas-Profile/telegram-mcp
Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
v0.4.0 · active · repository · descriptor JSON · versions
{
"mcpServers": {
"telegram-mcp": {
"type": "http",
"url": "https://telegram.regiq.in/api/mcp"
}
}
}claude mcp add --transport http telegram-mcp https://telegram.regiq.in/api/mcp[mcp_servers.telegram-mcp]
url = "https://telegram.regiq.in/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"telegram-mcp": {
"type": "remote",
"url": "https://telegram.regiq.in/api/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"telegram-mcp": {
"type": "http",
"url": "https://telegram.regiq.in/api/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=telegram-mcp&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdGVsZWdyYW0ucmVnaXEuaW4vYXBpL21jcCJ9"
}{
"servers": {
"telegram-mcp": {
"type": "http",
"url": "https://telegram.regiq.in/api/mcp"
}
}
}{
"mcpServers": {
"telegram-mcp": {
"httpUrl": "https://telegram.regiq.in/api/mcp"
}
}
}extensions:
"telegram-mcp":
enabled: true
name: "telegram-mcp"
type: streamable_http
uri: "https://telegram.regiq.in/api/mcp"
timeout: 300
Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.
protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)auth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)stability.changes, stability.rug_pulltool list unknowndeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +reachable +uptime-94% ~updated-98d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://telegram.regiq.in/api/mcp streamable-http | unknown | yes | 94% | 208 ms | – | 2026-10-20 |
No tools observed. Tools appear once a credential-free probe can list them.
Schemas: list_tools.
{
"name": "io.github.Shreyas-Profile/telegram-mcp",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
"remotes": [
{
"url": "https://telegram.regiq.in/api/mcp",
"type": "streamable-http",
"headers": [
{
"name": "Authorization",
"description": "Bearer <apiKey> — get yours at https://telegram.regiq.in after Google sign-in."
}
]
}
],
"version": "0.4.0",
"repository": {
"url": "https://github.com/globalion/telegram-mcp",
"source": "github"
},
"description": "Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack."
}