io.github.CloudCorpRecords/boothdesk
OCI · GHCR.IO/CLOUDCORPRECORDS/BOOTHDESK · 2 COMPONENTS
Dreambooth Studio operator console: sessions, revenue, credits, projects and booth design tools.
Available components
Last scanned (14 hours ago)
Scores higher than 39% of OCI servers
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4961 tokens (~225/item across 22 items; 22 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 39
First indexed and scored.
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 21 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/boothdesk@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
check_generation Check background work ~329
Report on background work started by start_frame, refine_frame, start_booth, refine_booth or create_booth. Always pass the jobId that the start/refine/create call returned — keep it for the rest of the conversation, because an id keeps working for the full 15 minutes even if the connection re-authenticates partway through, and calling with no arguments does not. With no arguments it reports the most recent job of any kind, which is a convenience for when the id was lost, not the normal way to call it. Designing a booth takes 1-3 minutes, a redraw about a minute, creating a booth 2-6 minutes: tell the operator that, then poll about every 15 seconds. While it says 'running', nothing exists yet — relay the progress line if there is one, tell the operator it is still going, and wait 10-15 seconds before calling again rather than polling tightly. When it says 'done': a frame job carries imageUrl, threadId and generationId (a preview — nothing saved until save_frame); a booth design carries draft{…} (a draft — nothing created until create_booth); a booth creation carries booth{slug, boothUrl, projectId} — the one case where something now exists. This reads a status and creates nothing, so it is always safe to call.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | – | The id a start/refine/create tool returned. Pass it whenever you have it. Omit only if it was lost, which falls back to the most recent job listed for this connection. |
No output schema declared.
No examples provided.
connect_account Connect a Dreambooth account ~207
Connect this conversation to the person's Dreambooth Studio account. The answer's status says what happened. already_connected: an account is connected; nothing to do. awaiting_approval: it returns a link the person opens in their own browser to sign in with Google and approve. A Google account with the same email as an existing Dreambooth account connects that account. Ask them to open it and say when they are done; do not call this tool again while waiting. use_client_sign_in: this client connects accounts through its own app or connector settings, where they can sign in with an email and password or with Google, so no link is returned. Ask them to connect Dreambooth there (the client also asks by itself when a tool needs an account), then repeat their question. Either way, someone who has no Dreambooth account yet gets one when they sign in. Call this when another tool reports that no account is connected, or when someone asks to connect or switch accounts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
connection_status Check Dreambooth connection ~50
Whether this conversation currently has a Dreambooth account connected, and which one. Call this if you are unsure whether to run connect_account first. Cheap and read-only — it does not contact Dreambooth.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_booth Create the booth ~497
Create the booth from a finished draft — the step that makes something real, live at its public link. Call it only after the operator has seen the draft via check_generation and agreed to create it; the title and link name (slug) default to the draft's unless the operator chose others. It reads the draft first (so everything set with update_booth_draft — settings, frames, filters, AI effect — is carried), checks the link name, draws the booth's own three photo-strip frames (3 images, up to five minutes), adds three starter frames from the catalogue and the Studio's default 'Normal' filter the way dreambooth.app/new does, then creates the booth with the draft's welcome design, background, colour theme and capture mode. Frames saved with save_frame and filters made with create_filter on this connection are carried automatically; ids can also be passed. Tell the operator it takes 2-6 minutes. Returns a job id; check_generation reports progress and, when done, the booth's public link, id and a dashboard link. If the link name is taken it stops before drawing anything — ask for another and call again. Creating twice with different link names makes two booths. The booth is live (unlisted) at once; there is no tool that edits or deletes a booth — changes happen in the dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| aiEffectTitle | string | – | The title of a public AI effect to add, exactly as the operator named it. Leave unset for none. |
| captureMode | string | – | Leave unset to keep what the draft proposed ('standard' = classic strip, 'frame-based' = frame mode). |
| draftId | string | yes | The draft to create, from check_generation. |
| filterIds | array | – | Ids of filters to include — e.g. one the operator just made with create_filter. The default 'Normal' filter is added anyway. |
| frameIds | array | – | Ids of frames to include — e.g. a frame the operator just saved with save_frame. Starter frames are added anyway. |
| slug | string | – | The link name: lowercase letters, digits and single hyphens (dreambooth.app/<slug>). Leave unset to use the draft's proposed slug. |
| title | string | – | The booth's name. Leave unset to use the draft's title (as shown by check_generation / set with update_booth_draft). |
No output schema declared.
No examples provided.
create_filter Create a photo filter ~219
Create a new photo filter on this operator's account from a description of the look they want — 'warm and slightly faded', 'high contrast black and white'. Translate the description into the adjustment numbers yourself; the ranges are in the schema. Call this only when the operator asks for a filter to be CREATED. It does not change an existing filter, and there is no tool that does — to edit or delete one, send them to the dashboard. Creating the same filter twice makes two filters, so do not retry a call that may have gone through.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustments | object | yes | Only include what the operator asked to change. An omitted adjustment keeps its neutral value; sending every field at its neutral value creates a filter that does nothing. |
| isPublic | boolean | – | Leave unset unless the operator explicitly asks for the filter to be shared. Default is private to their account. |
| name | string | yes | What the operator will see in their filter list. Use their words if they named it; otherwise a short descriptive name, not 'Untitled'. |
No output schema declared.
No examples provided.
duplicate_project Duplicate a booth ~168
Copy one of this operator's existing booths, with all of its settings, into a new one. Use it when they want another booth 'like' one they already run — a second location, a one-off event, a variant to experiment on. Call list_projects first to get the project id; the operator will name the booth, not its id. The copy is named after the original and is not published at the original's public address, so it is safe to make and they can rename it in the dashboard. To design a NEW booth from a description, use start_booth instead of this; there is no tool that edits or deletes a booth that already exists.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | The id of the booth to copy, from list_projects. Not its name or slug. |
No output schema declared.
No examples provided.
get_booth_draft Read a booth draft ~125
Read a booth draft by its draftId — the same summary check_generation gives for a finished design, plus everything the draft has been given since (settings, chosen frames, filters, AI effect). Use it when the job from start_booth is no longer tracked, to show the draft again before create_booth, or to confirm what update_booth_draft applied. Reads only; nothing is generated or created. A draft lives 7 days on the operator's account.
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | yes | The draft, from check_generation or a previous tool result. |
No output schema declared.
No examples provided.
get_credits Get AI credits and plan ~66
This operator's remaining AI credit balance and their current subscription plan, including when it ends. Call this when they ask how many credits are left, whether they can still run AI effects, or what plan they are on. Credits are separate from wallet money — do not confuse the two.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_gallery_stats Get gallery statistics ~104
How much media this operator's booths have produced: total, still active, and expired past the retention window. Call this when the operator asks how many photos or videos a booth has taken, or whether media is being lost to retention. Returns counts only, not the media itself.
| Name | Type | Req | Description |
|---|---|---|---|
| includeExpired | boolean | – | Count media past its retention window too (default false) |
| projectId | string | – | Limit to one booth. Omit for every booth this operator owns. |
No output schema declared.
No examples provided.
get_project Get one booth in detail ~98
Full detail for a single booth: its name, public link, currency, screen size, and the live status of the device running it — whether it is online, when it was last seen, app version, and camera/printer/internet state. Call this when the operator asks about one specific booth, or whether a booth is working. Get the project id from list_projects first.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | Project id from list_projects |
No output schema declared.
No examples provided.
get_revenue_summary Get revenue summary ~163
Business revenue from this operator's photobooth sessions across EVERY payment channel — gateway payments, cash vouchers (cash collected at the booth) and discount vouchers — grouped by month or day and by currency, with extra-print revenue and AI-effect purchases reported separately. Use this for any question about income, revenue or omzet. It is also the right tool when wallet earnings look too small: cash and voucher money never reaches the wallet ledger, so for operators who take cash the wallet figure legitimately understates income.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date, ISO YYYY-MM-DD. Omit for all time. |
| groupBy | string | – | Bucket size (default month) |
| to | string | – | End date, ISO YYYY-MM-DD. Omit for all time. |
No output schema declared.
No examples provided.
get_sessions Get photo sessions ~218
List the photo sessions recorded on this operator's booths, with totals. Call this when the operator asks how busy a booth has been, how many sessions ran in a period, or wants to inspect individual sessions. Supports date ranges, per-booth filtering, payment status and payment channel. For money totals rather than session counts, use get_revenue_summary instead.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | ISO date (YYYY-MM-DD) for the end of the range, inclusive |
| limit | integer | – | How many sessions to return (default 20, max 100) |
| paymentSource | string | – | Payment channel, e.g. gateway, cash-voucher, discount-voucher |
| projectIds | string | – | Comma-separated project ids to limit the range to specific booths |
| sessionStatus | string | – | Session status filter |
| startDate | string | – | ISO date (YYYY-MM-DD) for the start of the range, inclusive |
| transactionStatus | string | – | Payment status filter, e.g. settlement, pending |
No output schema declared.
No examples provided.
get_wallet_transactions Get wallet transactions ~120
This operator's wallet ledger: gateway earnings, withdrawals and refunds, newest first. Use for questions about the wallet, payouts or withdrawals. Do NOT use it to answer 'how much did I earn' — the wallet excludes cash and voucher income entirely, so for operators who take cash it understates real revenue. Use get_revenue_summary for income.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date, ISO YYYY-MM-DD |
| limit | integer | – | Max rows (default 10) |
| to | string | – | End date, ISO YYYY-MM-DD |
No output schema declared.
No examples provided.
list_projects List booths ~68
List the photobooth projects this operator owns, with id, name, public link slug, whether it is active, and its currency. Call this first whenever the operator names a booth — you need the project id to filter any other tool by booth. Does not return booth designs or page layouts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_filter Preview a photo filter ~194
Show what a filter would look like BEFORE creating it: the Studio renders its sample photo (or the operator's own preview photo, if they set one in the dashboard) through the exact pipeline the booth uses, and returns an image URL. Free and read-only — call it whenever the operator is designing a filter, adjust the numbers from their reaction ('warmer', 'less contrast'), preview again, and call create_filter with the same adjustments only once they are happy. Some adjustments (shadows, highlights, whites, blacks, clarity, dehaze, vibrance, texture) are applied by the booth but cannot be shown here; the result lists them as notPreviewed so you can say so. Nothing is created by this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustments | object | yes | Only include what the operator asked to change. An omitted adjustment keeps its neutral value; sending every field at its neutral value creates a filter that does nothing. |
No output schema declared.
No examples provided.
refine_booth Refine a booth draft ~360
Change a booth draft from start_booth, using the draftId check_generation returned. what='welcome' redraws the welcome screen from an instruction ('warmer colours', 'bigger headline', 'less clutter') while keeping the design; add orientation 'phone' or 'laptop' to redraw only that screen (1 redraw) — without it both screens are redrawn (2). what='app-background' redraws the calmer backdrop behind the rest of the booth (1 redraw). what='everything' rebuilds the whole draft from a NEW full description (spends 1 of the draft's 3 full generations) — only when the operator wants a different booth, not a tweak. A draft has 5 redraws in total; check_generation reports what is left. Title, headline, link name and colours cannot be edited directly: they change only through a redraw instruction, or at create time (title, slug). Returns a job id; call check_generation. Call only when the operator asks for a change — never iterate on your own.
| Name | Type | Req | Description |
|---|---|---|---|
| draftId | string | yes | The draft to change, from check_generation's result for start_booth. |
| instruction | string | yes | For 'welcome' / 'app-background': what to change, in the operator's words, up to 300 characters — the current design is kept and only this is applied. For 'everything': the new full description of th… |
| orientation | string | – | Only with what='welcome': redraw just the phone (portrait) or laptop (landscape) screen. Omit to redraw both. |
| what | string | yes | Which part to change. 'everything' is a full rebuild from a new description. |
No output schema declared.
No examples provided.
refine_frame Refine a photo frame design ~185
Ask for a changed version of a frame in an existing design thread — 'darker', 'less ornament', 'make the flowers smaller', 'more gold'. Call it with the threadId that check_generation returned for start_frame, and ONLY when the operator asks for a change: every call spends part of the account's free daily allowance, so never iterate on your own initiative. It returns immediately with a job id; call check_generation for the new preview. Earlier versions in the thread stay available to save_frame, so a change the operator dislikes loses nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | What to change, in the operator's words. It is read with the whole thread as context, so 'the same but darker' works; there is no need to repeat the original description. |
| threadId | string | yes | The design thread, from check_generation's result for start_frame. |
No output schema declared.
No examples provided.
save_frame Save a generated frame ~235
Save one generation from a design thread as a real frame in this operator's frame list, with its photo windows cut out. Call it only when the operator has chosen a result — pass the threadId and generationId that check_generation returned for it. This CREATES a frame: saving the same generation twice makes two frames, so do not retry a call that may have gone through. The frame is private to the account unless the operator explicitly asks for it to be shared. After saving, the operator picks the frame in a booth's frame settings; this tool does not assign it to a booth, and there is no tool that edits or deletes a frame.
| Name | Type | Req | Description |
|---|---|---|---|
| generationId | string | yes | The generation to save, from check_generation. Each version in a thread has its own id. |
| isPublic | boolean | – | Leave unset unless they explicitly ask to share it. Default is private to their account. |
| name | string | – | What the operator will see in their frame list. Use their words if they named it; otherwise derived from the description. |
| threadId | string | yes | The design thread the generation belongs to. |
No output schema declared.
No examples provided.
search_docs Search Dreambooth documentation ~129
Search the Dreambooth Studio documentation and FAQ. Call this before answering any question about the product, hardware, printing, booth setup, guest payments, or troubleshooting — answer from the docs rather than from memory. Pages about Dreambooth's own plans and billing come back as a link only: share the link, and do not quote prices, plans or trials in the conversation. Works without a connected account.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 5) |
| locale | string | – | Docs language (default en) |
| query | string | yes | Search terms, in English or Indonesian |
No output schema declared.
No examples provided.
start_booth Design a new booth ~318
Design a complete photobooth (a 'booth') for this operator from a description — the Studio designs the welcome screen for phone and laptop, the in-booth background, the colour theme, the capture mode, a title and a link name, exactly as dreambooth.app/new does. Before calling, gather in chat what /new would ask and put ALL of it in the prompt: the occasion or business, the vibe or style, colours, and the language the booth should speak — there is no separate questions step. It returns a job id immediately; call check_generation, and do NOT describe the booth as designed or created until that says done. The result is a DRAFT with a draftId: nothing is in the operator's booth list until create_booth. Every call makes a new draft and spends 1 of its 3 full generations, and an account may start 10 drafts an hour — never call it speculatively or twice for one request; change a draft with refine_booth instead.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | The language the booth's own text should be in, as a code: 'id', 'en', 'es'. Defaults to English — ask if the operator's booth is not in English. |
| prompt | string | yes | The booth, in the operator's words plus what you gathered: occasion or business, vibe and style, colours, mood, anything that must appear. Up to 1000 characters. Do not name brands, characters or fra… |
No output schema declared.
No examples provided.
start_frame Start designing a photo frame ~404
Start designing a new photo frame for this operator's booths from a description of the look they want — 'batik motifs in warm gold', 'minimal Scandinavian, lots of white space'. It opens a design thread and makes the FIRST version. It returns immediately with a job id; call check_generation to see the result, and do NOT describe the frame as made until that says so. The result is a preview in the thread — nothing is in the operator's frame list until save_frame is called with the generation they choose. To change a result, call refine_frame with the threadId that check_generation returns, rather than starting again. Every generation spends part of the account's free daily allowance, so do not call this speculatively, twice for the same request, or while another generation is still running.
| Name | Type | Req | Description |
|---|---|---|---|
| layout | string | yes | How many photos and how they sit. 'strip-3': the classic photo strip — 3 photos stacked, printed as a pair on a 4x6; 'strip-4': a taller strip — 4 photos stacked, printed as a pair on a 4x6; 'grid-4'… |
| prompt | string | yes | What the frame should look like, in the operator's own words where possible: decoration, colour, mood, occasion. Not the photo slots — those come from the layout. Do not name brands, characters or fr… |
| shape | string | – | The shape the photos are cut to. Defaults to rectangular. Not every layout comes in every shape; the Studio picks the closest available. |
No output schema declared.
No examples provided.
update_booth_draft Change a booth draft's settings ~704
Change a booth draft without a redraw: its title, link name, welcome button text, colours, capture mode, language, which frames and filters it carries, its AI effect, and the page settings the dashboard editor offers (photo count, countdown, timeouts, GIF/recording, retake, checkout, payment, result). Use it after check_generation shows the draft and the operator asks for one of these; what it sets is applied when create_booth runs. It cannot change the welcome headline or subtext of an AI-designed welcome (those are painted into the image — use refine_booth), and prices or packages are set in the dashboard. Answers at once with the updated draft, `applied` (what landed) and `rejected` (what did not, and why) — relay a rejection as a sentence, never as success. It never touches a booth that already exists.
| Name | Type | Req | Description |
|---|---|---|---|
| aiEffectTitle | string | – | The title of a public AI effect to add, exactly as the operator named it; an empty string removes the one chosen before. |
| buttonText | string | – | The welcome screen's button label, e.g. 'Mulai' or 'Start'. |
| captureMode | string | – | 'standard' = classic strip, 'frame-based' = frame mode. |
| draftId | string | yes | The draft to change, from check_generation or get_booth_draft. |
| filterIds | array | – | Filters the booth should carry (replaces the draft's list): e.g. one made with create_filter. The default 'Normal' is added anyway. |
| frameIds | array | – | Frames the booth should carry (replaces the draft's list): e.g. one saved with save_frame, or catalogue ids. create_booth adds starter frames anyway. |
| headline | string | – | Welcome headline. Only drafts whose welcome is laid out as text accept it; on an AI-designed welcome it is painted into the image and the reply says to use refine_booth. |
| language | string | – | Language code of the booth's own text: 'id', 'en', 'es'. |
| palette | object | – | Theme colours as #RRGGBB: primaryColor, secondaryColor, backgroundColor. Only the ones given change. |
| settings | object | – | Page settings, as the dashboard editor has them, keyed by page: welcome{startWithPayment}, capture{captureCount 1-10, captureCountdown 1-15, prepTimeout, captureTimeout, selfPhotoDuration, gifEnabled… |
| slug | string | – | The proposed link name (dreambooth.app/<slug>): lowercase letters, digits, single hyphens. Checked for availability; a taken one is reported, not stored. |
| subtext | string | – | Welcome subtext; same rule as headline. |
| title | string | – | The booth's name (used as the title at create time). |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/boothdesk MCP server?
io.github.CloudCorpRecords/boothdesk runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/boothdesk:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/boothdesk
claude mcp add cloudcorprecords-boothdesk -- docker run --rm -i ghcr.io/cloudcorprecords/boothdesk:0.1.0 mcp
What is the io.github.CloudCorpRecords/boothdesk MCP server?
io.github.CloudCorpRecords/boothdesk is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/boothdesk. Dreambooth Studio operator console: sessions, revenue, credits, projects and booth design tools. This page covers its container image (ghcr.io/cloudcorprecords/boothdesk).
Is the io.github.CloudCorpRecords/boothdesk MCP server safe to use?
io.github.CloudCorpRecords/boothdesk scores 42 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.CloudCorpRecords/boothdesk MCP server expose?
io.github.CloudCorpRecords/boothdesk exposes 22 tools: connect_account, connection_status, get_sessions, get_gallery_stats, search_docs, and 17 more. Their descriptions and schemas cost roughly 4,961 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/boothdesk MCP server still maintained?
io.github.CloudCorpRecords/boothdesk is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/boothdesk MCP server under?
io.github.CloudCorpRecords/boothdesk declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.CloudCorpRecords/boothdesk MCP server?
VerifyMCP ran 12 checks on io.github.CloudCorpRecords/boothdesk, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/boothdesk: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.