LeashIndex Get the report

Index / devtools

com.tweetsmash/mcp

com-tweetsmash-mcp declares 53 capabilities across 53 tools, with 2 critical issues.

95/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://mcp.tweetsmash.com/api/mcp, published in the official MCP registry as com.tweetsmash/mcp 2.0.0. 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 53 tools

53 of 53 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 · 9 of 53 tools

9 tools are classified as irreversible and declare no limit.

high · no-expiry · All 53 tools

53 of 53 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 53 tools

53 of 53 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 · 11 of 53 tools

11 tools can modify data and declare no limit.

low · uncapped-read · 33 of 53 tools

33 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
list_bookmarksread declared
list_likesread declared
search_bookmarksread declared
get_bookmark_countread declared
list_labelsread declared
add_labels_to_tweetswrite inferred
remove_labels_from_tweetsdestructive declared
delete_labeldestructive declared
setup_vector_storeread inferred
list_skillsread declared
get_skillread declared
get_library_overviewread declared
search_docsread declared
get_bookmarkread declared
tag_bookmarks_by_filterwrite inferred
archive_bookmarksdestructive declared
archive_bookmarks_by_filterdestructive declared
list_smart_viewsread declared
get_smart_viewread declared
get_smart_view_bookmarksread declared
create_smart_viewread inferred
update_smart_viewread inferred
delete_smart_viewdestructive declared
create_share_linkwrite inferred
revoke_share_linkdestructive declared
trigger_pdf_exportwrite assumed
trigger_csv_exportwrite assumed
trigger_json_exportwrite assumed
list_digest_preferencesread declared
update_digest_preferencewrite inferred
delete_digest_preferencedestructive declared
list_past_digestsread declared
list_mash_digestsread declared
list_mash_digest_issuesread declared
get_mash_digest_issueread declared
compose_mash_digestwrite assumed
get_sync_statusread declared
get_bookmark_sync_statusread declared
list_twitter_listsread declared
get_list_tweetsread declared
get_list_digestsread declared
send_list_digestsend inferred
preview_list_rankingread declared
get_author_preferencesread declared
set_author_preferencewrite inferred
get_meread declared
get_connection_statusread declared
fetch_recent_bookmarksread declared
rememberwrite assumed
recallread declared
forgetdestructive declared
get_interestsread declared
correct_interestwrite assumed
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.