# ShowMeStepByStep (remote · www.showmestepbystep.com)

Search, browse, and cite a 377-tutorial step-by-step how-to corpus from your AI client.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.showmestepbystep.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/rt1966-showmestepbystep/api-mcp.md), [page](https://verifymcp.io/servers/rt1966-showmestepbystep/api-mcp)

## Channel facts

- Endpoint: `https://www.showmestepbystep.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 642 tokens (~107/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http rt1966-showmestepbystep https://www.showmestepbystep.com/api/mcp
```

### Codex

```toml
[mcp_servers.rt1966-showmestepbystep]
url = "https://www.showmestepbystep.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rt1966-showmestepbystep": {
      "type": "remote",
      "url": "https://www.showmestepbystep.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rt1966-showmestepbystep --url https://www.showmestepbystep.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  rt1966-showmestepbystep:
    url: "https://www.showmestepbystep.com/api/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +1)

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

### 2026-08-01 (score 67, +1)

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

### 2026-07-31 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 65, +1)

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

### 2026-07-27 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (6)

### `search_tutorials` (~158 tokens)

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.

Input parameters:

- `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, required): Search query (>= 2 chars)

### `get_tutorial` (~114 tokens)

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.

Input parameters:

- `slug` (string, required): Tutorial slug (e.g. 'how-to-fix-a-leaky-faucet')

### `list_categories` (~33 tokens)

List all tutorial categories with a published tutorial. Returns slug, name, short description, and count of published tutorials per category.

### `list_tutorials_by_category` (~72 tokens)

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.

Input parameters:

- `categorySlug` (string, required): e.g. 'cooking', 'home-improvement', 'crafts'
- `limit` (integer)

### `list_recent_tutorials` (~78 tokens)

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.

Input parameters:

- `days` (integer): Lookback window in days (default 14, max 90).
- `limit` (integer)

### `request_tutorial` (~187 tokens)

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.

Input parameters:

- `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, required): What the user wants to learn how to do (e.g. 'how to get pesto stains out of a white shirt')

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/rt1966-showmestepbystep/api-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 66
- 2026-07-29: 65
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://www.showmestepbystep.com/api/mcp
- Repository: https://github.com/rt1966/ShowMeStepByStep
- Website: https://www.showmestepbystep.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/rt1966-showmestepbystep/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/rt1966-showmestepbystep/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/rt1966-showmestepbystep/api-mcp