# Stoory Hire Specialist (remote · mcp.stoory.io)

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

- Trust score: 67/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `mcp.stoory.io`: 67/100 (this document), [markdown](https://verifymcp.io/servers/stoorybot-stoory-mcp/mcp.md), [page](https://verifymcp.io/servers/stoorybot-stoory-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.stoory.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2065 tokens (~516/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 48/100
  - Stability check failed: schema churn in the 30 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Stoory Hire Specialist MCP server?

Stoory Hire Specialist is a hosted endpoint at https://mcp.stoory.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http stoorybot-stoory-mcp 'https://mcp.stoory.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "stoorybot-stoory-mcp": {
      "url": "https://mcp.stoory.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stoorybot-stoory-mcp": {
      "type": "http",
      "url": "https://mcp.stoory.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.stoorybot-stoory-mcp]
url = "https://mcp.stoory.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stoorybot-stoory-mcp": {
      "type": "remote",
      "url": "https://mcp.stoory.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stoorybot-stoory-mcp --url 'https://mcp.stoory.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  stoorybot-stoory-mcp:
    url: "https://mcp.stoory.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "stoorybot-stoory-mcp": {
      "Transport": "http",
      "Url": "https://mcp.stoory.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add stoorybot-stoory-mcp -t streamable-http -u 'https://mcp.stoory.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "stoorybot-stoory-mcp": {
      "type": "http",
      "url": "https://mcp.stoory.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 45 to 48.

### 2026-09-21 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 38 to 41.

### 2026-09-19 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 31 to 35.

### 2026-09-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 21 to 25.

### 2026-09-14 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 15 to 18.

### 2026-09-12 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 8 to 11.

## MCP tools (4)

### `search_specialists` (~577 tokens)

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.

Input parameters:

- `country` (string): Only when the user explicitly asks for the specialist's country (e.g. 'a designer from Poland'). Full English country name, e.g. "Poland", "Germany" — not an ISO code. Ignored if geo_location is also…
- `geo_location` (object): Only when the user gives a specific city/location and wants to search nearby (e.g. 'near Warsaw', 'a designer in Warsaw'). An object { lat, lon, radius_meters } — determine the lat/lon of the named c…
- `languages` (array): Only when the user explicitly asks for a specific specialist language (e.g. 'a Polish-speaking designer'). Allowed values: English, Polish, German, French, Spanish, Italian — any other value is rejec…
- `limit` (number): Default 10, raise to 20 for weak results or when the user asks for more options (max 20).
- `query` (string, required): The specialist's role and skills, MAX 12 words, natural language — not a full sentence describing the user's problem. In English if possible (faster response and better hits than other languages). Go…

### `create_task` (~700 tokens)

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).

Input parameters:

- `budget` (number, required)
- `context_files` (array): 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 D…
- `description` (string, required)
- `language` (string, required): 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).
- `problem_context` (string, required)
- `specialist_ids` (array, required): Id of one or more specialists to invite.
- `timeline` (string): How urgent the project is from the client's perspective — ask the user directly, do not guess.
- `title` (string, required)
- `user_confirmed` (boolean, required): Must be true — set it only after the user's explicit confirmation in the conversation.

### `get_task` (~144 tokens)

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.

Input parameters:

- `task_id` (string, required)

### `cancel_task` (~32 tokens)

Cancel task

Cancels the task, as long as the specialist has not started work yet.

Input parameters:

- `task_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/stoorybot-stoory-mcp/mcp#diagnostics

## Score history

- 2026-09-29: 67
- 2026-09-28: 67
- 2026-09-27: 67
- 2026-09-26: 67
- 2026-09-25: 67
- 2026-09-24: 67
- 2026-09-23: 67
- 2026-09-22: 66
- 2026-09-21: 66
- 2026-09-20: 65
- 2026-09-19: 65
- 2026-09-18: 64
- 2026-09-17: 64
- 2026-09-16: 64
- 2026-09-15: 63
- 2026-09-14: 63
- 2026-09-13: 62
- 2026-09-12: 62
- 2026-09-11: 61
- 2026-09-10: 61
- 2026-09-09: 60
- 2026-09-08: 60
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 65
- 2026-09-03: 65
- 2026-09-02: 64
- 2026-09-01: 64
- 2026-08-31: 63

## Common questions

### What is the Stoory Hire Specialist MCP server?

Stoory Hire Specialist is an MCP server listed in the public MCP registry as io.github.StooryBot/stoory-mcp. Find and hire a human specialist from the Stoory marketplace, right from chat. This page covers its hosted endpoint (https://mcp.stoory.io/mcp).

### Is the Stoory Hire Specialist MCP server safe to use?

Stoory Hire Specialist scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Stoory Hire Specialist MCP server expose?

Stoory Hire Specialist exposes 4 tools: search_specialists, create_task, get_task, cancel_task. Their descriptions and schemas cost roughly 1,453 tokens of context every time the server is loaded.

### Does the Stoory Hire Specialist MCP server require authentication?

No. We connected to Stoory Hire Specialist without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Stoory Hire Specialist MCP server still maintained?

Stoory Hire Specialist is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.stoory.io/mcp
- Authorisation metadata: https://mcp.stoory.io/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/StooryGitServer/stoory-mcp-server
- Website: https://stoory.io/
- Changelog RSS feed: https://verifymcp.io/servers/stoorybot-stoory-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/stoorybot-stoory-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/stoorybot-stoory-mcp/mcp