LeashIndex Get the report

Index / messaging

24Repost

io-github-24repost-ru-24repost-mcp declares 41 capabilities across 41 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

89/100 exposureHigh exposure

Manifest recorded 2026-11-08 from tools/list on https://my.24repost.ru/mcp, published in the official MCP registry as io.github.24repost-ru/24repost-mcp 1.0.1. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 41 tools

41 of 41 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 2 of 41 tools

2 tools are classified as irreversible and declare no limit.

high · no-expiry · All 41 tools

41 of 41 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 41 tools

41 of 41 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 26 of 41 tools

26 tools can modify data and declare no limit.

low · uncapped-read · 13 of 41 tools

13 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
chats_listread declared
routes_listread declared
route_showread declared
route_createwrite inferred
route_set_two_waywrite inferred
route_resumewrite assumed
route_pausewrite assumed
route_configurewrite assumed
route_change_targetwrite assumed
route_set_ruleswrite inferred
route_set_wordswrite inferred
route_set_replacementswrite inferred
route_set_attachmentswrite inferred
route_set_utmwrite inferred
route_set_ad_filterwrite inferred
route_set_frame_textwrite inferred
route_set_groupwrite inferred
route_set_delaywrite inferred
route_set_schedulewrite inferred
import_startwrite assumed
import_showread declared
import_pausewrite assumed
import_resumewrite assumed
import_canceldelete inferred
group_createwrite inferred
group_renamewrite inferred
chat_assign_botwrite inferred
chatbots_listread declared
chatbot_showread declared
chatbot_rulesread declared
chatbot_statsread declared
chatbot_savewrite assumed
bot_constants_listread declared
bot_constant_setwrite inferred
bot_constant_deletedelete inferred
channel_statsread declared
topics_listread declared
route_set_topicswrite inferred
notifications_showread declared
route_comments_stateread declared
route_set_commentswrite inferred
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.