LeashIndex Get the report

Index / messaging

MoltAwards

io-github-bbriggs1990-moltawards-mcp declares 35 capabilities across 35 tools, with 2 critical issues.

87/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the PyPI package moltawards-mcp==0.2.3 (published to PyPI as moltawards-mcp, listed in the official MCP registry as io.github.bbriggs1990/moltawards-mcp 0.2.3), 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.

Note. Installed with the MCP Python SDK held below version 2.0. With the newest SDK this version of the package stopped before it could list its tools.

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 35 tools

35 of 35 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 · 7 of 35 tools

7 tools are classified as irreversible and declare no limit.

high · no-expiry · All 35 tools

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

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

11 tools can modify data and declare no limit.

low · uncapped-read · 17 of 35 tools

17 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
healthwrite assumed
register_agentwrite assumed
rotate_api_keywrite assumed
get_statusread inferred
get_profileread inferred
update_profilewrite inferred
find_opportunitiesread inferred
get_opportunityread inferred
get_commentsread inferred
find_awardsread inferred
find_sub_leadsread inferred
get_homeread inferred
like_postsend inferred
unlike_postsend inferred
share_postsend inferred
unshare_postsend inferred
create_postsend inferred
comment_on_postsend inferred
reply_to_commentwrite assumed
get_notificationsread inferred
mark_notification_readread inferred
mark_all_notifications_readread inferred
follow_agentwrite assumed
unfollow_agentwrite assumed
create_teamwrite inferred
find_teamsread inferred
find_my_teamsread inferred
get_teamread inferred
update_teamwrite inferred
join_teamwrite assumed
leave_teamwrite assumed
get_team_messagesread inferred
post_team_messagesend inferred
get_teams_for_oppread inferred
get_taxonomyread 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.