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.

io.github.mjaskolski/wondel-skills-mcp

REMOTE · SKILLS.WONDEL.AI · SCANNED SEP 22

Read-only MCP server over 50 book-based agent skills: routes a task to the right framework.

Available components

+2 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1917 tokens (~26/item across 72 items; 5 tools + 67 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (80% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.mjaskolski/wondel-skills-mcp server?

io.github.mjaskolski/wondel-skills-mcp is a hosted endpoint at https://skills.wondel.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · skills.wondel.ai

# add to Claude Code
claude mcp add --transport http mjaskolski-wondel-skills-mcp 'https://skills.wondel.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "mjaskolski-wondel-skills-mcp": {
      "url": "https://skills.wondel.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mjaskolski-wondel-skills-mcp": {
      "type": "http",
      "url": "https://skills.wondel.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.mjaskolski-wondel-skills-mcp]
url = "https://skills.wondel.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mjaskolski-wondel-skills-mcp": {
      "type": "remote",
      "url": "https://skills.wondel.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mjaskolski-wondel-skills-mcp --url 'https://skills.wondel.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  mjaskolski-wondel-skills-mcp:
    url: "https://skills.wondel.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mjaskolski-wondel-skills-mcp": {
      "Transport": "http",
      "Url": "https://skills.wondel.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add mjaskolski-wondel-skills-mcp -t streamable-http -u 'https://skills.wondel.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "mjaskolski-wondel-skills-mcp": {
      "type": "http",
      "url": "https://skills.wondel.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 19 Sept 26 0
    • Stability: 0.97 → pass security
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

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 22 Sept 2026 · Probed https://skills.wondel.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=skills.wondel.ai CN=WE1,O=Google Trust Services,C=US 15 Aug 2026 13 Nov 2026 ECDSA 256 ECDSA-SHA256 d927db23d0a07e0a0efb68ec3bd3ead0
SANs: skills.wondel.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of skills.wondel.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
wondel.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://skills.wondel.ai/mcp Verified 200
http (plaintext) http://skills.wondel.ai/mcp HTTPS enforced 301 https://skills.wondel.ai/mcp
MCP tools · 5 exposed · ~792 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
get_journey ~131

One guided journey as a phase plan: the ordered skills, the decision question each phase answers, the docs/ file it writes, and which phases are go/no-go gates. Pass slug for a known journey, or goal to have one picked.

NameTypeReqDescription
contextstringyesWhy are you calling this tool? One line on the user's actual task, in their words — not a restatement of the tool name.
goalstringWhat you are trying to achieve, if you do not know which journey fits
slugstringJourney slug, e.g. "grow-website"
NameTypeReqDescription
artifactsarrayyes
canonicalstringyes
definitionstringyes
installstringyes
namestringyes
nextstringyes
notForarrayyes
phasesarrayyes
slugstringyes
taglinestringyes
useWhenarrayyes

No examples provided.

get_skill ~168

Metadata for one skill or journey: its definition, when to use it, when not to, and related slugs. Deliberately cheap (~300 tokens) so you can check a candidate before committing context to it. Pass sections to widen, or sections:["all"] for the whole page. This does not return the skill instructions — load_skill does.

NameTypeReqDescription
contextstringyesWhy are you calling this tool? One line on the user's actual task, in their words — not a restatement of the tool name.
sectionsarrayWhich parts to return. Default: definition, use_when, not_for, related. "all" returns the full page.
slugstringyesSkill or journey slug, e.g. "refactoring-ui" or "create-business"
NameTypeReqDescription
bookobject
canonicalstringyes
categorystringyes
definitionstring
examplePromptsarray
faqsarray
installstringyes
keyConceptsarray
kindstringyes
namestringyes
nextstringyes
notForarray
oneLinerstringyes
phasesarray
relatedarray
slugstringyes
sourcestringyes
updatedstringyes
useWhenarray

No examples provided.

load_skill ~133

The skill's actual instructions — the upstream SKILL.md, ready to follow in this session with nothing installed. The response also lists the skill's reference files with their token cost, so you can pull deeper material on demand by calling again with part set to a filename.

NameTypeReqDescription
contextstringyesWhy are you calling this tool? One line on the user's actual task, in their words — not a restatement of the tool name.
partstring"core" (default) for SKILL.md, or a reference filename from a previous response
slugstringyesSkill or journey slug

No output schema declared.

No examples provided.

recommend_skills ~188

Route a task to the right skills. Describe the job in your own words and this returns which skills to load first, which to skip whenever a skill's own "not for" line rules it out for this task — quoted verbatim — and a guided journey when the task spans a whole project rather than one step. This is the tool to reach for first.

NameTypeReqDescription
contextstringyesWhy are you calling this tool? One line on the user's actual task, in their words — not a restatement of the tool name.
maxintegerHow many skills to return (default 3)
phasestringWhere in the work you are
stackstringLanguage, framework or platform, if it narrows the answer
taskstringyesThe job to be done, in your own words — a full sentence beats a keyword
NameTypeReqDescription
avoidarrayyes
journeyobject
loadFirstarrayyes
nextstringyes
taskstringyes
thenarrayyes

No examples provided.

search_skills ~172

Search 51 book-based agent skills and 14 guided journeys by keyword or phrase. Each skill is matched against its own trigger text, so plain task language works ("my UI looks amateur", "pricing", "dark mode"). Returns compact hits, each quoting the line that matched. Use recommend_skills instead when you have a task rather than a keyword.

NameTypeReqDescription
categorystringRestrict to one domain
contextstringyesWhy are you calling this tool? One line on the user's actual task, in their words — not a restatement of the tool name.
kindstringRestrict to single skills or guided journeys
limitintegerMaximum hits (default 8)
querystringyesKeyword, phrase, slug or plain description of the problem
NameTypeReqDescription
nextstringyes
querystringyes
resultsarrayyes
totalnumberyes

No examples provided.

Common questions

What is the io.github.mjaskolski/wondel-skills-mcp server?

io.github.mjaskolski/wondel-skills-mcp is listed in the public MCP registry as io.github.mjaskolski/wondel-skills-mcp. Read-only MCP server over 50 book-based agent skills: routes a task to the right framework. This page covers its hosted endpoint (https://skills.wondel.ai/mcp).

Is the io.github.mjaskolski/wondel-skills-mcp server safe to use?

io.github.mjaskolski/wondel-skills-mcp scores 80 out of 100 on VerifyMCP. 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 io.github.mjaskolski/wondel-skills-mcp server expose?

io.github.mjaskolski/wondel-skills-mcp exposes 5 tools: search_skills, recommend_skills, get_skill, load_skill, get_journey. Their descriptions and schemas cost roughly 792 tokens of context every time the server is loaded.

Does the io.github.mjaskolski/wondel-skills-mcp server require authentication?

No. We connected to io.github.mjaskolski/wondel-skills-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.mjaskolski/wondel-skills-mcp server still maintained?

io.github.mjaskolski/wondel-skills-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.