Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

mountable.io

NPM · MOUNTABLE-CLI

Manage persistent AI-agent filesystems. Paid hosted service; Apache-2.0 client.

Available components

+2 this week 86 Trust /100

Last scanned (7 hours ago)

Scores higher than 89% of npm servers

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to writeitai/mountable). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2565 tokens (~150/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_grant" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 7 Nov 26 0
    • Schema quality: 132 → 150 ▼ functional
    • Schema quality: excellent → good functional
    • Package version: 0.8.0 → 0.10.0 functional
  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 886 → 1328 ▼ functional
    • Package version: 0.6.0 → 0.8.0 functional
  • 24 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Nov 2026 · Analysed npm/mountable-cli@0.10.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo writeitai/mountable
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/writeitai/mountable/.github/workflows/release.yml@refs/tags/v0.10.0
Rekor log index 3726251575
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:328d09b5faf0af5c4564056ccfd5f9221abc94a9e1d8c71fd0a4f4ad4a23897e85d289442226e765c002e091d105b92793bf27b26f8875725173a77aa

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~2,485 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_filesystem ~153

Create a filesystem and return it; its id is what tickets and mounts need. Needs a management key (mtblm_) or the login of an owner or admin; an API key gets management_key_required. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. Not idempotent, and names need not be unique: after a timeout or an unknown outcome, call list_filesystems and look for the name before creating again. Never retry blindly. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
namestringyesthe filesystem's name; names need not be unique
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

create_mount_ticket ~452

Create a one-time mount ticket for a sandbox. The result is the mount session with its ticket (single use, valid for minutes) and mount_command, a convenience hint for a person. Agents must construct the documented mountable mount --ticket-stdin --json command with separately quoted arguments, not evaluate mount_command. Pass the ticket through stdin from MOUNTABLE_TICKET, never in an argument list or log. /mnt/mountable is only a default: use a caller-approved writable directory. Use an existing approved CLI; if installation is authorized, choose npm install --global --ignore-scripts mountable-cli or uv tool install mountable, then mountable version. Report setup blockers instead of using sudo or a remote shell installer. Linux mounts need FUSE. Validate the nonempty ticket and selected filesystem ID, then wait for a mounted JSON event matching the intended path, filesystem and mode before using the directory. Retries: pass your own idempotency_key and reuse it when retrying after an unknown outcome. A replay returns the existing session without a ticket. If that session is still requested, its ticket was lost: this tool revokes it and creates a new one with a fresh key, and the result names the old one as replaced_session_id. If it is active or later, the ticket was used: nothing is revoked and the tool fails with ticket_already_used; use a new idempotency_key for another mount. idempotency_conflict means an identical request is in progress. If the outcome is unknown (network_error or outcome_unknown), the error's idempotency_key is the key that request was sent with: retry with exactly that key, even if you did not choose it. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
idempotency_keystring–a key you choose and reuse when retrying this request; a new key for each new mount
max_duration_secondsinteger–the session's maximum duration in seconds; optional (default 12 hours, at most the API key's or login's expiry)
read_onlyboolean–mount read-only

No output schema declared.

No examples provided.

delete_grant ~143

Remove a grant; sessions that relied on it end. Not idempotent: after an unknown outcome, call list_grants to see whether it is gone. Needs a management key (mtblm_) or the login of an owner or admin; an API key gets management_key_required. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
grant_idstringyesthe grant's ID, from list_grants
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

delete_webhook ~115

Delete a webhook; deliveries to its URL stop. Not idempotent: after an unknown outcome, call list_webhooks to see whether it is gone. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
org_idstring–the organisation ID; optional
webhook_idstringyesthe webhook ID, from list_webhooks

No output schema declared.

No examples provided.

enable_webhook ~150

Re-enable a webhook disabled after 24 hours of failed deliveries (disabled_reason failing), once its endpoint works again; the next delivery is usually a files.resync. A webhook disabled as access_revoked cannot be re-enabled (error access_revoked): create a new one with `mountable webhooks create`. Safe to retry. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
org_idstring–the organisation ID; optional
webhook_idstringyesthe webhook ID, from list_webhooks

No output schema declared.

No examples provided.

filesystem_usage ~93

A filesystem's stored bytes and files against its quotas, and its traffic over 30 days. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. Read-only and safe to retry. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

list_api_keys ~171

List the organisation's API keys: id, name, filesystem_id (set for a key limited to one filesystem), expires_at and revoked; never their secrets. Creating a key is not a tool, because its answer is the key's secret: run `mountable api-keys create` or `mountable s3-keys create` (or use the SDKs) where the backend stores it. Needs a management key (mtblm_) or the login of an owner or admin; an API key gets management_key_required. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. Read-only and safe to retry. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

list_filesystems ~88

List the organisation's filesystems (an API key sees those it has a grant on; a management key sees all). org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. Read-only and safe to retry. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

list_grants ~128

List a filesystem's grants: id, principal_type (member, group or api_key), principal_id and mode (ro or rw). Needs a management key (mtblm_) or the login of an owner or admin; an API key gets management_key_required. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. Read-only and safe to retry. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

list_mount_sessions ~91

List a filesystem's live mount sessions (an API key sees those it created). org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. Read-only and safe to retry. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

list_organizations ~44

List the caller's mountable.io organisations (a key has exactly one). Read-only and safe to retry. On rate_limited, wait retry_after seconds before retrying.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_s3_keys ~194

List a filesystem's S3 keys: access_key_id, name, mode, expires_at and revoked; never their secrets. The bucket is the filesystem ID at https://s3.mountable.io (path-style). Creating a key is not a tool, because its answer is the key's secret: run `mountable api-keys create` or `mountable s3-keys create` (or use the SDKs) where the backend stores it. Needs a management key (mtblm_) or the login of an owner or admin; an API key gets management_key_required. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. Read-only and safe to retry. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

list_webhooks ~174

List a filesystem's webhooks: url, path_prefix, state (active or disabled), disabled_reason (failing or access_revoked) and the last delivery's outcome (last_success_at, last_failure, failing_since). Needs read-write access to the filesystem. Creating a webhook and rotating its secret are not tools, because their answer is the signing secret: run `mountable webhooks create` or `rotate-secret` (or use the SDKs) where the receiving backend stores it. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. Read-only and safe to retry. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

revoke_api_key ~123

Revoke an API key; its sessions end and its calls fail. Idempotent and safe to retry. Needs a management key (mtblm_) or the login of an owner or admin; an API key gets management_key_required. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
key_idstringyesthe API key's ID, from list_api_keys
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

revoke_mount_session ~53

Revoke a mount session; its mount stops working. Idempotent and safe to retry. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
session_idstringyesthe mount session ID

No output schema declared.

No examples provided.

revoke_s3_key ~142

Revoke an S3 key; S3 refuses it within 15 seconds. Idempotent and safe to retry. Needs a management key (mtblm_) or the login of an owner or admin; an API key gets management_key_required. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
access_key_idstringyesthe S3 key's access key ID, from list_s3_keys
filesystem_idstringyesthe filesystem ID
org_idstring–the organisation ID; optional

No output schema declared.

No examples provided.

set_grant ~171

Give a member, group or API key access to a filesystem, or change the mode of its grant. Sets the same grant when repeated, so it is safe to retry. Needs a management key (mtblm_) or the login of an owner or admin; an API key gets management_key_required. org_id is optional: a key uses its own organisation, and a login with one organisation uses that one. On rate_limited, wait retry_after seconds before retrying.

NameTypeReqDescription
filesystem_idstringyesthe filesystem ID
modestringyesro or rw
org_idstring–the organisation ID; optional
principal_idstringyesthe member's, group's or API key's ID
principal_typestringyesmember, group or api_key

No output schema declared.

No examples provided.

Install

How do I install the mountable.io MCP server?

mountable.io runs locally as an npm package, launched with npx -y mountable-cli mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mountable-cli

# add to Claude Code
claude mcp add writeitai-mountable -- npx -y mountable-cli mcp
Common questions

What is the mountable.io MCP server?

mountable.io is an MCP server listed in the public MCP registry as io.github.writeitai/mountable. Manage persistent AI-agent filesystems. Paid hosted service; Apache-2.0 client. This page covers its npm package (mountable-cli).

Is the mountable.io MCP server safe to use?

mountable.io scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the mountable.io MCP server expose?

mountable.io exposes 17 tools: create_filesystem, create_mount_ticket, delete_grant, delete_webhook, enable_webhook, and 12 more. Their descriptions and schemas cost roughly 2,485 tokens of context every time the server is loaded.

Is the mountable.io MCP server still maintained?

mountable.io is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the mountable.io MCP server under?

mountable.io declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the mountable.io MCP server?

VerifyMCP ran 16 checks on mountable.io, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.