LeashIndex Get the report

Index / devtools

io.github.BillNobill/trello-mcp-server

io-github-billnobill-trello-mcp-server declares 33 capabilities across 33 tools, with 2 critical issues.

86/100 exposureHigh exposure

Manifest recorded 2026-10-12 from tools/list answered by the npm package @billnobill/trello-mcp-server@1.1.0 (published to npm as @billnobill/trello-mcp-server, listed in the official MCP registry as io.github.BillNobill/trello-mcp-server 1.1.0), run in an isolated container with no network access and placeholder credentials. 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 33 tools

33 of 33 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 · 4 of 33 tools

4 tools are classified as irreversible and declare no limit.

high · no-expiry · All 33 tools

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

33 of 33 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 · 16 of 33 tools

16 tools can modify data and declare no limit.

low · uncapped-read · 13 of 33 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
list_boardsread inferred
read_boardread inferred
get_board_labelsread inferred
get_board_membersread inferred
create_listread inferred
create_cardwrite inferred
assign_memberwrite inferred
add_checklistwrite inferred
update_checklistwrite inferred
delete_checklistdelete inferred
create_checkitemwrite inferred
update_checkitemwrite inferred
delete_checkitemdelete inferred
add_attachmentwrite inferred
move_cardwrite inferred
add_commentwrite inferred
archive_carddelete inferred
archive_listread inferred
delete_boarddelete inferred
update_listread inferred
update_cardwrite inferred
update_card_namewrite inferred
create_labelwrite inferred
update_labelwrite inferred
move_all_cardswrite inferred
upload_filewrite inferred
set_custom_fieldwrite inferred
get_lists_on_boardread inferred
get_cards_in_listread inferred
get_cards_by_dateread inferred
get_member_workloadread inferred
get_card_detailsread inferred
search_cardsread 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.