_ registry / mcp streamable-http · checked 16h ago

showmestepbystep-mcp

https://www.showmestepbystep.com

Registry code: 344937d2d53cc17a

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://www.showmestepbystep.com/api/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is showmestepbystep-mcp live?
Yes — it answered the hub's last check (checked 16h ago). It answered 99% of checks over the last 30 days.
Is showmestepbystep-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does showmestepbystep-mcp have?
6 tools: request_tutorial, list_tutorials_by_category, get_tutorial, search_tutorials, list_categories, list_recent_tutorials.
Is showmestepbystep-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 99.2%· all time 99.2%

latency
150ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 516 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search step-by-step how-to tutorials
  • get a tutorial with numbered steps
  • browse tutorials by category
  • request a missing tutorial
takes → gives
text → text, data
tools
5 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
2 open 4 never probed 2 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_categories reads open 37h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_recent_tutorials reads open 37h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "default": 14,
          "maximum": 90,
          "minimum": 1,
          "description": "Lookback window in days (default 14, max 90)."
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1
        }
      }
    }
    arguments 18 lines
  • request_tutorial changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "topic"
      ],
      "properties": {
        "topic": {
          "type": "string",
          "maxLength": 200,
          "minLength": 5,
          "description": "What the user wants to learn how to do (e.g. 'how to get pesto stains out of a white shirt')"
        },
        "context": {
          "type": "string",
          "maxLength": 200,
          "description": "Brief context about the requester (e.g. 'beginner crocheter', 'first-time homeowner', 'gluten-free baker'). Helps shape the tutorial when we ship it."
        },
        "notifyEmail": {
          "type": "string",
          "maxLength": 254,
          "description": "Optional email to notify when the tutorial ships. Pure opt-in."
        },
        "originalQuery": {
          "type": "string",
          "maxLength": 500,
          "description": "The exact user query that came up empty in search_tutorials. Useful for matching keyword demand."
        }
      }
    }
    arguments 29 lines
  • list_tutorials_by_category reads unknown 37h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "categorySlug"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1
        },
        "categorySlug": {
          "type": "string",
          "description": "e.g. 'cooking', 'home-improvement', 'crafts'"
        }
      }
    }
    arguments 18 lines
  • get_tutorial reads unknown 47h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Tutorial slug (e.g. 'how-to-fix-a-leaky-faucet')"
        }
      }
    }
    arguments 12 lines
  • search_tutorials reads unknown 47h ago

    Search the Show Me Step by Step 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Search query (>= 2 chars)"
        },
        "difficulty": {
          "enum": [
            "easy",
            "medium",
            "advanced"
          ],
          "type": "string",
          "description": "Optional difficulty filter."
        },
        "categorySlug": {
          "type": "string",
          "description": "Optional category to restrict the search to (e.g. 'cooking', 'crochet'). Use list_categories to see available slugs."
        },
        "maxDurationMinutes": {
          "type": "integer",
          "minimum": 1,
          "description": "Optional ceiling on tutorial total duration. Useful for 'quick recipes' / 'under 10 min' queries."
        }
      }
    }
    arguments 36 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 344937d2d53cc17a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/344937d2d53cc17a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/344937d2d53cc17a/badge.svg)](https://brick.blue/agent/344937d2d53cc17a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.