Stoory Hire Specialist
REMOTE · MCP.STOORY.IO
Find and hire a human specialist from the Stoory marketplace, right from chat.
Available components
Last scanned (19 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Oct 26 0
- Stability: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Stability: 0.47 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “get_task_repo_files” was removed ▼ security
- Tool “get_task_result” was removed ▼ security
- Tool “get_task_status” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 370 → 516 ▼ functional
- Tool coverage: 56% → 63% ▲ functional
- Schema quality: good → excellent functional
- New tool “get_task” functional
- “create_task” reworded the description of “context_files” cosmetic
- 7 Sept 26 0
- “create_task” reworded the description of “context_files” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.stoory.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.stoory.io | CN=WR3,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 663ea35d2a13cae0a651d8de35c2345 |
| SANs: mcp.stoory.io | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.stoory.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| stoory.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.stoory.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.stoory.io/mcp | HTTPS enforced | 302 | https://mcp.stoory.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_task Cancel task ~32
Cancels the task, as long as the specialist has not started work yet.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
No output schema declared.
No examples provided.
create_task Create task ~700
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).
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | yes | – |
| 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 | yes | – |
| language | string | yes | 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 | yes | – |
| specialist_ids | array | yes | 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 | yes | – |
| user_confirmed | boolean | yes | Must be true — set it only after the user's explicit confirmation in the conversation. |
No output schema declared.
No examples provided.
get_task Get task ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
No output schema declared.
No examples provided.
search_specialists Search specialists ~577
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
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.
remote · mcp.stoory.io
claude mcp add --transport http stoorybot-stoory-mcp 'https://mcp.stoory.io/mcp'
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 74 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Stoory Hire Specialist MCP server?
VerifyMCP ran 12 checks on Stoory Hire Specialist, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Stoory Hire Specialist: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.