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.

Shortcut Forge (Apple Shortcuts MCP)

PYPI · SHORTCUT-FORGE

Apple Shortcuts MCP: build, lint and sign iOS Shortcuts (.shortcut) from Claude, Codex or any LLM.

Available components

77 Trust /100

Last scanned (14 hours ago)

Scores higher than 75% of PyPI servers

Category Developer Tools

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 hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Hyunki6040/shortcut-forge). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1047 tokens (~87/item across 12 items; 10 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 (30% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "shortcut_publish" implies "publish" 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 12 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 15 Oct 26 +28
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Tool coverage: 30 functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
  • 14 Oct 26 49

    First indexed and scored.

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/shortcut-forge@0.2.1

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 Hyunki6040/shortcut-forge
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Hyunki6040/shortcut-forge/.github/workflows/release.yml@refs/tags/v0.2.1
Rekor log index 3251571142
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:1025695c5d5405554946547ee765bdc572e749d0cda7289ee9b0f4bc4755480c

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

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

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

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~731 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
shortcut_build ~98

Build a .shortcut from a JSON spec ({"name": ..., "actions": [...]}) and lint it. See shortcut_reference(topic="spec") for every step type. Set sign=true on macOS to produce an importable signed file. Returns paths, action count and lint findings (fix all errors).

NameTypeReqDescription
output_path–––
signboolean––
sign_modestring––
specobjectyes–

No output schema declared.

No examples provided.

shortcut_from_template ~109

Generate a shortcut from a ready-made template. template: "supplement-tracker" (multi-user supplements -> Apple Health + self-maintaining reminders, 7-day Apple Intelligence report) or "water-log". config: template config; omit to get the example. Call shortcut_reference(topic="templates") to see each template's config shape.

NameTypeReqDescription
config–––
output_path–––
signboolean––
sign_modestring––
templatestringyes–

No output schema declared.

No examples provided.

shortcut_inspect ~31

Return an indented, human-readable outline of an unsigned .shortcut file.

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

shortcut_library ~87

Browse the community shortcut library (20+ ready shortcuts: productivity, health, money, dev, home...). No slug: list entries matching `query` (name/description/tags). With slug: return its meta, its spec (or template config) to use as a starting point, and the signed download link if published.

NameTypeReqDescription
querystring––
slug–––

No output schema declared.

No examples provided.

shortcut_lint ~37

Lint an unsigned .shortcut file against known on-device failure patterns (rules SF000-SF013).

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

shortcut_llm_prompt ~31

Return a copy-paste system prompt that teaches any chatbot (ChatGPT, Gemini...) to write specs.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

shortcut_publish ~107

macOS: build + sign + write manifest.json so installed copies can update themselves. Adds a daily update check (spec.update_manifest = base_url/manifest.json) to the shortcut. Host the two output files at base_url (GitHub raw/Pages/S3). Bump `version` for every release.

NameTypeReqDescription
base_urlstringyes–
notesstring––
output_dir–––
specobjectyes–
versionstringyes–

No output schema declared.

No examples provided.

shortcut_reference ~40

Docs for building shortcuts. topic: spec | pitfalls | lint-rules | health-types | templates | library | ios27.

NameTypeReqDescription
topicstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

shortcut_sign ~59

Sign a .shortcut with the macOS `shortcuts` CLI so iOS can import it. mode: anyone | people-who-know-me.

NameTypeReqDescription
modestring––
output_path–––
pathstringyes–

No output schema declared.

No examples provided.

shortcut_submit ~132

Package a shortcut for the open-source library (github.com/Hyunki6040/shortcut-forge/library). Validates the spec and metadata, lints it, and returns the exact files plus the git/gh commands to open a pull request. Encourage the user to run it on their iPhone first and fill `verified_on`.

NameTypeReqDescription
authorstringyes–
categorystringyes–
descriptionstringyes–
description_kostring––
namestringyes–
slugstringyes–
specobjectyes–
tags–––

No output schema declared.

No examples provided.

Install

How do I install the Shortcut Forge (Apple Shortcuts MCP) server?

Shortcut Forge (Apple Shortcuts MCP) runs locally as a PyPI package, launched with uvx shortcut-forge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · shortcut-forge

# add to Claude Code
claude mcp add hyunki6040-shortcut-forge -- uvx shortcut-forge
Common questions

What is the Shortcut Forge (Apple Shortcuts MCP) server?

Shortcut Forge (Apple Shortcuts MCP) is listed in the public MCP registry as io.github.Hyunki6040/shortcut-forge. Apple Shortcuts MCP: build, lint and sign iOS Shortcuts (.shortcut) from Claude, Codex or any LLM. This page covers its PyPI package (shortcut-forge).

Is the Shortcut Forge (Apple Shortcuts MCP) server safe to use?

Shortcut Forge (Apple Shortcuts MCP) scores 77 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 Shortcut Forge (Apple Shortcuts MCP) server expose?

Shortcut Forge (Apple Shortcuts MCP) exposes 10 tools: shortcut_build, shortcut_from_template, shortcut_lint, shortcut_inspect, shortcut_sign, and 5 more. Their descriptions and schemas cost roughly 731 tokens of context every time the server is loaded.

Is the Shortcut Forge (Apple Shortcuts MCP) server still maintained?

Shortcut Forge (Apple Shortcuts MCP) 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 Shortcut Forge (Apple Shortcuts MCP) server under?

Shortcut Forge (Apple Shortcuts MCP) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.