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

aigifmaker-mcp

https://aigifmaker.ai

Registry code: 64740cf9831bd719

api record

AI GIF Maker turns text into animated GIFs (native GIF generation, no video conversion) on the user's own aigifmaker.ai account. One GIF costs 1 credit. generate_gif usually returns the GIF URL in about a minute; if it returns a task id instead, poll it with check_gif.

endpoint
https://aigifmaker.ai/api/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 aigifmaker-mcp live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is aigifmaker-mcp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does aigifmaker-mcp have?
3 tools: check_credits, generate_gif, check_gif.
Is aigifmaker-mcp 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
476ms

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
1 auth-required 2 never probed 1 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.

  • check_gif auth-required 11h ago

    Look up a GIF by the task id generate_gif returned when it was still running, and return its URL once it is ready. Free to call.

    mcp-tool

    {
  "type": "object",
  "required": [
    "task_id"
  ],
  "properties": {
    "task_id": {
      "type": "string",
      "description": "The task id from generate_gif."
    }
  }
}
    arguments 12 lines
  • check_credits unknown never probed

    Credits left on the AI GIF Maker account behind your API key. One GIF costs 1 credit. Free to call.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • generate_gif unknown never probed

    Turn a text prompt into an animated GIF on AI GIF Maker (aigifmaker.ai) and return the GIF URL. Native GIF generation, no video conversion; usually about a minute. Costs 1 credit on the AI GIF Maker account behind your API key, the same as on the website. If the GIF is still running when this returns, it gives a task id for check_gif.

    mcp-tool

    {
  "type": "object",
  "required": [
    "prompt"
  ],
  "properties": {
    "prompt": {
      "type": "string",
      "description": "What the GIF should show and how it moves, e.g. \"a corgi in sunglasses dancing on a beach, looping\"."
    }
  }
}
    arguments 12 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 64740cf9831bd719.

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