MCP serverco.civai.nova/telegram-agent
I use your linked Telegram MTProto session (Integrations → Telegram) to list groups, members, and s…
Overview
Score?
UNRATED 0.718
of what a free look can see, on 20 looks
Looks
51
last 2 hr ago
Tools
6
changed 18 days ago
More info
URL
nova.civai.co/mcp/agents/telegram-agent
streamable-http
Says it is
Telegram Agent by Nova (CIVAI) 1.0.0
protocol 2025-06-18
In the record since
58 days ago
Among servers32,729 with a card
0median 0.547 · this server 0.718 · highest on record 0.8351
Toolsfrom sha256:9922249b4b…a1d4a5 · +6 −22 18 days ago
| Tool | Schema |
|---|---|
| converse added Reply conversationally when the request is ambiguous or needs clarification. |
input · no output |
| list_active_chat_participants added Telegram: list active chat participants |
input · no output |
| list_dialogs added Telegram: list dialogs |
input · no output |
| list_group_participants added Telegram: list group participants |
input · no output |
| resolve_user added Telegram: resolve user |
input · no output |
| send_message added Telegram: send message |
input · no output |
Stop stuck running scans (marks interrupted, releases schedule lock). |
— |
Clear Leads Discovery scan cache for an agent (seen handles / WA progress). |
— |
Continue a scan paused for selection (WhatsApp/Telegram groups or IG/X targets). |
— |
Create an auto-scan schedule (Import Only or Message now outreach). Discovery params for x/instagram accept max_post_age_days (1-365; omit = no age limit) and post_age_relax_steps |
— |
Delete an auto-scan schedule. |
— |
Delete one or more completed scan runs (does not delete schedules). |
— |
The ad plan rendered as steps to tap, per channel, in the owner's own words with the daily budget already divided. Use this when the owner wants to run the ads themselves. Nova nev |
— |
The ads this business should run, built from its own scans: three things to film, each citing a count from this agent's own leads, plus the spend and reach for a lead target. Reads |
— |
Get sourced-leads analytics for an agent (window e.g. 7d, 30d). |
— |
Get one scan with paginated leads (status, progress, leads). |
— |
Import discovered leads into the agent CRM (outreach: none|immediate|bulk_followup). |
— |
Run one ad on one channel, under a spend cap the owner has named out loud. The cap is debited before anything is created and nothing is ever created above it. Creative is the owner |
— |
Every ad this agent has already launched, newest first, with its cap, its channel and whether it is running or stopped. Reads only. |
— |
List WhatsApp, Instagram, Email, X connector status for a support agent. |
— |
Alias of get_scan — read leads from an active or completed scan. |
— |
List auto-scan schedules for an agent. |
— |
List past and active leads discovery scans for an agent. |
— |
Start a leads discovery scan (whatsapp, instagram, x, telegram, or jiji). Discovery params for x/instagram accept max_post_age_days (1-365; omit = no age limit) and post_age_relax_ |
— |
Switch one launched ad off. The campaign is paused first, so spend stops on the very first call. |
— |
AI-propose Instagram or X @targets for a discovery scan (depth/breadth optional). |
— |
Run an auto-scan schedule immediately (Run now). |
— |
Update or pause/resume an auto-scan schedule. Discovery params for x/instagram accept max_post_age_days (1-365; omit = no age limit) and post_age_relax_steps (0-4, default 3) to ca |
— |
Verify it yourself
npx teppi-check https://nova.civai.co/mcp/agents/telegram-agentcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M318Q9J3PVCM7R0W72ERTKBG