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.

Tisty

NPM · TISTY-MCP

Agents plan in Markdown and work in tasks with steps, where you can follow and audit every stage.

Available components

npm · tisty-mcp 69
69 Trust /100

Last scanned (8 hours ago)

Scores higher than 40% of npm servers

Category Project Management

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
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 160 tokens (~160/item across 1 items; 1 tools + 0 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

  • 23 Oct 26 69

    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 24 Oct 2026 · Analysed npm/tisty-mcp@1.0.2

Provenance Repository mismatch

The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.

Result Repository mismatch
Ecosystem npm
Reason Repository mismatch
Discovered via Registry attestation endpoint
Source repo rgdevment/mcp-plugins
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/rgdevment/mcp-plugins/.github/workflows/npm.yml@refs/heads/main
Rekor log index 3414795049
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5d3d67869ac53317c48481d25bd1bfc331f65ea550705b3764c735391841b370eaecdd965dd3c5a18b67e4cd83ba683fb15b076991de2e28c58e983c7

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~37 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
install_tisty ~37

Tisty is not installed on this computer, so its tools are missing. Call this for the steps to install it and tell the person.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Tisty MCP server?

Tisty runs locally as an npm package, launched with npx -y tisty-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · tisty-mcp

# add to Claude Code
claude mcp add rgdevment-tisty -- npx -y tisty-mcp
Common questions

What is the Tisty MCP server?

Tisty is an MCP server listed in the public MCP registry as io.github.rgdevment/tisty. Agents plan in Markdown and work in tasks with steps, where you can follow and audit every stage. This page covers its npm package (tisty-mcp).

Is the Tisty MCP server safe to use?

Tisty scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. It declares no install or post-install scripts. 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 Tisty MCP server expose?

Tisty exposes 1 tool: install_tisty. Their descriptions and schemas cost roughly 37 tokens of context every time the server is loaded.

Is the Tisty MCP server still maintained?

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

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