MCP servers › io.github.ppcvote › mindthread
MCP server · registry snapshot 2026-10-26 · last tested 2026-10-26
io.github.ppcvote/mindthread
by ppcvote · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗
Threads scheduler for AI agents: write, schedule and publish posts, review replies, read insights. — the publisher's description
Summary
io.github.ppcvote/mindthread is a remote and local MCP server listed in the official MCP registry at version 0.2.0, under the namespace of the GitHub account ppcvote. Its linked repository, github.com/ppcvote/mindthread-mcp, belongs to the same GitHub account. On 2026-10-26 ProtocolProbe connected to it in read-only mode and read its inventory: 40 tools, 0 resources and 0 prompts.
Record checks
7 of 8 record checks met · 1 not checked
- 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 checked: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: no download figure available
- Not ranked by stars: 0 stars (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
Key facts
- Runs
- remote and local package
- Transport
- standard input/output, streamable HTTP
- Your own values
- for the package, a secret: MINDTHREAD_API_KEY
- Sign-in
- none needed to open a session
- Package
- npm · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 40
- Last tested
- 2026-10-26
Tool list size
10,757 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (40 tools). Counted with Anthropic's token counter on 2026-10-26, from the tool list we read on 2026-10-26. Median across 23,424 counted servers: 2,725 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-10-26 (mindthread.tw), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (0.2.0).
Observed fact
This server accepted a session without any credential and lists 17 tools whose name or declaration suggests they change data (build_material, update_account_settings, apply_account_settings, revert_account_settings_batch, publish and 12 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-26.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-26
- Mode
- read-only (no tool calls)
- Latest version
- 0.2.0, published 2026-10-26 (registry, as of the 2026-10-26 snapshot)
- First listed version
- 2026-10-26 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-26
- Package and repository
- checked 2026-10-26
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. 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
New in the registry: not in the list of 2026-10-24, listed on 2026-10-26 with version 0.2.0 (published 2026-10-26).
Source: the official MCP Registry list on 2026-10-24 and on 2026-10-26.
What it is
What does this server offer?
Observed inventoryNone of its 40 tools are described as changing anything. For 40 the reading was uncertain, so no mark is shown.
- get_meon 21 other servers
“Returns the current plan, this connection's identity and permissions (each permission is allow, ask or deny), remaining daily calls in this connection's pool, remaining patrol points, and the connect…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- list_accountson 40 other servers
“Lists the Threads accounts connected to this MindThread member, with the id to pass as account_id to every other tool.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- get_materialon 4 other servers
“Returns the account's material digest (who the brand is, what it sells, claims, experiences, FAQ, sourced numbers, voice) that every generation path appends to the persona.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
account_idstringrequired“Account id”
- build_material
“Builds or rebuilds the account's material digest from up to 8 https pages of the brand's own website, optional notes with real cases and FAQs (up to 6,000 characters), and the account's top posts.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
4 inputs, 1 required
account_idstringrequired“Account id”urlsarray“Up to 8 https:// pages”notesstring“Real experiences, cases, FAQs (≤6000 chars)”dryboolean“Preview only”
- get_account_settingson 1 other server
“Returns one account's persona, schedule_times, review_before_publish, auto_reply_enabled, auto_thread, content_rules, and the guardrails block: etag (used as if_match on update), last_change, pending…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
account_idstringrequired“Account id”
- update_account_settingson 1 other server
“Changes an account's persona (up to 4,000 characters), schedule_times (comma-separated HH:MM in the account time zone, up to 8), review_before_publish, auto_reply_enabled, auto_thread, auto_link_to_c…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
12 inputs, 1 required
account_idstringrequired“Account id”if_matchstring“guardrails.etag from get_account_settings (optional, 1.9.0)”reasonstring“Why, up to 200 chars (optional, 1.9.0)”dry_runboolean“true = preview only (1.9.0); at most 10 a minute per key”personastring“Brand persona, up to 4000 chars”schedule_timesstring“Comma-separated HH:MM, up to 8”review_before_publishboolean“AI drafts wait for approval”auto_reply_enabledboolean“AI replies to comments on own posts”auto_threadboolean“Auto-split >500 chars”auto_link_to_commentboolean“Links go to first comment”enabledboolean“Master switch”content_rulesobject“Structured rules: max_chars, min_chars, forbid_cta, forbid_hashtags, banned_phrases[], facts[] (allowed numbers as plain sentences), forbid_causal_claims, judg…”
- list_guardrail_changes
“Lists an account's guardrail revisions, newest first (limit 1 to 50, default 20; before for the next page).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
account_idstringrequired“Account id”limitinteger“1-50 (default 20)”beforestring“next_before from the previous page”
- list_account_settings
“Lists every connected Threads account of this member with the settings of the MindThread bulk settings sheet (run mode, auto-posting, review before publish, posting times, audience time zone, random …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
limitinteger“1-100, default 100”cursorstring“next_cursor from the previous page”
- preview_account_settings
“Shows what a batch of settings changes would do and writes nothing: for each account and cell the current value and the new value, warnings (for example no posting time left), and row errors (an acco…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
changesarray“Up to 100 entries: { account_id, set: { column: value }, base?: { column: value you saw } }.”csvstring“Instead of changes: a CSV in the website download format (UTF-8), up to 1 MB”
- apply_account_settings
“Writes a batch of settings changes to up to 100 accounts, each account in its own transaction, and returns a per-row result (ok, unchanged, or failed with the reason) and a batch_id that revert_accou…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
6 inputs, 1 required
changesarray“Up to 100 entries: { account_id, set: { column: value }, base?: { column: value you saw } }.”csvstring“Instead of changes: a CSV in the website download format (UTF-8)”idempotency_keystringrequired“8-200 characters; reuse the same key when retrying the same request”confirm_sensitiveboolean“true when the batch changes run mode, auto-posting or review before publish”preview_idstring“preview_id from preview_account_settings (required from Claude and ChatGPT connections)”reasonstring“Optional note stored with the batch, up to 200 characters”
- revert_account_settings_batch
“Restores the values that one batch changed, within 24 hours of the batch.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
1 input, 1 required
batch_idstringrequired“batch_id from apply_account_settings”
- get_account_settings_batch
“Returns one batch by batch_id: when it was sent and from where (website, API or MCP), counts, whether it can still be reverted, and each row's result with the failure reason.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
batch_idstringrequired“batch_id from apply_account_settings”
Show 28 more tools
- generate_postson 4 other servers
“Generates 1 to 5 post drafts about a topic using a content formula (auto, or an id from list_formulas), the account persona and material, optional reference context (up to 8,000 characters) and a qua…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 1 required
topicstringrequired“What to write about”account_idstring“Persona source”countinteger“1-5”formulastring“auto or a formula id from list_formulas”qualitystring“fast | standard | premium”contextstring“Reference material up to 8000 chars”
- publishon 17 other servers
“Publishes a post to Threads now (publish_now:true) or at publish_at (ISO 8601 with offset).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
7 inputs, 1 required
account_idstringrequired“Account id”textstring“Post text / caption”media_urlsarray“Public https image URLs (1 = image, 2-10 = carousel)”video_urlstring“Public https MP4/MOV”publish_nowboolean“Publish immediately”publish_atstring“ISO 8601 if not publish_now”idempotency_keystring“Optional”
- schedule_text
“Schedules an existing text (up to 500 characters) at publish_at, or at the next best slot with auto_optimize_time:true (the two are mutually exclusive).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
5 inputs, 2 required
account_idstringrequired“Account id”textstringrequired“Text”publish_atstring“ISO 8601 with offset (canonical time field)”schedule_atstring“Deprecated alias of publish_at”auto_optimize_timeboolean“Next best slot (mutually exclusive with publish_at)”
- list_scheduleson 20 other servers
“Lists scheduled posts, optionally filtered by account_id, with status, publish_at, and held_reason when a post was held (for example content_rules_violated or publish_result_unknown).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
account_idstring“Filter by account”
- cancel_scheduleon 4 other servers
“Cancels a scheduled post by id.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
idstringrequired“Post id”
- list_libraryon 6 other servers
“Lists an account's library items by status (queued, draft, published, failed; limit up to 200).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
account_idstringrequired“Account id”statusstring“queued | draft | published | failed”limitinteger“max 200”
- add_library
“Adds up to 20 items (text, optional public https images) to an account's library as queued (default; they publish automatically at schedule_times) or draft (they wait).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
3 inputs, 2 required
account_idstringrequired“Account id”statusstring“queued (default) | draft”itemsarrayrequired“Items”
- delete_library_itemon 2 other servers
“Permanently deletes one queued, draft or archived library item by id.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
idstringrequired“Item id”
- approve_library_item
“Moves one draft into the publishing queue by id.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
idstringrequired“Item id”
- update_library_itemon 3 other servers
“Changes one library item by id: status (archived, draft, queued), text (checked against content_rules), or its place in the queue (position first or last, or an explicit order).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
5 inputs, 1 required
idstringrequired“Item id”statusstring“archived | draft | queued”textstring“New text”positionstring“first | last”orderinteger“Explicit order”
- get_cloud_patrol
“Returns an account's cloud patrol configuration and status: keywords, daily cap, replies sent today, review_before_reply, last scan time.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
account_idstringrequired“Account id”
- set_cloud_patrol
“Creates or updates an account's cloud patrol: keywords (1 to 10; a "#tag" entry searches a topic tag), reply persona, daily_cap (1 to 50 on free and trial, up to 80 on paid plans, up to 150 with a ha…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
7 inputs, 1 required
account_idstringrequired“Account id”keywordsarray“1-10 entries; "#tag" = topic-tag search”personastring“Reply persona”daily_capinteger“reply: 1-50 free/trial, up to 80 paid, up to 150 with add-on; discover: 1 to plan daily haixun points (default)”enabledboolean“Start / stop”review_before_replyboolean“Hold drafts for approval”modestring“"reply" (default): AI drafts and posts replies.”
- cloud_patrol_log
“Lists replies sent by cloud patrol for an account in the last 1 to 7 days, with the target post and the reply text.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
account_idstringrequired“Account id”daysinteger“1-7”
- cloud_patrol_stats
“Returns views and likes earned by cloud patrol replies for an account over 1 to 14 days, with the top replies.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
account_idstringrequired“Account id”daysinteger“1-14”
- list_pending_replies
“Lists cloud patrol reply drafts for an account by status (pending by default; also sent, rejected, expired).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
account_idstringrequired“Account id”statusstring“pending (default) | sent | rejected | expired”
- approve_pending_reply
“Approves one drafted cloud patrol reply by id and sends it to Threads now, optionally with an edited reply text that passes the same quality gates as generated text.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
2 inputs, 1 required
idstringrequired“Pending id”replystring“Optional edited reply”
- reject_pending_reply
“Rejects one drafted cloud patrol reply by id with an optional note.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 1 required
idstringrequired“Pending id”reasonstring“Optional note”
- list_eventson 112 other servers
“Returns the member's event feed for the last 7 days, newest first (limit 1 to 200): post.published, post.failed, reply.sent, patrol.reply, patrol.pending, token.expiring, usage.threshold, approval.de…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
sincestring“ISO 8601”typesstring“Comma-separated event names”limitinteger“1-200”
- analytics_insightson 1 other server
“Returns views, likes, replies and followers for one account over a period (7d, 30d; default 30d).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
account_idstringrequired“Account id from list_accounts, or "all" for the organization-wide aggregate”periodstring“e.g.”
- list_formulason 2 other servers
“Lists the content formulas that generate_posts accepts, with id and a short description of each.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- get_playbookon 15 other servers
“Returns the operating playbook for running an account through this server: the daily loop, how confirmation requests work, quotas, and the review checklist.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- connect_account_link
“Returns a Threads OAuth link for the user to open in a browser to connect a new Threads account to this member.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
Takes no inputs.
- disable_this_key
“Permanently disables the key or connection making this call.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
Takes no inputs.
- get_my_usageon 5 other servers
“Returns this connection's own usage for the last 1 to 30 days (days=1 is today since 00:00 Asia/Taipei): summary (calls, units, errors, by_endpoint) and recent calls (request_id, endpoint, status, un…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
daysinteger“1-30 (default 1 = today)”limitinteger“1-100 (default 50)”cursorstring“next_cursor from the previous result”
- get_approvalon 8 other servers
“Returns one confirmation request created by this connection, by id (apr_...): status (pending, approved, executed, failed, denied, expired, cancelled), the action summary, how the owner decided (deci…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
idstringrequired“Approval id (apr_...) from error.approval_id”
- bulk_archive_library
“Archives up to 50 library items by id in one call.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
idsarrayrequired“Item ids (max 50)”
- bulk_delete_library
“Permanently deletes up to 50 queued, draft or archived library items by id in one call.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
idsarrayrequired“Item ids (max 50)”
- bulk_queue_library
“Moves up to 50 drafts into the publishing queue by id in one call; they publish automatically at the account's schedule_times.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
idsarrayrequired“Draft ids (max 50)”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-26.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 96
- Tools with a description
- 100% of 40
- Typical description length
- 384 characters
The tool set
Counted from the listing
- Tools
- 40
- Size of the list
- about 9,873 tokens for an agent to load (characters ÷ 4)
- Naming
- 39 of 40 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 40 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the npm package mindthread-mcp
This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"mindthread": {
"command": "npx",
"args": [
"-y",
"mindthread-mcp@0.2.0"
],
"env": {
"MINDTHREAD_API_KEY": "<MINDTHREAD_API_KEY>"
}
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mindthread": {
"command": "npx",
"args": [
"-y",
"mindthread-mcp@0.2.0"
],
"env": {
"MINDTHREAD_API_KEY": "<MINDTHREAD_API_KEY>"
}
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"mindthread": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mindthread-mcp@0.2.0"
],
"env": {
"MINDTHREAD_API_KEY": "${input:mindthread-api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "mindthread-api-key",
"description": "MINDTHREAD_API_KEY",
"password": true
}
]
}Claude Code
claude mcp add --env "MINDTHREAD_API_KEY=<MINDTHREAD_API_KEY>" --transport stdio mindthread -- npx -y mindthread-mcp@0.2.0
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"mindthread": {
"command": "npx",
"args": [
"-y",
"mindthread-mcp@0.2.0"
],
"env": {
"MINDTHREAD_API_KEY": "<MINDTHREAD_API_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"mindthread": {
"command": "npx",
"args": [
"-y",
"mindthread-mcp@0.2.0"
],
"env": {
"MINDTHREAD_API_KEY": "<MINDTHREAD_API_KEY>"
}
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.mindthread] command = "npx" args = ["-y", "mindthread-mcp@0.2.0"] [mcp_servers.mindthread.env] "MINDTHREAD_API_KEY" = "<MINDTHREAD_API_KEY>"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"mindthread": {
"command": "npx",
"args": [
"-y",
"mindthread-mcp@0.2.0"
],
"env": {
"MINDTHREAD_API_KEY": "<MINDTHREAD_API_KEY>"
}
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -e "MINDTHREAD_API_KEY=<MINDTHREAD_API_KEY>" -- npx -y mindthread-mcp@0.2.0
- Replace <MINDTHREAD_API_KEY> with your own values; the entry marks MINDTHREAD_API_KEY as secret, so keep the file out of version control.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-26 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://mindthread.tw/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mindthread": {
"url": "https://mindthread.tw/api/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"mindthread": {
"type": "http",
"url": "https://mindthread.tw/api/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"mindthread","type":"http","url":"https://mindthread.tw/api/mcp"}'Claude Code
claude mcp add --transport http mindthread https://mindthread.tw/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"mindthread": {
"type": "streamableHttp",
"url": "https://mindthread.tw/api/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"mindthread": {
"httpUrl": "https://mindthread.tw/api/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.mindthread] url = "https://mindthread.tw/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"mindthread": {
"url": "https://mindthread.tw/api/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mindthread.tw/api/mcp --transport http
- Optional settings the entry also lists (left out above): Authorization.
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
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.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.2.0
- Latest stable
- 0.2.0
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-10-26. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-10-26 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-3cKDU19pyDi7Kub9J…
- Signature
- signed
- License
- MIT
Source: the package registry · 2026-10-26.
Does the registry listing match what we found?
Feature #6The 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 says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint mindthread.tw/api/mcp | Session opened | matches | our test · 2026-10-26 |
| A secret is declared as required | Opened a session without any credential | differs | our test · 2026-10-26 |
| Version 0.2.0 on npm | Exists and can be installed | matches | npm · 2026-10-26 |
| Repository github.com/ppcvote/mindthread-mcp | Opens publicly | matches | api.github.com · 2026-10-26 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.ppcvote
- GitHub owner
- a personal account (ppcvote)
- Build record
- signed
- Repository
- github.com/ppcvote/mindthread-mcp
- Stars
- 0
- Repository age
- 181–365 days
- Last push
- 0–30 days ago
- Archived
- no
Source: the registry entry and api.github.com · 2026-10-26.
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 rating7 of 8 record checks met · 1 not checked
- Not ranked by downloads: no download figure available
- Not ranked by stars: 0 stars (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 checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-26. 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. How each check works · Leaderboards
Common questions about io.github.ppcvote/mindthread
Answered from the data aboveWho publishes io.github.ppcvote/mindthread?
The registry ties the namespace io.github.ppcvote to the GitHub account ppcvote; only its owner can publish under it. Its linked repository, github.com/ppcvote/mindthread-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.ppcvote/mindthread safe to install?
We do not rate servers as safe or unsafe. 7 of its 8 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. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.github.ppcvote/mindthread need an API key or sign-in?
It opened a session without any credential on 2026-10-26. The registry entry declares a required secret.
Has io.github.ppcvote/mindthread been security tested?
Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.
Is the listed version current?
Yes. The registry lists 0.2.0, the latest stable release on npm.
Where is the source code of io.github.ppcvote/mindthread?
In github.com/ppcvote/mindthread-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA 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
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
3 exercised12 not run (reason given)3 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-10-26, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,383 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 40 tools, 0 resources, 0 prompts.
- 4,495 msFinished: 3 checks exercised.
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.
“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.ppcvote/mindthread: MCP server record.” Data checked 2026-10-26. https://protocolprobe.com/mcp/servers/io.github.ppcvote/mindthread
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
[](https://protocolprobe.com/mcp/servers/io.github.ppcvote/mindthread)
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.
Write to hello@protocolprobe.com · corrections log · methodology