ShowMeStepByStep
REMOTE · WWW.SHOWMESTEPBYSTEP.COM · SCANNED SEP 24
Search, browse, and cite a 377-tutorial step-by-step how-to corpus from your AI client.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability89
- 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 642 tokens (~107/item across 6 items; 6 tools + 0 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 Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the ShowMeStepByStep MCP server?
ShowMeStepByStep is a hosted endpoint at https://www.showmestepbystep.com/api/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 · www.showmestepbystep.com
claude mcp add --transport http rt1966-showmestepbystep 'https://www.showmestepbystep.com/api/mcp'
{
"mcpServers": {
"rt1966-showmestepbystep": {
"url": "https://www.showmestepbystep.com/api/mcp"
}
}
} {
"servers": {
"rt1966-showmestepbystep": {
"type": "http",
"url": "https://www.showmestepbystep.com/api/mcp"
}
}
} [mcp_servers.rt1966-showmestepbystep] url = "https://www.showmestepbystep.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rt1966-showmestepbystep": {
"type": "remote",
"url": "https://www.showmestepbystep.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add rt1966-showmestepbystep --url 'https://www.showmestepbystep.com/api/mcp' --transport streamable-http
mcp_servers:
rt1966-showmestepbystep:
url: "https://www.showmestepbystep.com/api/mcp" {
"McpServers": {
"rt1966-showmestepbystep": {
"Transport": "http",
"Url": "https://www.showmestepbystep.com/api/mcp"
}
}
} assistant mcp add rt1966-showmestepbystep -t streamable-http -u 'https://www.showmestepbystep.com/api/mcp'
{
"mcpServers": {
"rt1966-showmestepbystep": {
"type": "http",
"url": "https://www.showmestepbystep.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 80
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 Sept 2026 · Probed https://www.showmestepbystep.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.showmestepbystep.com | CN=YR2,O=Let's Encrypt,C=US | 14 Aug 2026 | 12 Nov 2026 | RSA 2048 | SHA256-RSA | 6156a89043214349a2965ae5d7c08ac8955 |
| SANs: *.showmestepbystep.com, showmestepbystep.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.showmestepbystep.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| showmestepbystep.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.showmestepbystep.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.showmestepbystep.com/api/mcp | HTTPS enforced | 308 | https://www.showmestepbystep.com/api/mcp |
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 →
get_tutorial ~114
Fetch the full machine-readable rendition of a tutorial by slug: title, TL;DR, numbered steps (with text, imageUrl, tips, and YouTube videoTimestampSeconds for deep-linking), tools/materials, tags, related tutorial slugs, creator credit, recipe (with nutrition + cuisine when applicable), license, and canonicalUrl. Use this after search_tutorials to fetch step details.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Tutorial slug (e.g. 'how-to-fix-a-leaky-faucet') |
No output schema declared.
No examples provided.
list_categories ~33
List all tutorial categories with a published tutorial. Returns slug, name, short description, and count of published tutorials per category.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recent_tutorials ~78
List the most recently published tutorials, newest first. Use this to discover what's new on the site or to surface fresh content for aggregator / 'what's new this week' agent loops. Tenant-aware.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days (default 14, max 90). |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_tutorials_by_category ~72
Browse tutorials within a specific category, ranked by view count then publish date. Use this when a user wants to explore a topic area rather than search.
| Name | Type | Req | Description |
|---|---|---|---|
| categorySlug | string | yes | e.g. 'cooking', 'home-improvement', 'crafts' |
| limit | integer | – | – |
No output schema declared.
No examples provided.
request_tutorial ~187
Submit a request for a tutorial we don't yet have. Call this when search_tutorials returned no good match for what the user actually wants. The request enters our content-demand queue, which the daily content batch reviews and prioritizes. Optionally include an email for notification when the tutorial ships.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Brief context about the requester (e.g. 'beginner crocheter', 'first-time homeowner', 'gluten-free baker'). Helps shape the tutorial when we ship it. |
| notifyEmail | string | – | Optional email to notify when the tutorial ships. Pure opt-in. |
| originalQuery | string | – | The exact user query that came up empty in search_tutorials. Useful for matching keyword demand. |
| topic | string | yes | What the user wants to learn how to do (e.g. 'how to get pesto stains out of a white shirt') |
No output schema declared.
No examples provided.
search_tutorials ~158
Search the ShowMeStepByStep tutorial corpus by free-text query. Searches across tutorial titles, descriptions, and step content. Returns slim summaries with TL;DRs and canonical URLs. Tenant-aware. Optional filters narrow by category, difficulty, or maximum duration.
| Name | Type | Req | Description |
|---|---|---|---|
| categorySlug | string | – | Optional category to restrict the search to (e.g. 'cooking', 'crochet'). Use list_categories to see available slugs. |
| difficulty | string | – | Optional difficulty filter. |
| limit | integer | – | – |
| maxDurationMinutes | integer | – | Optional ceiling on tutorial total duration. Useful for 'quick recipes' / 'under 10 min' queries. |
| query | string | yes | Search query (>= 2 chars) |
No output schema declared.
No examples provided.
What is the ShowMeStepByStep MCP server?
ShowMeStepByStep is an MCP server listed in the public MCP registry as io.github.rt1966/showmestepbystep. Search, browse, and cite a 377-tutorial step-by-step how-to corpus from your AI client. This page covers its hosted endpoint (https://www.showmestepbystep.com/api/mcp).
Is the ShowMeStepByStep MCP server safe to use?
ShowMeStepByStep 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 ShowMeStepByStep MCP server expose?
ShowMeStepByStep exposes 6 tools: search_tutorials, get_tutorial, list_categories, list_tutorials_by_category, list_recent_tutorials, request_tutorial. Their descriptions and schemas cost roughly 642 tokens of context every time the server is loaded.
Does the ShowMeStepByStep MCP server require authentication?
No. We connected to ShowMeStepByStep without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ShowMeStepByStep MCP server still maintained?
ShowMeStepByStep is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.