# Stoory Hire Specialist

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

- name: io.github.StooryBot/stoory-mcp
- version: 0.1.0
- connection class: R1 (autonomous)
- trust: 90/100
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.StooryBot%2Fstoory-mcp
- tools: https://api.protogrid.dev/v1/servers/io.github.StooryBot%2Fstoory-mcp/tools

**An agent can connect on its own if it already holds `X_API_KEY`, `X_API_KEY`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "stoory-mcp": {
      "type": "http",
      "url": "https://mcp.stoory.io/mcp",
      "headers": {
        "x-api-key": "${X_API_KEY}",
        "Authorization": "${X_API_KEY}"
      }
    }
  }
}
```

Placeholders to fill: `${X_API_KEY}`, `${X_API_KEY}`.

## Trust

- hygiene: 100
- liveness: 100
- freshness: 85
- provenance: 75
- drivers: +repository +website +reachable +uptime-99% ~updated-57d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: create_task (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_specialists (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_task (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,975 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 1,975 tokens to load them all
- tool set hash: 4dc2e5ab4407515473bdb0cc06f6cd65
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.StooryBot/stoory-mcp.svg)](https://protogrid.dev/servers/io.github.StooryBot/stoory-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.stoory.io/mcp (streamable-http, auth api_key ${X_API_KEY}, reachable true, uptime30d 0.99159664)

## Packages

_none_

## Tools (4)

- `cancel_task`: Cancels the task, as long as the specialist has not started work yet.
- `create_task`: 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).
- `get_task`: 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_specialists`: 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.
