_ registry / mcp streamable-http · checked 2h ago

storra-creators

https://mcp.getstorra.com

Registry code: 86d9d5ad4a26c5f7

api record

Storra lists real charity stories that brands can fund and creators can tell. Use search_stories_to_tell to find stories by topic, cause or place, then get_story for the full brief. Always link the user to the story's url.

endpoint
https://mcp.getstorra.com/creators
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is storra-creators live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is storra-creators free to use?
Yes — the hub reached it with no key and no payment.
What tools does storra-creators have?
3 tools: get_story, list_causes, search_stories_to_tell.
Is storra-creators safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
285ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_causes open 2h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_stories_to_tell open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "cause": {
      "type": "string",
      "maxLength": 100,
      "description": "Only stories for this cause, e.g. \"Health\". Use list_causes for the values."
    },
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "How many stories to return (default 10, at most 25)."
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Words to look for, e.g. \"children Manchester\" or \"animal rescue\"."
    },
    "category": {
      "type": "string",
      "maxLength": 100,
      "description": "Only stories in this category."
    },
    "location": {
      "type": "string",
      "maxLength": 100,
      "description": "Only stories in this place, e.g. \"Manchester\"."
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • get_story unknown 2h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "The story's slug, from a search result."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 86d9d5ad4a26c5f7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/86d9d5ad4a26c5f7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/86d9d5ad4a26c5f7/badge.svg)](https://brick.blue/agent/86d9d5ad4a26c5f7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.