LeashIndex Get the report

Index / other

Orb Studio news radars

io-github-farenberglord-star-orb-studio declares 44 capabilities across 44 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.

73/100 exposureHigh exposure

Manifest recorded 2026-11-08 from tools/list on https://orbstudio.org/mcp, published in the official MCP registry as io.github.farenberglord-star/orb-studio 1.3.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 44 tools

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

2 tools are classified as irreversible and declare no limit.

high · no-expiry · All 44 tools

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

44 of 44 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 · 5 of 44 tools

5 tools can modify data and declare no limit.

low · uncapped-read · 37 of 44 tools

37 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_changes_sinceread declared
get_radarsread declared
get_radarread declared
get_broadcastread declared
get_agent_indicesread declared
get_david_episodesread declared
get_tracksread declared
get_canvasread declared
emo_robotwrite assumed
make_qrread declared
make_printableread declared
check_headlineread declared
get_ai_pulseread declared
get_promisesread declared
get_violinread declared
get_pricesread declared
get_tariffsread declared
get_qualityread declared
get_receiptsread declared
get_impulsesread declared
vote_top_storywrite assumed
get_vote_resultsread declared
get_historyread declared
get_followupsread declared
report_outcomewrite inferred
get_agent_walletread declared
get_aviation_sensorsread declared
get_roadsread declared
get_sensorsread declared
predictread inferred
get_predictionread declared
get_world_voicesread declared
get_liveread declared
get_placesread declared
ask_davidsend inferred
get_question_statusread declared
get_hall_of_fameread declared
get_bridgeread declared
get_crisisread declared
propose_exit_pathsend inferred
rate_exit_pathwrite assumed
check_agent_accessread declared
register_agentread inferred
investigate_threatwrite 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.