Stoory Hire Specialist

by StooryBot · remote · no sign-in to list tools · v0.1.0 · published by GitHub user StooryBot

Find and hire a human specialist from the Stoory marketplace, right from chat.

Deletes · 1Final · 1

Compare Registry entry

4 tools: 1 can delete or cancel things, 1 do something that can't be undone and 2 only read.

Scanned Oct 21, 2026

Deletes or cancels1Claude Code: deny: see these tools
Can't be undone1Claude Code: ask: see these tools
Changes things0Claude Code: ask
Only reads2Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http stoory https://mcp.stoory.io/mcp --header 'x-api-key: <your-x-api-key>'

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Deletes or cancels 1Removes, cancels or revokes something.Claude Code: deny

cancel_taskCancels the task, as long as the specialist has not started work yet.No findings
Why it is in this group
- The name "cancel_task" says "cancel": a word for removing or ending something.
Description, as the server wrote it
Cancels the task, as long as the specialist has not started work yet.

Can't be undone 1Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

create_taskInvites one or more chosen specialists to a project — does NOT charge payment.No findings
Why it is in this group
- The name "create_task" says "create": a word for a change.
- The description's first verb is "invite": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it
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 minor graphic tweak; 2h = a standard debug across a few files / a draft legal document (e.g. Privacy Policy) / a landing page design; 3h = an architecture review, a full legal package (ToS+Privacy+GDPR) or a compliance audit, full branding, no clear diagnosis) times the specialist's min_rate_per_hour (from search_specialists) — this field is informational, not enforced, always in USD (the only currency on the marketplace).

Only reads 2Looks things up and changes nothing.Claude Code: allow

get_taskReturns the whole task record in one call — use it both to check progress and to read the result.No findings
Why it is in this group
- The name "get_task" says "get": a word for reading.
Description, as the server wrote it
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 user asks about progress. create_task already returns attached_files for the files it uploaded.
search_specialistsSearches for specialists in the Stoory marketplace via semantic search.No findings
Why it is in this group
- The name "search_specialists" says "search": a word for reading.
Description, as the server wrote it
Searches for specialists in the Stoory marketplace via semantic search. Result quality depends mostly on a well-built `query` — see the `query` field description. If a result has <3 hits or only 'Alternative fit', retry with a simpler/broader query (see `query`) instead of asking the user; only after about 3 failed attempts tell the user you have no one to recommend for these requirements and suggest widening the criteria.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Looked at Oct 22, 2026, 14:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable: yes
HTTP status of an anonymous initialize: 200
tools/list served without credentials: yes
Tools that change things, listed without credentials: 2
Protocol version: 2025-06-18
WWW-Authenticate on 401: not observed
resource_metadata in WWW-Authenticate: none
RFC 9728 protected resource metadata: none
Authorization servers: none
Legacy HTTP+SSE transport: no
Dynamic client registration: not observed
Client ID metadata documents: not observed

HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
Matched text
https://mcp.stoory.io/mcp: tools/list returned 4 tools to an anonymous client, including cancel_task (destructive), create_task (irreversible)
What this check looks for

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http stoory https://mcp.stoory.io/mcp --header 'x-api-key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__stoory__search_specialists",
      "mcp__stoory__get_task"
    ],
    "ask": [
      "mcp__stoory__create_task"
    ],
    "deny": [
      "mcp__stoory__cancel_task"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stoory. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.StooryBot/stoory-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:21 UTC.

For agents: Markdown · JSON · report this listing