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

ibo-studio

https://ibouniverse.com

Registry code: a2207a2a3fd31f47

api record

IBO is an AI-native film studio. Typical flow: list_offers -> create_checkout (your USER approves payment at checkout_url) -> get_order to verify paid and receive an order_token -> create_upload_url per asset file -> submit_brief with the order_token. Payment amounts are fixed server-side and cannot be altered. Later, check progress with get_project_status (paid orders) or get_inquiry_status (custom inquiries).

endpoint
https://ibouniverse.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 ibo-studio live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is ibo-studio free to use?
Yes — the hub reached it with no key and no payment.
What tools does ibo-studio have?
8 tools: submit_brief, create_upload_url, submit_custom_inquiry, get_order, get_inquiry_status, get_project_status, create_checkout, list_offers.
Is ibo-studio 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
99.6%

90 days 99.7%· all time 99.7%

latency
576ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 392 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
media generation video
used for
  • list film production packages
  • pay a deposit for a video production
  • upload brand assets
  • submit a creative brief
  • check production status
takes → gives
data, text, payments, documents → data
tools
4 reads3 changes data1 moves money
_ 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 8 tools
1 open 7 never probed 1 of 8 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_offers reads open 23h ago

    IBO's production packages: stable ids, prices, 50% deposits, deliverables, review rounds, and the scope/refund policy. Call this first.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • submit_brief changes data unknown never probed

    Submit the creative brief for a PAID order: pass order_token (from get_order; session ids are not accepted here) plus project fields (product, goal, audience, channels, resolution, launch, links, constraints) and files[] from create_upload_url. Delivery resolution must be selected before creative kickoff. Customer identity comes from the verified payment. NOTE: unpaid/anonymous submissions are rejected here; for Custom Production inquiries without payment use the submit_custom_inquiry tool instead.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "goal": {
      "type": "string"
    },
    "name": {
      "type": "string"
    },
    "email": {
      "type": "string"
    },
    "files": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "key",
          "name",
          "size"
        ],
        "properties": {
          "key": {
            "type": "string"
          },
          "name": {
            "type": "string"
          },
          "size": {
            "type": "number"
          }
        },
        "additionalProperties": false
      }
    },
    "links": {
      "type": "string"
    },
    "launch": {
      "type": "string"
    },
    "company": {
      "type": "string"
    },
    "package": {
      "type": "string"
    },
    "product": {
      "type": "string"
    },
    "audience": {
      "type": "string"
    },
    "channels": {
      "type": "string"
    },
    "resolution": {
      "type": "string",
      "description": "Final master resolution selected before creative kickoff"
    },
    "constraints": {
      "type": "string"
    },
    "order_token": {
      "type": "string",
      "description": "From get_order"
    }
  },
  "additionalProperties": false
}
    arguments 70 lines
  • create_upload_url changes data unknown never probed

    Get a short-lived presigned URL to upload one brand-asset file to IBO's private storage. Requires order_token from get_order; the storage location is bound to the order server-side. PUT the raw file bytes to url, then reference key in submit_brief files[]. Allowed: jpg png webp pdf svg mp4 mov zip ai psd; 250MB/file, 1GB per order.

    mcp-tool

    {
  "type": "object",
  "required": [
    "filename",
    "size",
    "order_token"
  ],
  "properties": {
    "size": {
      "type": "number",
      "description": "File size in bytes"
    },
    "filename": {
      "type": "string"
    },
    "order_token": {
      "type": "string",
      "description": "From get_order"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • submit_custom_inquiry changes data unknown never probed

    Start a Custom Production conversation without payment. IMPORTANT: interview your user for the real project details FIRST (what they are promoting, audience, formats, delivery resolution, timing); placeholder inquiries are rejected. A 4K Campaign Series must use this route before checkout. Submits a scope inquiry; IBO then emails the customer a one-click confirmation link (double opt-in), and only a confirmed inquiry reaches the studio. Tell your user to check their inbox and click confirm. IBO replies with scope and proposal within one business day of confirmation.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "email",
    "goal"
  ],
  "properties": {
    "goal": {
      "type": "string",
      "description": "What they want to make and why, in real detail (30+ chars; placeholders rejected)"
    },
    "name": {
      "type": "string"
    },
    "email": {
      "type": "string",
      "description": "Customer's real email; the confirmation link goes here"
    },
    "links": {
      "type": "string"
    },
    "notes": {
      "type": "string"
    },
    "launch": {
      "type": "string"
    },
    "company": {
      "type": "string"
    },
    "product": {
      "type": "string"
    },
    "audience": {
      "type": "string"
    },
    "channels": {
      "type": "string"
    },
    "resolution": {
      "type": "string",
      "description": "Required production target: 1080p, 4K mastered, or not applicable for still images"
    },
    "constraints": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 50 lines
  • get_order reads unknown never probed

    Verify payment after checkout and receive an order-scoped access token. Returns paid, package, deposit, and order_token: use order_token for create_upload_url and submit_brief. Payment status can only be established here, never assumed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "session_id"
  ],
  "properties": {
    "session_id": {
      "type": "string",
      "description": "Stripe checkout session id (cs_...)"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_inquiry_status reads unknown 23h ago

    Where a custom inquiry stands: awaiting_confirmation (customer hasn't clicked the emailed link yet) or confirmed with the studio stage (new, replied, proposal_sent, won, closed). PII-free; pass the inquiry_id returned by submit_custom_inquiry.

    mcp-tool

    {
  "type": "object",
  "required": [
    "inquiry_id"
  ],
  "properties": {
    "inquiry_id": {
      "type": "string",
      "description": "From submit_custom_inquiry"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_project_status reads unknown 23h ago

    Where a paid order is in production. Returns the studio stage (new, brief_received, in_production, review, delivered) plus paid/package/deposit. PII-free; pass the stripe_session_id from create_checkout/get_order.

    mcp-tool

    {
  "type": "object",
  "required": [
    "session_id"
  ],
  "properties": {
    "session_id": {
      "type": "string",
      "description": "Stripe checkout session id (cs_...)"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • create_checkout moves money unknown never probed

    Create a Stripe Checkout for a package's 50% deposit. Returns checkout_url, stripe_session_id, and amount_due. Show the amount to your user and open checkout_url for THEM to approve and pay; agents never complete payment themselves. Prices are fixed server-side. Pass a stable client_request_id so retries do not create duplicate checkouts.

    mcp-tool

    {
  "type": "object",
  "required": [
    "package",
    "client_request_id"
  ],
  "properties": {
    "package": {
      "enum": [
        "film",
        "film4k",
        "series"
      ],
      "type": "string",
      "description": "Offer id from list_offers"
    },
    "client_request_id": {
      "type": "string",
      "description": "Stable id you generate; makes creation idempotent on retry"
    }
  },
  "additionalProperties": false
}
    arguments 23 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 a2207a2a3fd31f47.

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

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.