io.github.41fred/ibo
REMOTE · IBOUNIVERSE.COM
Commission cinematic AI campaign films from IBO Studio, with custom scoping when needed.
Available components
Last scanned (18 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Design and Media
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1040 tokens (~130/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 35% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://ibouniverse.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ibouniverse.com | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | dc537b32352e23a9137d60f7b87889a5 |
| SANs: ibouniverse.com, *.ibouniverse.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of ibouniverse.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ibouniverse.com. | present | 2371 | 13 | Verified |
| ibouniverse.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ibouniverse.com/mcp | Verified | 200 | |
| http (plaintext) | http://ibouniverse.com/mcp | HTTPS enforced | 301 | https://ibouniverse.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_checkout Create a deposit checkout ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_request_id | string | yes | Stable id you generate; makes creation idempotent on retry |
| package | string | yes | Offer id from list_offers |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_due | number | – | – |
| checkout_url | string | – | – |
| currency | string | – | – |
| note | string | – | – |
| offer_id | string | – | – |
| stripe_session_id | string | – | – |
No examples provided.
create_upload_url Get a presigned asset-upload URL ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | – |
| order_token | string | yes | From get_order |
| size | number | yes | File size in bytes |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| key | string | – | – |
| url | string | – | – |
No examples provided.
get_inquiry_status Check status of a custom production inquiry ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| inquiry_id | string | yes | From submit_custom_inquiry |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| note | string | – | – |
| stage | string | – | – |
| status | string | – | – |
| updated | string | – | – |
No examples provided.
get_order Verify an order after checkout ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Stripe checkout session id (cs_...) |
| Name | Type | Req | Description |
|---|---|---|---|
| deposit | number | – | – |
| expires_at | number | – | – |
| order_token | string | – | – |
| package | string | – | – |
| paid | boolean | – | – |
| total | string | – | – |
No examples provided.
get_project_status Check production status of a paid order ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Stripe checkout session id (cs_...) |
| Name | Type | Req | Description |
|---|---|---|---|
| deposit | number | – | – |
| package | string | – | – |
| paid | boolean | – | – |
| stage | string | – | – |
| total | string | – | – |
No examples provided.
list_offers List IBO production packages ~42
IBO's production packages: stable ids, prices, 50% deposits, deliverables, review rounds, and the scope/refund policy. Call this first.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| how_to_order | array | – | – |
| offers | array | – | – |
| policies | object | – | – |
| studio | string | – | – |
| url | string | – | – |
No examples provided.
submit_brief Submit the creative brief ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| channels | string | – | – |
| company | string | – | – |
| constraints | string | – | – |
| string | – | – | |
| files | array | – | – |
| goal | string | – | – |
| launch | string | – | – |
| links | string | – | – |
| name | string | – | – |
| order_token | string | – | From get_order |
| package | string | – | – |
| product | string | – | – |
| resolution | string | – | Final master resolution selected before creative kickoff |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| ok | boolean | – | – |
No examples provided.
submit_custom_inquiry Submit a custom production inquiry (no payment) ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| channels | string | – | – |
| company | string | – | – |
| constraints | string | – | – |
| string | yes | Customer's real email; the confirmation link goes here | |
| goal | string | yes | What they want to make and why, in real detail (30+ chars; placeholders rejected) |
| launch | string | – | – |
| links | string | – | – |
| name | string | yes | – |
| notes | string | – | – |
| product | string | – | – |
| resolution | string | – | Required production target: 1080p, 4K mastered, or not applicable for still images |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| message | string | – | – |
| ok | boolean | – | – |
| status | string | – | – |
No examples provided.
How do I install the io.github.41fred/ibo MCP server?
io.github.41fred/ibo is a hosted endpoint at https://ibouniverse.com/mcp, 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.
remote · ibouniverse.com
claude mcp add --transport http 41fred-ibo 'https://ibouniverse.com/mcp'
What is the io.github.41fred/ibo MCP server?
io.github.41fred/ibo is an MCP server listed in the public MCP registry as io.github.41fred/ibo. Commission cinematic AI campaign films from IBO Studio, with custom scoping when needed. This page covers its hosted endpoint (https://ibouniverse.com/mcp).
Is the io.github.41fred/ibo MCP server safe to use?
io.github.41fred/ibo scores 85 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 io.github.41fred/ibo MCP server expose?
io.github.41fred/ibo exposes 8 tools: list_offers, create_checkout, get_order, submit_brief, create_upload_url, and 3 more. Their descriptions and schemas cost roughly 951 tokens of context every time the server is loaded.
Does the io.github.41fred/ibo MCP server require authentication?
No. We connected to io.github.41fred/ibo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.41fred/ibo MCP server still maintained?
io.github.41fred/ibo is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.