mcp-registry/io.github.stoorybot/stoory-mcp · v0.1.0
Also listed as github/stoorygitserver/stoory-mcp-server
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 13:11 UTC, the Stoory Hire Specialist 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. It had 10 outages in 90 days, with a median recovery of 2 minutes.
Find and hire a human specialist from the Stoory marketplace, right from chat.
Point your MCP client at this streamable-http endpoint: https://mcp.stoory.io/mcp
4 of 4 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 →
6 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 →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. 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%2Fio.github.stoorybot%2Fstoory-mcp/fixes
{
"name": "cancel_task",
"description": "Cancels the task, as long as the specialist has not started work yet.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"task_id"
],
"properties": {
"task_id": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
},
"title": "Cancel task"
}{
"name": "create_task",
"description": "Invites one or more chosen specialists to a project — does NOT charge payment. budget is a single amount for the whole task (not multiplied per specialist) — whoever accepts it does the work for it. Requires user_confirmed=true, set only after the user has explicitly confirmed in the conversation the choice of specialists, the list of shared files and the estimated cost. Estimate budget yourself from the problem's complexity (e.g. 1h = a single well-localized bug / a simple document fix / a mino",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"specialist_ids",
"title",
"description",
"problem_context",
"budget",
"language",
"user_confirmed"
],
"properties": {
"title": {
"type": "string"
},
"budget": {
"type": "number",
"minimum": 0
},
"language": {
"enum": [
"English",
"Polish",
"French",
"German",
"Spanish",
"Italian"
],
"type": "string",
"description": "The task's language — must match the language the user phrased title/description in (there is no auto-detection, set it according to the user's input)."
},
"timeline": {
"enum": [
"In a week",
"In a month",
"In 3 months",
"No rush",
"Do not know"
],
"type": "string",
"default": "No rush",
"description": "How urgent the project is from the client's perspective — ask the user directly, do not guess."
},
"description": {
"type": "string"
},
"context_files": {
"type": "array",
"items": {
"type": "object",
"required": [
"name"
],
"properties": {
"url": {
"type": "string",
"format": "uri"
},
"name": {
"type": "string"
},
"content_base64": {
"type": "string"
}
},
"additionalProperties": false
},
"description": "The minimal set of files the specialist needs. Each entry is { name, url?, content_base64? } and must carry exactly one source. `url` is strongly preferred: pass a link if the user gave one (Google Drive / Dropbox / S3 / raw GitHub) — the server rewrites common Google Drive and Dropbox share links to their direct-download form, and rejects a URL that returns a web page instead of a file — or, if you have a way to upload the file yourself (e.g. a code execution / shell environment) — upload it to any URL-reachable location first and pass that link instead of the raw bytes; the server just downloads it, which is fast and costs you almost no extra tokens. Use `content_base64` only as a last resort, when there is no URL and you have no way to produce one yourself (e.g. a small file the user attached directly in a chat-only client with no upload capability of its own) — inlining bytes means writing out the entire file as text, which is slow and burns far more tokens than a URL for anything beyond a tiny file. Before falling back to it, tell the user that creating the task will take noticeably longer and use more tokens because of it. Raw base64 only, never a `data:...;base64,` prefix. This server runs remotely and cannot read the caller's disk, so never pass local paths. The server scans every file for secrets, then uploads the rest to the task's file storage on Stoory; contents never enter the model context. Max 5MB per file. Entries that are unreadable or filtered as secrets come back in blocked_files — the task is still created without them."
},
"specialist_ids": {
"type": "array",
"items": {
"type": "string"
},
"minItems": 1,
"description": "Id of one or more specialists to invite."
},
"user_confirmed": {
"type": "boolean",
"description": "Must be true — set it only after the user's explicit confirmation in the conversation."
},
"problem_context": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create task"
}{
"name": "get_task",
"description": "Returns the whole task record in one call — use it both to check progress and to read the result. Fields: status, title, desc, budget, deadline, timeline, created, modified; specialist_invited and specialist_accepted (arrays of { id, profile_url } — profile_url is already in the right language, show it to the user as a link, not a bare id); and `files` — URLs of every file attached to the task on Stoory (the client's context files plus whatever the specialist delivers). Call it again when the us",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"task_id"
],
"properties": {
"task_id": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get task"
}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/io.github.stoorybot/stoory-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.stoorybot/stoory-mcp"}) over MCP.
create_task ~966 tokenssearch_specialists ~851 tokensget_task ~199 tokenscancel_task ~80 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fio.github.stoorybot%2Fstoory-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.stoorybot%2Fstoory-mcp?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.stoorybot%2Fstoory-mcp.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9a439259201204f9…, first seen 2026-10-17, included at leaf 1091 of 383,855. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable communication servers · most reliable data 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?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 13:11 UTC, the Stoory Hire Specialist 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. It had 10 outages in 90 days, with a median recovery of 2 minutes.
Stoory Hire Specialist MCP server advertises 4 tools, including cancel_task, create_task, get_task, search_specialists.
Point your MCP client at this streamable-http endpoint: https://mcp.stoory.io/mcp
Glimind scanned all 4 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.