LeashIndex Get the report

Index / data

Tensorust Ontology

com-tensorust-ontology declares 38 capabilities across 38 tools, with 3 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.

69/100 exposureElevated

Manifest recorded 2026-11-08 from tools/list on https://shop.tensorust.com/api/mcp, published in the official MCP registry as com.tensorust/ontology 0.6.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 38 tools

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

2 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 2 of 38 tools

2 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 38 tools

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

38 of 38 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.

low · uncapped-read · 36 of 38 tools

36 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
query_ontologyread declared
describe_schemaread declared
lookup_organizationread declared
search_organizationsread declared
get_objectread declared
who_owns_homeread declared
rule_coverageread declared
aircraft_ownerread declared
lender_marksread declared
credit_disagreementsread declared
credit_q3_cutsread declared
exposure_summaryread declared
exposure_institutionread declared
exposure_awardsread declared
exposure_screen_purchasesread declared
exposure_workspaceread declared
exposure_dbgapread declared
perf_summaryread declared
perf_firmread declared
perf_queueread declared
perf_recentread declared
contractor_creditread declared
contractor_credit_watchread declared
agency_credit_exposureread declared
clearinghouse_precheckread declared
clearinghouse_validateread declared
clearinghouse_recordread declared
clearinghouse_programread declared
program_precheckread declared
rip_replace_deadlinesread declared
erate_deadline_checkread declared
road_screen_purchasepay inferred
road_investor_groupread declared
road_purchase_streampay inferred
road_monitor_summaryread declared
list_datasetsread declared
get_datasetread declared
get_dataset_sampleread declared
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.