Things Poke MCP Server

things-poke npm v0.1.1

Published by ysmaliak — 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.

Local Things 3 MCP server for Poke

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

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:

PointsAdoption-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 2

high Shell/command execution in server code (dist/appleScript.js)MTC-SRC-002

In the server's implementation (`dist/appleScript.js:1`): 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: rt { spawn } from "node:child_process"; export class AppleScriptError extends Error { kind; constructor(kind, me

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 dist/appleScript.js

high Shell/command execution in server code (dist/cli.js)MTC-SRC-002

In the server's implementation (`dist/cli.js:3`): 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: ile, spawn } from "node:child_process"; import { access, chmod, copyFile, mkdir, readFile, realpath, rm, writeFile } fro

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 dist/cli.js

Tools 24

Each tool and what it can reach — statically extracted from the published source.

  • get_todosreads sensitive data
  • create_areano sensitive capability
  • create_projectno sensitive capability
  • create_tagno sensitive capability
  • create_todono sensitive capability
  • delete_areano sensitive capability
  • delete_projectno sensitive capability
  • delete_tagno sensitive capability
  • delete_todono sensitive capability
  • edit_todo_in_thingsno sensitive capability
Show 14 more tools ↓
  • empty_trashno sensitive capability
  • get_areasno sensitive capability
  • get_listsno sensitive capability
  • get_projectsno sensitive capability
  • get_tagsno sensitive capability
  • get_things_infono sensitive capability
  • log_completed_nowno sensitive capability
  • move_todono sensitive capability
  • open_quick_entryno sensitive capability
  • search_in_thingsno sensitive capability
  • search_todosno sensitive capability
  • show_in_thingsno sensitive capability
  • update_projectno sensitive capability
  • update_todono sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v0.1.1 latest A 93/100 2 1.13.0 2026-09-07

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/things-poke/badge.svg)](https://mcptrustchecker.com/registry/things-poke)
HTML
<a href="https://mcptrustchecker.com/registry/things-poke"><img src="https://mcptrustchecker.com/registry/things-poke/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/things-poke/badge.json via https://img.shields.io/endpoint?url=…

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-poke --online

Use the free API → How scoring works

More in Productivity & Workflow