mcp-registry/com.craftingstepbystep/tutorials · v0.1.0
As of 2026-10-26 17:06 UTC, the Craftingstepbystep Tutorials MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Search and cite step-by-step papercraft and craft tutorials with tools, supplies, and video credit.
Point your MCP client at this streamable-http endpoint: https://www.craftingstepbystep.com/api/mcp
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.craftingstepbystep%2Ftutorials/fixes
{
"name": "get_tutorial",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Tutorial slug (e.g. 'how-to-fix-a-leaky-faucet')"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_categories",
"description": "List all tutorial categories with a published tutorial. Returns slug, name, short description, and count of published tutorials per category.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_recent_tutorials",
"description": "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.",
"inputSchema": {
"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
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.craftingstepbystep/tutorials"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.craftingstepbystep/tutorials"}) over MCP.
request_tutorial ~302 tokenssearch_tutorials ~267 tokensget_tutorial ~158 tokenslist_recent_tutorials ~135 tokenslist_tutorials_by_category ~124 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.craftingstepbystep%2Ftutorials?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.craftingstepbystep%2Ftutorials?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.craftingstepbystep%2Ftutorials.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.craftingstepbystep%2Ftutorials.svg :target: https://glimind.com/server/mcp-registry%2Fcom.craftingstepbystep%2Ftutorials?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:07d48887dda6114a…, first seen 2026-10-17, included at leaf 16294 of 74,307. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable other servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:06 UTC, the Craftingstepbystep Tutorials MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Craftingstepbystep Tutorials MCP server advertises 6 tools, including get_tutorial, list_categories, list_recent_tutorials, list_tutorials_by_category, request_tutorial.
Point your MCP client at this streamable-http endpoint: https://www.craftingstepbystep.com/api/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.