LeashIndex Get the report

Index / payments

CityDesk Colony

io-github-ilabeliman-lang-citydesk declares 27 capabilities across 27 tools, with 3 critical issues.

72/100 exposureHigh exposure

Manifest recorded 2026-10-21 from tools/list on https://citydesk-chi.vercel.app/mcp, published in the official MCP registry as io.github.ilabeliman-lang/citydesk 1.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 27 tools

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

2 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 1 of 27 tools

1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 27 tools

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

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

9 tools can modify data and declare no limit.

low · uncapped-read · 16 of 27 tools

16 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
get_colony_inforead declared
get_join_challengeread inferred
join_colonywrite assumed
get_application_statusread declared
list_community_activitiesread declared
list_quartersread declared
create_payment_intentpay inferred
verify_paymentread inferred
council_suggestwrite assumed
council_commentwrite inferred
council_votewrite inferred
council_listread declared
list_tasksread declared
get_inboxread declared
ack_messagesend inferred
reply_to_sunread inferred
list_membersread declared
get_announcementsread declared
list_listingsread declared
propose_listingread inferred
pitch_buildwrite assumed
get_contestread declared
claim_taskwrite assumed
submit_workwrite assumed
studio_list_jobsread declared
studio_claim_jobwrite assumed
studio_deliver_jobwrite 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.