Skip to content

Telegram Agent by Nova (CIVAI) MCP server

co.civai.nova/telegram-agentnova.civai.costreamable-httpv1.0.0Scanned

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

6 tools: 2 do something that can't be undone and 4 only read.

Tools: 0 delete, 2 irreversible, 0 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Telegram Agent by Nova (CIVAI) MCP server can do

The Telegram Agent by Nova (CIVAI) MCP server is published by nova.civai.co, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_message and converse), but cannot delete data. 4 tools only read.

1 tool reads private data (list_active_chat_participants); 1 tool brings in text other people can write (list_active_chat_participants); 2 tools can send data out of your system (send_message and converse). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Can't be undone 2Claude Code: ask
  • converseReply conversationally when the request is ambiguous or needs clarification.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "reply": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    Reply conversationally when the request is ambiguous or needs clarification.
  • send_messageTelegram: send messageCan send data outNo findings

    Why it is in this group

    • The name "send_message" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_message" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Telegram: send message
Only reads 4Show 4 read-only tools
  • list_active_chat_participantsTelegram: list active chat participantsReads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_active_chat_participants" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_active_chat_participants" says "list" and "chat": it reads messages.
    • private-dataThe description's first sentence says "chat": it reads messages.
    • untrusted-inputThe name "list_active_chat_participants" says "list" and "chat": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Telegram: list active chat participants
  • list_dialogsTelegram: list dialogsNo findings

    Why it is in this group

    • The name "list_dialogs" says "list": a word for reading.
    Description, as the server wrote it
    Telegram: list dialogs
  • list_group_participantsTelegram: list group participantsNo findings

    Why it is in this group

    • The name "list_group_participants" says "list": a word for reading.
    Description, as the server wrote it
    Telegram: list group participants
  • resolve_userTelegram: resolve userNo findings

    Why it is in this group

    • The name "resolve_user" says "resolve": a word for reading.
    Description, as the server wrote it
    Telegram: resolve user

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__telegram-agent__list_active_chat_participants"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:28 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/telegram-agent
Authorization servers
https://nova.civai.co
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://nova.civai.co/mcp/agents/telegram-agent: tools/list returned 6 tools to an anonymous client, including send_message (irreversible), converse (irreversible)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 13 to 2
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 11 to 13

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 13 -> 2.View diff
    • Tools that change things, listed without credentials: 13 to 2
  2. Tools6 added, 17 removed.+6 added−17 removedView diff
    • Added:converseCan't be undone
    • Added:list_active_chat_participantsOnly reads
    • Added:list_dialogsOnly reads
    • Added:list_group_participantsOnly reads
    • Added:resolve_userOnly reads
    • Added:send_messageCan't be undone
    • Removed:abort_scans
    • Removed:clear_discovery_cache
    • Removed:continue_scan
    • Removed:create_scan_schedule
    • Removed:delete_scan_schedule
    • Removed:delete_scans
    • Removed:get_discovery_analytics
    • Removed:get_scan
    • Removed:import_leads
    • Removed:list_connectors
    • Removed:list_scan_results
    • Removed:list_scan_schedules
    • Removed:list_scans
    • Removed:run_scan
    • Removed:suggest_targets
    • Removed:trigger_scan_schedule
    • Removed:update_scan_schedule
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 13.View diff
    • Tools that change things, listed without credentials: 11 to 13

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http telegram-agent https://nova.civai.co/mcp/agents/telegram-agent
claude mcp add --transport http telegram-agent https://nova.civai.co/mcp/agents/telegram-agent

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__telegram-agent__list_dialogs",
      "mcp__telegram-agent__list_group_participants",
      "mcp__telegram-agent__list_active_chat_participants",
      "mcp__telegram-agent__resolve_user"
    ],
    "ask": [
      "mcp__telegram-agent__send_message",
      "mcp__telegram-agent__converse"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as telegram-agent. Review it before you use it.

Capability tags behind 3 rules
  • mcp__telegram-agent__list_active_chat_participants private-data, untrusted-input
  • mcp__telegram-agent__send_message outbound
  • mcp__telegram-agent__converse outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.civai.nova/telegram-agent/verify?hash=594f83c56e97097cb0eb6e2e88e96a91b4fa51a325644e38028764dcfeb8ed61" | jq -e '.changed == false'

Pinned hash 594f83c56e97, from Nov 17, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.civai.nova/telegram-agent/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.civai.nova/telegram-agent
[![Anlyon Radar](https://radar.anlyon.com/badge/co.civai.nova/telegram-agent.svg)](https://radar.anlyon.com/servers/co.civai.nova/telegram-agent)

Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.

Telegram Agent by Nova (CIVAI) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Telegram Agent by Nova (CIVAI) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Telegram Agent by Nova (CIVAI) MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: send_message and converse.

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

6 tools: 2 irreversible, 4 read. send_message, converse, list_dialogs, list_group_participants, list_active_chat_participants and resolve_user.

Does the Telegram Agent by Nova (CIVAI) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Telegram Agent by Nova (CIVAI) MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_message and converse.

Has the Telegram Agent by Nova (CIVAI) MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.