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.

Apple Files

PYPI · APPLE-FILES-MCP · 2 COMPONENTS

Inspect and manage local files and folders inside allowed roots on macOS.

−1 this week 91 Trust /100

Last scanned (29 minutes ago)

Scores higher than 94% of PyPI 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
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to JonathanRReed/Apple-MCPs). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 891 tokens (~33/item across 27 items; 23 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 25 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
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.

  • 16 Oct 26 +1

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

  • 15 Oct 26 +40
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → 0.87 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → 67 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Package version: 1.0.5 → 1.1.2 functional
  • 14 Oct 26 0
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → 0.83 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 67 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Package version: 1.0.5 → 1.1.2 functional
    • Package version: 1.0.5 → 1.1.1 functional
  • 13 Oct 26 0
    • Package version: 1.1.0 → 1.1.1 functional
  • 12 Oct 26 −42
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 67 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 1.0.5 → 1.1.0 functional
  • 4 Oct 26 0
    • Stability: 0.97 → pass security
  • 3 Oct 26 +1

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

  • 2 Oct 26 −1
    • Stability: pass → 0.93 functional
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 17 Oct 2026 · Analysed pypi/apple-files-mcp@1.1.2

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo JonathanRReed/Apple-MCPs
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/JonathanRReed/Apple-MCPs/.github/workflows/release.yml@refs/tags/v1.1.2
Rekor log index 3252400217
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:b0072b25a262bdb216a62cbe0659f4f80c7d7412234a0fd78597c70f6de6e535

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 23 exposed · ~745 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
files_add_tags ~41

Add Finder tags to a file or folder. Requires safe_manage or full_access safety mode.

NameTypeReqDescription
pathstringyes–
tagsarrayyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_create_folder ~24

Create a folder inside the allowed roots.

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_delete_path ~33

Delete a file or empty folder inside the allowed roots. Requires full_access safety mode.

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_get_file_info ~29

Get metadata for a file or folder inside the allowed roots.

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_get_icloud_status ~30

Report whether local iCloud Drive is available and whether it is part of the current allowed roots.

Input schema present but exposes no named parameters.

NameTypeReqDescription
result–yes–

No examples provided.

files_get_prompt ~33

Fallback prompt rendering tool for tool-only MCP clients.

NameTypeReqDescription
arguments_json–––
namestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

files_get_tags ~29

Read Finder tags for a file or folder inside the allowed roots.

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_health ~16

Report the active Apple Files MCP configuration.

Input schema present but exposes no named parameters.

NameTypeReqDescription
allowed_rootsarrayyes–
capabilitiesarrayyes–
okboolean––
safety_modestringyes–
server_namestringyes–
supportsarrayyes–
transportstringyes–
versionstringyes–

No examples provided.

files_list_allowed_roots ~21

List the file system roots the server may access.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countintegeryes–
okboolean––
rootsarrayyes–

No examples provided.

files_list_directory ~26

List files and folders inside an allowed directory path.

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_list_prompts ~21

Fallback prompt discovery tool for tool-only MCP clients.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

files_list_recent_locations ~33

List recently active parent folders across the allowed roots, including iCloud-aware metadata.

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
result–yes–

No examples provided.

files_move_path ~35

Move or rename a file or folder inside the allowed roots.

NameTypeReqDescription
destinationstringyes–
sourcestringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_open_path ~35

Open a file or folder in the default app. Requires safe_manage or full_access safety mode.

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_permission_guide ~22

Explain how Apple Files MCP access is scoped on this machine.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

files_read_text_file ~37

Read a UTF-8 text file inside the allowed roots.

NameTypeReqDescription
max_bytesinteger––
pathstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_recent_files ~25

List recently modified files inside the allowed roots.

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
result–yes–

No examples provided.

files_remove_tags ~41

Remove Finder tags from a file or folder. Requires safe_manage or full_access safety mode.

NameTypeReqDescription
pathstringyes–
tagsarrayyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_reveal_in_finder ~36

Reveal a file or folder in Finder. Requires safe_manage or full_access safety mode.

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_search_files ~39

Search file and folder names inside the allowed roots.

NameTypeReqDescription
base_path–––
limitinteger––
querystringyes–
NameTypeReqDescription
result–yes–

No examples provided.

files_set_tags ~41

Replace Finder tags for a file or folder. Requires safe_manage or full_access safety mode.

NameTypeReqDescription
pathstringyes–
tagsarrayyes–
NameTypeReqDescription
result–yes–

No examples provided.

get_tool_info ~48

Load the full schema, examples, and metadata for one tool from this server.

NameTypeReqDescription
include_examplesboolean––
include_schemaboolean––
namestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

search_tools ~50

Search this server's tool catalog by keyword, alias, or domain tag.

NameTypeReqDescription
domain_tags–––
limitinteger––
modestring––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Apple Files MCP server?

Apple Files runs locally as a PyPI package, launched with uvx apple-files-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · apple-files-mcp

# add to Claude Code
claude mcp add jonathanrreed-apple-files-mcp -- uvx apple-files-mcp
Common questions

What is the Apple Files MCP server?

Apple Files is an MCP server listed in the public MCP registry as io.github.JonathanRReed/apple-files-mcp. Inspect and manage local files and folders inside allowed roots on macOS. This page covers its PyPI package (apple-files-mcp).

Is the Apple Files MCP server safe to use?

Apple Files scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. 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 Apple Files MCP server expose?

Apple Files exposes 23 tools: files_health, files_permission_guide, files_list_allowed_roots, files_list_directory, files_search_files, and 18 more. Their descriptions and schemas cost roughly 745 tokens of context every time the server is loaded.

Is the Apple Files MCP server still maintained?

Apple Files is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Apple Files MCP server under?

Apple Files declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.