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

promptcelerator

https://promptcelerator.com

Registry code: 8a232b4f8c010ed6

api record

Promptcelerator is a free library of AI video prompts that really worked, each next to the video it produced and credited to its creator.

search finds the prompts that fit a video idea and links to their pages, where the videos can be watched. fetch returns one prompt in full. list_options lists the models, categories and techniques.

endpoint
https://promptcelerator.com/mcp
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 promptcelerator live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is promptcelerator free to use?
Yes — the hub reached it with no key and no payment.
What tools does promptcelerator have?
3 tools: fetch, list_options, search.
Is promptcelerator 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
273ms

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_options open 1h ago

    Lists what search can filter on: the video models the library covers, its categories and its camera, light and style techniques.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "language": {
          "type": "string",
          "description": "Language of the user, as a code such as fr, es, ja, zh, zh-tw (50 languages). Titles, summaries and links come in this language, and fetch adds the translated prompt. Defaults to en."
        }
      }
    }
    arguments 9 lines
  • search open 1h ago

    Searches a free library of AI video prompts that really worked, each published next to the video it produced. Takes a plain-language description of a video (subject, mood, style, shot) in any language; English gives the closest matches. Returns the prompts that fit, best first, each with how well it fits (strong, possible or weak), its page, its video, its model and its creator. The full text of a prompt comes from fetch.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "How many results. Defaults to 6."
        },
        "model": {
          "type": "string",
          "description": "Only prompts made with this video model, for example \"veo\", \"seedance\" or \"Kling\". See list_options."
        },
        "query": {
          "type": "string",
          "maxLength": 500,
          "description": "What the user wants to make, for example \"a slow-motion perfume ad\" or \"documentaire sur la Corée filmé au caméscope\". Leave empty to get the most liked prompts for the filters."
        },
        "format": {
          "enum": [
            "landscape",
            "portrait",
            "square"
          ],
          "type": "string",
          "description": "Shape of the video."
        },
        "category": {
          "type": "string",
          "description": "Only this category, as a slug from list_options."
        },
        "language": {
          "type": "string",
          "description": "Language of the user, as a code such as fr, es, ja, zh, zh-tw (50 languages). Titles, summaries and links come in this language, and fetch adds the translated prompt. Defaults to en."
        },
        "technique": {
          "type": "string",
          "description": "Only prompts using this technique, as a slug from list_options, for example \"dolly-in\"."
        },
        "with_sound": {
          "type": "boolean",
          "description": "Only videos with sound."
        }
      }
    }
    arguments 48 lines
  • fetch unknown 1h ago

    Returns one prompt in full, from an id given by search or the address of a prompt page: the original text that produced the video, its translation when there is one, the blanks to fill, the model, the video and the credit of its creator.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The id of a result of search, or the address of a prompt page."
        },
        "language": {
          "type": "string",
          "description": "Language of the user, as a code such as fr, es, ja, zh, zh-tw (50 languages). Titles, summaries and links come in this language, and fetch adds the translated prompt. Defaults to en."
        }
      }
    }
    arguments 16 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 8a232b4f8c010ed6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8a232b4f8c010ed6/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/8a232b4f8c010ed6/badge.svg)](https://brick.blue/agent/8a232b4f8c010ed6?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.