# Storra for Creators (remote · mcp.getstorra.com)

Find real charity stories a creator could make content about. Read-only, no sign-in.

- Trust score: 82/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.getstorra.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-getstorra-creators/creators.md), [page](https://verifymcp.io/servers/com-getstorra-creators/creators)

## Channel facts

- Endpoint: `https://mcp.getstorra.com/creators`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-21.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 290 tokens (~96/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Storra for Creators MCP server?

Storra for Creators is a hosted endpoint at https://mcp.getstorra.com/creators, 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 com-getstorra-creators 'https://mcp.getstorra.com/creators'
```

### Cursor

```json
{
  "mcpServers": {
    "com-getstorra-creators": {
      "url": "https://mcp.getstorra.com/creators"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-getstorra-creators": {
      "type": "http",
      "url": "https://mcp.getstorra.com/creators"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-getstorra-creators]
url = "https://mcp.getstorra.com/creators"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getstorra-creators": {
      "type": "remote",
      "url": "https://mcp.getstorra.com/creators",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-getstorra-creators --url 'https://mcp.getstorra.com/creators' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-getstorra-creators:
    url: "https://mcp.getstorra.com/creators"
```

### Netclaw

```json
{
  "McpServers": {
    "com-getstorra-creators": {
      "Transport": "http",
      "Url": "https://mcp.getstorra.com/creators"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-getstorra-creators -t streamable-http -u 'https://mcp.getstorra.com/creators'
```

### Other

```json
{
  "mcpServers": {
    "com-getstorra-creators": {
      "type": "http",
      "url": "https://mcp.getstorra.com/creators"
    }
  }
}
```

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-11-18 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-11-16 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 76, 0)

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

### 2026-11-05 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `search_stories_to_tell` (~153 tokens)

Search stories to tell

Search real charity stories a creator could make a video or post about. Matches the query against titles, summaries, charities, causes and places, and returns the best matches with a link to each story page.

Input parameters:

- `category` (string): Only stories in this category.
- `cause` (string): Only stories for this cause, e.g. "Health". Use list_causes for the values.
- `limit` (integer): How many stories to return (default 10, at most 25).
- `location` (string): Only stories in this place, e.g. "Manchester".
- `query` (string): Words to look for, e.g. "children Manchester" or "animal rescue".

### `get_story` (~50 tokens)

Get a story

Get one story in full: the story, where you could take it, the support on offer, and the charity's details.

Input parameters:

- `slug` (string, required): The story's slug, from a search result.

### `list_causes` (~34 tokens)

List causes

List the causes stories are filed under, with how many stories each has. Use a cause as the filter in a search.

## Diagnostics

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

## Score history

- 2026-11-21: 82
- 2026-11-20: 82
- 2026-11-19: 82
- 2026-11-18: 82
- 2026-11-17: 81
- 2026-11-16: 81
- 2026-11-15: 80
- 2026-11-14: 80
- 2026-11-13: 79
- 2026-11-12: 79
- 2026-11-11: 79
- 2026-11-10: 78
- 2026-11-09: 78
- 2026-11-08: 77
- 2026-11-07: 77
- 2026-11-06: 76
- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70

## Common questions

### What is the Storra for Creators MCP server?

Storra for Creators is an MCP server listed in the public MCP registry as com.getstorra/creators. Find real charity stories a creator could make content about. Read-only, no sign-in. This page covers its hosted endpoint (https://mcp.getstorra.com/creators).

### Is the Storra for Creators MCP server safe to use?

Storra for Creators scores 82 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 Storra for Creators MCP server expose?

Storra for Creators exposes 3 tools: search_stories_to_tell, get_story, list_causes. Their descriptions and schemas cost roughly 237 tokens of context every time the server is loaded.

### Does the Storra for Creators MCP server require authentication?

No. We connected to Storra for Creators without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Storra for Creators MCP server still maintained?

Storra for Creators 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 Storra for Creators MCP server?

VerifyMCP ran 12 checks on Storra for Creators, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Storra for Creators: HTTPS. 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.

## Links

- Remote endpoint: https://mcp.getstorra.com/creators
- Website: https://getstorra.com/ai
- Changelog RSS feed: https://verifymcp.io/servers/com-getstorra-creators/creators.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-getstorra-creators/creators/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-getstorra-creators/creators.json
- HTML version of this page: https://verifymcp.io/servers/com-getstorra-creators/creators
