Things (hald) MCP Server
things-mcp
PyPI
v0.8.1
Published by hald — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Things app Model Context Protocol (MCP) server
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (src/things_mcp/url_scheme.py)MTC-SRC-002
In the server's implementation (`src/things_mcp/url_scheme.py:36`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: n in background subprocess.run([ 'osascript', '-e', f'do shell script "open -g \\"{url}\
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/things_mcp/url_scheme.py
Tools 26
Each tool and what it can reach — statically extracted from the published source.
add_areano sensitive capabilityadd_projectno sensitive capabilityadd_todono sensitive capabilitybulk_update_todosno sensitive capabilityget_anytimeno sensitive capabilityget_areasno sensitive capabilityget_headingsno sensitive capabilityget_inboxno sensitive capabilityget_logbookno sensitive capabilityget_projectsno sensitive capability
Show 16 more tools ↓
get_recentno sensitive capabilityget_somedayno sensitive capabilityget_tag_usageno sensitive capabilityget_tagged_itemsno sensitive capabilityget_tagsno sensitive capabilityget_todayno sensitive capabilityget_todosno sensitive capabilityget_trashno sensitive capabilityget_upcomingno sensitive capabilitysearch_advancedno sensitive capabilitysearch_itemsno sensitive capabilitysearch_todosno sensitive capabilityshow_itemno sensitive capabilityupdate_areano sensitive capabilityupdate_projectno sensitive capabilityupdate_todono sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (26 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.8.1 latest |
A 93/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan things-mcp --online --registry pypiOther implementations of Things 7
Independent packages implementing the same tool, scanned with the same engine. Compare all 8 side by side →
MCP server for Things 3 task management via URL Scheme
Model Context Protocol server for Things 3 task management integration
A Model Context Protocol (MCP) server that provides seamless integration with the Things productivity app.
MCP server for controlling Things on macOS
MCP server for Things 3 on macOS — full URL scheme support
MCP server for Things 3 task manager on macOS.
More in Other
A Model Context Protocol server implementation for AdGuard Home that enables AI agents to query and manage DNS records, filtering rules and more
Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.
MCP server with Airtable integration
A free one-minute reset for people, delivered by AI, with no account or personal data.
Access SEC filings efficiently, save time and tokens, and get cited answers.
A smart [MCP](https://modelcontextprotocol.io) server for [AniList](https://anilist.co) that gets your anime/manga taste - not just API calls.