MCP servers › io.github.SupportPages-io › wtfm
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.SupportPages-io/wtfm
Your coding agent writes the user docs from your codebase, screenshots included. — the publisher's description
Summary
io.github.SupportPages-io/wtfm is a local MCP server listed in the official MCP registry at version 0.5.7. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 47 tools, 0 resources and 0 prompts.
Record checks
- 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
- met: 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
- met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #7,364 of 15,112 packages by monthly downloads, tied with 14 others
- #1,078 of 22,952 repositories by GitHub stars, tied with 12 others
- #848 of 1,074 packages meeting all 9 record checks, by downloads, tied with 2 others
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- local package
- Transport
- standard input/output
- Package
- npm · listed version current
- License
- Apache-2.0
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 47
- Described as changing data
- 25 of 47 toolsAI-classified
- Mainly works on
- files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
- Topic
- developer-toolsAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- 25 tools are described as changing something (supportpages_init, supportpages_publish, supportpages_request_permissions, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
- Its package is signed and carries a build record naming its source.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 0.5.7, published 2026-10-21 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-19 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-10-19 to 2026-10-21; 3 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 3 versions
0.5.7· 2026-10-210.5.6· 2026-10-200.5.5· 2026-10-19
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.5.7 (published 2026-10-21).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.
25 of 47 tools are described as changing something (creating, editing, deleting, sending or running). For 10 the reading was uncertain, so no mark is shown.
- supportpages_initdescribed as changing data
“Sign this device in to SupportPages.io if needed and link the current workspace to a help centre.”
Publisher declares: read-only no · destructive yes · open-world yes
4 inputs
workspacestring“Select an absolute client workspace root only when discovery is ambiguous.”project_idstring“Help centre to link this workspace to when it is not linked yet.”signupboolean“True when the user chose to create a free SupportPages.io account: browser approval starts on registration instead of sign-in.”host_localboolean“True when the user explicitly asked to sign in or use a help centre from a folder that saves articles locally.”
- supportpages_publishcreates or changes datadescribed as changing data
“Host saved local articles on a SupportPages.io help centre.”
Publisher declares: read-only no · destructive no · open-world yes
4 inputs
workspacestringproject_idstring“The help centre the user selected; cannot replace an existing destination.”slugsarray“Saved article slugs selected by the user.”signupboolean“True when the user chose to create a free SupportPages.io account rather than sign in.”
- supportpages_statusreads or searches
“Check article progress and draft links, the signed-in account, browser approval progress and access to the linked help centre.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
workspacestring“Select a client workspace root when discovery is ambiguous.”run_idstring“Inspect a particular article run; otherwise shows the active or most recent run.”
- supportpages_doctorreads or searches
“Check configuration and local generation prerequisites without exposing credentials.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
- supportpages_get_capabilitiesreads or searches
“Check whether an action can run and return its execution location or next setup step.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
workspacestringactionstringrequiredarticle_idstring
- supportpages_request_permissionscontrols a browser or desktopdescribed as changing data
“Request explicit browser consent for missing Writer permissions.”
Publisher declares: read-only no · destructive yes · open-world yes
4 inputs, 2 required
workspacestringactionstringrequiredarticle_idstringscopesarrayrequired
- supportpages_find_article_gapsruns code or commandsdescribed as changing data
“Run hosted documentation analysis and return a durable operation.”
Publisher declares: read-only no · destructive yes · open-world yes
4 inputs
workspacestringrequest_idstring“Use a new UUID for a new intentional request, and reuse it for recovery.”prefer_backgroundbooleanopen_when_readyboolean
- supportpages_suggest_sectionsruns code or commandsdescribed as changing data
“Run hosted documentation analysis and return a durable operation.”
Publisher declares: read-only no · destructive yes · open-world yes
4 inputs
workspacestringrequest_idstring“Use a new UUID for a new intentional request, and reuse it for recovery.”prefer_backgroundbooleanopen_when_readyboolean
- supportpages_recommend_articlesruns code or commandsdescribed as changing data
“Run hosted documentation analysis and return a durable operation.”
Publisher declares: read-only no · destructive yes · open-world yes
4 inputs
workspacestringrequest_idstring“Use a new UUID for a new intentional request, and reuse it for recovery.”prefer_backgroundbooleanopen_when_readyboolean
- supportpages_list_sectionsreads or searches
“List persisted suggestions with IDs and review state.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
workspacestringafter_idstring
- supportpages_review_sectionscreates or changes datadescribed as changing data
“Accept or reject one selected suggestion.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 2 required
workspacestringidstringrequireddecisionstringrequired
- supportpages_list_recommendationsreads or searches
“List persisted suggestions with IDs and review state.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
workspacestringafter_idstring
Show 35 more tools
- supportpages_review_recommendationscreates or changes datadescribed as changing data
“Accept or reject one selected suggestion.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 2 required
workspacestringidstringrequireddecisionstringrequired
- supportpages_create_video_walkthroughgenerates contentdescribed as changing data
“Create a hosted video walkthrough for a completed eligible article.”
Publisher declares: read-only no · destructive yes · open-world yes
6 inputs
workspacestringarticle_idstringexpected_revisionstringrequest_idstring“Use a new UUID for a new intentional request, and reuse it for recovery.”prefer_backgroundbooleanopen_when_readyboolean
- supportpages_setup_hosteddescribed as changing data
“Sign in or create an account and connect a repository for the original requested hosted action.”
Publisher declares: read-only no · destructive no · open-world yes
6 inputs, 1 required
workspacestringproject_idstringarticle_idstringsignupboolean“True when the user chose to create a free SupportPages.io account rather than sign in.”resume_argumentsobjectactionstringrequired
- supportpages_connect_repositorydescribed as changing data
“Compatibility alias for supportpages_setup_hosted.”
Publisher declares: read-only no · destructive no · open-world yes
7 inputs
workspacestringproject_idstringarticle_idstringsignupboolean“True when the user chose to create a free SupportPages.io account rather than sign in.”resume_argumentsobjectactionstringfeaturestring
- supportpages_set_repository_reminderscreates or changes datadescribed as changing data
“Enable or disable optional repository connection reminders when the user asks.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 1 required
workspacestringenabledbooleanrequired
- supportpages_set_hosting_reminderscreates or changes datadescribed as changing data
“Enable or disable the optional hosting reminders shown after an article is saved locally, when the user asks.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 1 required
workspacestringenabledbooleanrequired
- supportpages_set_telemetrycreates or changes datadescribed as changing data
“Turn the Writer’s anonymous usage counts and crash reports on or off for this device when the user asks.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
enabledbooleanrequired
- supportpages_list_projectsreads or searches
“List accessible SupportPages.io help centres.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
- supportpages_create_projectcreates or changes datadescribed as changing data
“Create a SupportPages.io project for local generation; no repository connection is needed.”
Publisher declares: read-only no · destructive yes · open-world yes
2 inputs, 2 required
namestringrequiredsubdomainstringrequired
- supportpages_bind_workspacecreates or changes datadescribed as changing data
“Bind this configured local workspace to a remote project.”
Publisher declares: read-only no · destructive yes · open-world yes
1 input, 1 required
project_idstringrequired
- supportpages_get_contextreads or searches
“Fetch writing guidance, sections, article inventory and current account-wide article hosting capacity with billing and management links.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
- supportpages_get_local_planreads or searches
“Read validated local project detection context.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
- supportpages_create_articlegenerates contentdescribed as changing data
“Create one illustrated article using the permitted execution location.”
Publisher declares: read-only no · destructive yes · open-world yes
9 inputs
workspacestringtitlestringrecommendation_idstringdescriptionstringarticle_typestringpublishbooleanrequest_idstring“Use a new UUID for a new intentional request, and reuse it for recovery.”prefer_backgroundbooleanopen_when_readyboolean
- supportpages_edit_articlecreates or changes datadescribed as changing data
“Edit an existing article according to instructions.”
Publisher declares: read-only no · destructive yes · open-world yes
7 inputs, 3 required
workspacestringarticle_idstringrequiredexpected_revisionstringrequiredinstructionsstringrequiredrequest_idstring“Use a new UUID for a new intentional request, and reuse it for recovery.”prefer_backgroundbooleanopen_when_readyboolean
- supportpages_get_operationreads or searches
“Check a hosted operation once, when the user asks how it is going or after a client restart; it never resubmits work.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
workspacestringoperation_idstringwait_msinteger
- supportpages_retry_operationruns code or commandsdescribed as changing data
“Explicitly retry a failed hosted operation after fixing its reported prerequisite.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 2 required
workspacestringoperation_idstringrequiredexpected_attemptintegerrequired
- supportpages_prepare_articlecreates or changes datadescribed as changing data
“Check account-wide article hosting capacity before preparing a writing task and self-contained task brief.”
Publisher declares: read-only no · destructive yes · open-world yes
8 inputs, 1 required
workspacestringtitlestringrequireddescriptionstringarticle_typestringsection_idstringallow_duplicateboolean“Only true when the user explicitly wants a separate article despite an existing article with the same title.”prefer_backgroundboolean“Override the saved personal preference only when explicitly requested.”open_when_readyboolean“Override the saved personal preference only when explicitly requested.”
- supportpages_update_runcreates or changes datadescribed as changing data
“Report actual host task start, failure, interruption or cancellation.”
Publisher declares: read-only no · destructive no · open-world no
6 inputs, 2 required
workspacestringrun_idstringrequiredeventstringrequiredexecution_modestringhost_task_idstringstoppedboolean
- supportpages_retry_articledescribed as changing data
“Resume the same partial article after stopping the previous writer.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 2 required
workspacestringrun_idstringrequiredstoppedbooleanrequired
- supportpages_complete_articlecreates or changes datadescribed as changing data
“After successful host writing and validation, finalize and upload this run as a draft.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 2 required
workspacestringrun_idstringrequiredcompletedbooleanrequired
- supportpages_cancel_rundeletesdescribed as changing data
“Release a generation run after the host agent has stopped.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 1 required
workspacestringrun_idstringrequiredstoppedboolean
- supportpages_syncreads or searches
“Refresh remote project settings, articles and video walkthroughs, including remote-only resources, publication/sharing, review links and changes.”
Publisher declares: read-only no · destructive no · open-world yes
1 input
workspacestring
- supportpages_list_walkthroughsreads or searches
“List existing hosted video walkthroughs, including videos created in the browser.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
workspacestringarticle_idstringafter_idstringthrough_idstring
- supportpages_get_walkthroughreads or searches
“Read a hosted video walkthrough by ID: current generation and public visibility, revision, assets, transcript when available, and private review/playback links.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
workspacestringwalkthrough_idstringrequired
- supportpages_list_local_articlesreads or searches
“List current local article files when signed out or in local mode, without login or network requests.”
Publisher declares: read-only no · destructive no · open-world yes
1 input
workspacestring
- supportpages_validate_article
“Validate article schema, image references and available lint results.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
artifact_dirstringrequired“Workspace-relative article output directory.”
- supportpages_preview_articlecalculates or converts
“Create a self-contained local preview.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
artifact_dirstringrequired“Workspace-relative article output directory.”
- supportpages_finalize_articlecreates or changes datadescribed as changing data
“Snapshot a successfully completed article for upload.”
Publisher declares: read-only no · destructive no · open-world no
4 inputs, 2 required
artifact_dirstringrequired“Workspace-relative article output directory.”completedbooleanrequiredrun_idstringsection_idstring
- supportpages_upload_draft
“Upload the finalized article bundle to the bound SupportPages.io project as an unreviewed draft.”
Publisher declares: read-only no · destructive yes · open-world yes
1 input, 1 required
slugstringrequired
- supportpages_get_article
“Read remote content, revision and publication state for an article in the bound project.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
article_idstringrequired
- supportpages_list_articles
“List existing support articles.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
workspacestringafter_idstringsourcestring
- supportpages_update_article
“Save an exact content update using the current revision from get_article.”
Publisher declares: read-only no · destructive yes · open-world yes
6 inputs, 2 required
workspacestringarticle_idstringrequiredexpected_revisionstringrequiredstructured_contentobjectbodystringtitlestring
- supportpages_publish_article
“Make an article visible in the hosted help centre.”
Publisher declares: read-only no · destructive no · open-world yes
4 inputs, 1 required
workspacestringarticle_idstringslugstringexpected_revisionstringrequired
- supportpages_unpublish_article
“Remove an article from the public help centre while retaining it as a draft.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 2 required
workspacestringarticle_idstringrequiredexpected_revisionstringrequired
- supportpages_delete_article
“Soft-delete the selected article using its latest revision.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 2 required
workspacestringarticle_idstringrequiredexpected_revisionstringrequired
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-23.
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
- Says what the tool does
- 100% of 40 tools
- Says what it returns
- 65% of 37 tools
- States limits, defaults or errors
- 3% of 40 tools
- Says when to use it
- 100% of 23 tools
- Items covered per tool
- 2.5 of 4 on average
Counted from the listing
- Parameters with a description
- 16% of 146
- Tools with a description
- 100% of 47
- Typical description length
- 279 characters
The tool set
Counted from the listing
- Tools
- 47
- Size of the list
- about 13,688 tokens for an agent to load (characters ÷ 4)
- Naming
- 47 of 47 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 40 of 47 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, comparing tools within groups of 40. 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 @supportpages.io/wtfm
Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"wtfm": {
"command": "npx",
"args": [
"-y",
"@supportpages.io/wtfm@0.5.7",
"mcp"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"wtfm": {
"command": "npx",
"args": [
"-y",
"@supportpages.io/wtfm@0.5.7",
"mcp"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"wtfm": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@supportpages.io/wtfm@0.5.7",
"mcp"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"wtfm","type":"stdio","command":"npx","args":["-y","@supportpages.io/wtfm@0.5.7","mcp"]}'Claude Code
claude mcp add --transport stdio wtfm -- npx -y @supportpages.io/wtfm@0.5.7 mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @supportpages.io/wtfm@0.5.7 mcp
- Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
- 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.
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). 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.5.7
- Latest stable
- 0.5.7
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-10-23. 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-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-LSHzXTTei9gzhegNt…
- Signature
- signed and attested
- License
- Apache-2.0
Source: the package registry · 2026-10-23.
Usage
- Downloads
- 317 in the last month
Source: api.npmjs.org · 2026-10-23.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Published package can be started | Started and answered | matches | our test · 2026-10-23 |
| Version 0.5.7 on npm | Exists and can be installed | matches | npm · 2026-10-23 |
| Repository github.com/SupportPages-io/wtfm | Opens publicly | matches | api.github.com · 2026-10-23 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.SupportPages-io
- GitHub owner
- an organization (SupportPages-io)
- Build record
- signed and attested
- Repository
- github.com/SupportPages-io/wtfm
- Stars
- 58
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.
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 rating9 of 9 record checks met
- #7,364 of 15,112 packages by monthly downloads, tied with 14 others
- #1,078 of 22,952 repositories by GitHub stars, tied with 12 others
- #848 of 1,074 packages meeting all 9 record checks, by downloads, tied with 2 others
- 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.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- MetPackage names its licence with a standard (SPDX) identifierApache-2.0
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
- 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-23. 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.SupportPages-io/wtfm
Answered from the data aboveIs io.github.SupportPages-io/wtfm safe to install?
We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. 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. 25 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.SupportPages-io/wtfm been security tested?
Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.
What can io.github.SupportPages-io/wtfm do?
It lists 47 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, run code or commands, control a browser or desktop and generate content and more. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.SupportPages-io/wtfm change or delete data?
25 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.github.SupportPages-io/wtfm publish a security policy?
Yes: its repository has a public security policy (github.com/supportpages-io/wtfm/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Is the listed version current?
Yes. The registry lists 0.5.7, the latest stable release on npm.
Where is the source code of io.github.SupportPages-io/wtfm?
In github.com/SupportPages-io/wtfm, 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.
Similar servers
Same topic · AI-read
- io.github.tomyud1/godot-mcpalso has tools that calculates or converts, controls a browser or desktop, creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
- io.github.kivanccakmak/yaverYaveralso has tools that calculates or converts, controls a browser or desktop, creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
- io.github.yaver-io/yaverYaveralso has tools that calculates or converts, controls a browser or desktop, creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
- io.github.abap2UI5/mcp-serverabap2UI5also has tools that calculates or converts, controls a browser or desktop, creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
- io.github.HaD0Yun/gopeakalso has tools that calculates or converts, controls a browser or desktop, creates or changes data, deletes, runs code or commands, reads or searchescompare with this one
- io.github.SummerEngine/summerSummer Enginealso has tools that controls a browser or desktop, creates or changes data, deletes, runs code or commands, generates content, reads or searchescompare with this one
Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
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
Not probed (read-only run)
We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. 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 applicable
- Consent handling: not applicable
- Sign-in metadata: not applicable
2 exercised10 not run (reason given)6 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 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
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.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 package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.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 package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.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
- 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 runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
Source: our own test in an isolated sandbox, 2026-10-23, 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 the published package in an isolated sandbox (read-only mode)
- 35,017 msConnected after 0 redirects.
- Read the inventory: 47 tools, 0 resources, 0 prompts.
- 36,476 msFinished: 2 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.SupportPages-io/wtfm: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.SupportPages-io/wtfm
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.SupportPages-io/wtfm)
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