Index / storage

CloudSign MCP by usefulapi

io-usefulapi-cloudsign declares 9 capabilities across 9 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.

69/100 exposureElevated

Manifest recorded 2026-11-08 from tools/list on https://cloudsign.usefulapi.io/mcp, published in the official MCP registry as io.usefulapi/cloudsign 1.0.1. 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 9 tools

9 of 9 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 · destructive-uncapped · 6 of 9 tools

6 tools are annotated by the server as destructive (destructiveHint) and declare no limit. In MCP that annotation marks a tool that may make destructive changes rather than only additive ones; it does not say the change cannot be undone.

high · no-expiry · All 9 tools

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

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

3 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.

Tool	Read as	Basis
`cloudsign_list_documents`	`read`	declared
`cloudsign_get_document`	`read`	declared
`cloudsign_list_cabinets`	`read`	declared
`cloudsign_create_document`	`destructive`	declared
`cloudsign_update_document`	`destructive`	declared
`cloudsign_add_participant`	`destructive`	declared
`cloudsign_add_file`	`destructive`	declared
`cloudsign_send_document`	`destructive`	declared
`cloudsign_delete_draft`	`destructive`	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.