Skip to content

MCP servers › io.github.worldsavepoint › home-screen-organizer

MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19

home-screen-organizer MCP server

Registry name io.github.worldsavepoint/home-screen-organizer

Screen Organizer — the publisher's title

by worldsavepoint · GitHub account (the registry's namespace rule)repository: same ownerSource ↗

Arrange iPhone Home Screen apps, folders, widgets and the App Library from your Mac. — the publisher's description

4 of 5 record checks metversion 1.3.0Pythonstandard input/output

Summary

io.github.worldsavepoint/home-screen-organizer is a local MCP server listed in the official MCP registry at version 1.3.0, under the namespace of the GitHub account worldsavepoint. Its linked repository, github.com/worldsavepoint/ios-homescreen-organizer, belongs to the same GitHub account.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
MCP bundle
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
1.3.0, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-13 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-11-13 to 2026-11-19; 2 in the 90 days before the 2026-11-19 snapshot.
Most recent 2 versions
  • 1.3.0 · 2026-11-19
  • 1.2.0 · 2026-11-13
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.2.0 (published 2026-11-13) → 1.3.0 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.

The publisher’s GitHub release note for v1.3.0 (“Screen Organizer v1.3.0”), published 2026-11-19.

Read the release note (the publisher’s text, shown as plain text)
Screen Organizer 1.3.0 — for iOS

Arrange iPhone and iPad Home Screen apps, folders, widgets and the App Library from your Mac.

- Shared language support for English, Simplified Chinese, Traditional Chinese, Spanish, German, French, Russian and Portuguese. Display names are Screen Organizer, 屏幕整理 and 螢幕整理.
- Every app launch presents the agreement. Read to the end and select agreement to continue; declining exits.
- MCP Setup registers and updates Codex and Claude Code and exports settings for any stdio client. New registrations default to read-only. Configuration, startup checks and client-reported connection states are distinct.
- Advanced MCP exports follow the selected access mode. Device Apply and Restore require the existing write controls.
- Native Apple silicon and Intel apps require macOS 14+. The ad-hoc signed app includes its Python engine, dependencies and native language resources.
- iOS 16+ layout support, per-device drafts and backups, layout comparison, local editor, CLI and MCP server remain available.

Choose `macos-arm64` for Apple silicon or `macos-x86_64` for Intel. Open the matching DMG and drag **Screen Organizer.app** into Applications, or extract the ZIP. Use **System Settings → Privacy & Security → Open Anyway** if macOS requests approval. After an upgrade or move, update the engine path in **MCP Setup** or your client settings. Commands, archive basenames, Registry namespace and saved-data locations stay compatible.

For an MCPB-compatible client, install `home-screen-organizer-1.3.0-macos.mcpb`. It includes both native engines and defaults to `HOMESCREEN_READ_ONLY=1`. To enable MCP Apply and Restore, set both `HOMESCREEN_READ_ONLY=0` and `HOMESCREEN_ALLOW_APPLY=1`, then reconnect. Before Apply, review `diff` and use its latest `apply_token`.

`SHA256SUMS.txt` covers both DMGs, both ZIPs, the MCPB, the Corresponding Source archive and `server.json`. Save it beside your download and run `shasum -a 256 --check --ignore-missing SHA256SUMS.txt`. Native CI verifies both architectures, localized app resources, signatures, checksums and discovery-only MCP startup before publication. Registry metadata retains `io.github.worldsavepoint/home-screen-organizer`.

The bundled Python engine is distributed under GPL version 3 or later. The per-component notices are in the app and MCPB. Download [Corresponding Source and rebuild instructions](https://github.com/worldsavepoint/ios-homescreen-organizer/releases/download/v1.3.0/home-screen-organizer-1.3.0-corresponding-source.tar.gz) for this release.

Original project by [Jonathan Kats](https://github.com/kats1123/homescreen-mcp), distributed under the [MIT License](https://github.com/worldsavepoint/ios-homescreen-organizer/blob/main/LICENSE). Screen Organizer is not affiliated with, endorsed by, or sponsored by Apple Inc. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license.

The release on GitHub

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the MCP bundle is a file to install in a client that supports bundles, not a command.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • Bundle platforms (MCPB). The bundle lists platforms darwin (manifest.json compatibility). Source: read 2026-11-19.
  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/worldsavepoint/ios-homescreen-organizerOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.worldsavepoint
GitHub owner
a personal account (worldsavepoint)
Repository
github.com/worldsavepoint/ios-homescreen-organizer
Stars
1
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-13.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 1 star (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-13). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.worldsavepoint/home-screen-organizer

Answered from the data above

Who publishes io.github.worldsavepoint/home-screen-organizer?

The registry ties the namespace io.github.worldsavepoint to the GitHub account worldsavepoint; only its owner can publish under it. Its linked repository, github.com/worldsavepoint/ios-homescreen-organizer, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.worldsavepoint/home-screen-organizer safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.worldsavepoint/home-screen-organizer been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.worldsavepoint/home-screen-organizer publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.worldsavepoint/home-screen-organizer?

In github.com/worldsavepoint/ios-homescreen-organizer, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-11-19
Hosting type
registry · 2026-11-19
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
registry · 2026-11-19
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Integrity hash
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Signature / provenance
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Dependency advisories
not checked
only npm and PyPI packages are audited
Popularity
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
your machine
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.worldsavepoint/home-screen-organizer: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.worldsavepoint/home-screen-organizer

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.worldsavepoint/home-screen-organizer)](https://protocolprobe.com/mcp/servers/io.github.worldsavepoint/home-screen-organizer)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology