Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Telegram Agent by Nova (CIVAI)

REMOTE · NOVA.CIVAI.CO

I use your linked Telegram MTProto session (Integrations → Telegram) to list groups, members, and s…

Available components

+4 this week 76 Trust /100

Last scanned (16 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security92
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 276 tokens (~46/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 30 days we've observed: 17 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +4
    • Authorization: fail → pass ▲ security
    • First check of Authorization: pass security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Nov 26 −9
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “abort_scans” was removed ▼ security
    • Tool “clear_discovery_cache” was removed ▼ security
    • Tool “continue_scan” was removed ▼ security
    • Tool “create_scan_schedule” was removed ▼ security
    • Tool “delete_scan_schedule” was removed ▼ security
    • Tool “delete_scans” was removed ▼ security
    • Tool “get_ad_guide” was removed ▼ security
    • Tool “get_ad_plan” was removed ▼ security
    • Tool “get_discovery_analytics” was removed ▼ security
    • Tool “get_scan” was removed ▼ security
    • Tool “import_leads” was removed ▼ security
    • Tool “launch_ad_plan” was removed ▼ security
    • Tool “list_ad_plans” was removed ▼ security
    • Tool “list_connectors” was removed ▼ security
    • Tool “list_scan_results” was removed ▼ security
    • Tool “list_scan_schedules” was removed ▼ security
    • Tool “list_scans” was removed ▼ security
    • Tool “run_scan” was removed ▼ security
    • Tool “stop_ad_plan” was removed ▼ security
    • Tool “suggest_targets” was removed ▼ security
    • Tool “trigger_scan_schedule” was removed ▼ security
    • Tool “update_scan_schedule” was removed ▼ security
    • Tool coverage: 16% → 100% ▲ functional
    • Schema quality: 77 → 46 ▲ functional
    • Schema quality: fair → good functional
    • New tool “converse” functional
    • New tool “list_active_chat_participants” functional
    • New tool “list_dialogs” functional
    • New tool “list_group_participants” functional
    • New tool “resolve_user” functional
    • New tool “send_message” functional
  • 30 Oct 26 +1
    • Schema quality: 66 → 77 ▼ functional
    • Tool coverage: 0% → 16% ▲ functional
    • New tool “get_ad_guide” functional
    • New tool “get_ad_plan” functional
    • New tool “launch_ad_plan” functional
    • New tool “list_ad_plans” functional
    • New tool “stop_ad_plan” functional
  • 29 Oct 26 +14
    • Stability: fail → pass ▲ security
  • 25 Oct 26 0
    • Tool “create_scan_schedule” rewrote its description, which is the text the model reads security
    • Tool “run_scan” rewrote its description, which is the text the model reads security
    • Tool “update_scan_schedule” rewrote its description, which is the text the model reads security
    • Schema quality: 55 → 66 ▼ functional
  • 21 Oct 26 0
    • Authorization: unverified → fail ▼ security
  • 20 Oct 26 0
    • Authorization: fail → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://nova.civai.co/mcp/agents/telegram-agent

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.vearn.co CN=YR2,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 RSA 2048 SHA256-RSA 5989a0174450d554cb27dbfdec88b2ff58a
SANs: allegedly-api.crypvestai.cloud, allegedly.crypvestai.cloud, api.agi.civai.co, api.browser.civai.co, api.nova.civai.co, api.vearn.co, app.browsergpt.co, app.vearn.co, arcade-assets.civai.co, audience-resolver-api.civai.co, audience-resolver.civai.co, audience.civai.co and 11 more
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of nova.civai.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
civai.co. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/telegram-agent", scope="mcp:access"

Bearer resource_metadata="https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/telegram-agent", scope="mcp:access"

Protected resource metadata

Document https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/telegram-agent
Retrieved Yes
Resource https://nova.civai.co/mcp/agents/telegram-agent
Authorisation server https://nova.civai.co

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://nova.civai.co/mcp/agents/telegram-agent Verified 200
http (plaintext) http://nova.civai.co/mcp/agents/telegram-agent HTTPS enforced 301 https://nova.civai.co/mcp/agents/telegram-agent
MCP tools · 6 exposed · ~276 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
converse ~33

Reply conversationally when the request is ambiguous or needs clarification.

NameTypeReqDescription
reply_hintstring–Optional hint for the conversational reply.

No output schema declared.

No examples provided.

list_active_chat_participants ~68

Telegram: list active chat participants

NameTypeReqDescription
active_daysinteger–Only users active in chat within this many days (default 90).
chat_idstringyesTelegram group id from list_dialogs.
limitinteger–Max participants (default 2000).

No output schema declared.

No examples provided.

list_dialogs ~29

Telegram: list dialogs

NameTypeReqDescription
limitinteger–Max dialogs to return (default 100).

No output schema declared.

No examples provided.

list_group_participants ~47

Telegram: list group participants

NameTypeReqDescription
chat_idstringyesTelegram group or channel id from list_dialogs.
limitinteger–Max participants (default 2000).

No output schema declared.

No examples provided.

resolve_user ~25

Telegram: resolve user

NameTypeReqDescription
usernamestringyesTelegram @username to resolve.

No output schema declared.

No examples provided.

send_message ~74

Telegram: send message

NameTypeReqDescription
access_hashstring–Recipient access_hash when sending by user id.
telegram_user_idstring–Recipient user id (from resolve_user or participant list).
textstringyesMessage body to send.
usernamestring–Recipient @username (alternative to user id).

No output schema declared.

No examples provided.

Install

How do I install the Telegram Agent by Nova (CIVAI) MCP server?

Telegram Agent by Nova (CIVAI) is a hosted endpoint at https://nova.civai.co/mcp/agents/telegram-agent, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · nova.civai.co

# add to Claude Code
claude mcp add --transport http co-civai-nova-telegram-agent 'https://nova.civai.co/mcp/agents/telegram-agent'
Common questions

What is the Telegram Agent by Nova (CIVAI) MCP server?

Telegram Agent by Nova (CIVAI) is an MCP server listed in the public MCP registry as co.civai.nova/telegram-agent. I use your linked Telegram MTProto session (Integrations → Telegram) to list groups, members, and s… This page covers its hosted endpoint (https://nova.civai.co/mcp/agents/telegram-agent).

Is the Telegram Agent by Nova (CIVAI) MCP server safe to use?

Telegram Agent by Nova (CIVAI) scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Telegram Agent by Nova (CIVAI) MCP server expose?

Telegram Agent by Nova (CIVAI) exposes 6 tools: list_dialogs, list_group_participants, list_active_chat_participants, resolve_user, send_message, converse. Their descriptions and schemas cost roughly 276 tokens of context every time the server is loaded.

Does the Telegram Agent by Nova (CIVAI) MCP server require authentication?

Yes. Telegram Agent by Nova (CIVAI) asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Telegram Agent by Nova (CIVAI) MCP server still maintained?

Telegram Agent by Nova (CIVAI) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Telegram Agent by Nova (CIVAI) MCP server?

VerifyMCP ran 13 checks on Telegram Agent by Nova (CIVAI), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.