Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bisque Presentations

REMOTE · BISQUE.CLOUD

Create narrated presentations from HTML, poll build status, list them, read one back as text.

Available components

+1 this week 92 Trust /100

Last scanned (8 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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 Security89
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6398 tokens (~228/item across 28 items; 26 tools + 2 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% 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
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 28 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 16 Nov 26 +1
    • New tool “read_artifact_analytics” functional
    • New tool “read_artifact_results” functional
  • 15 Nov 26 −1

    No change was recorded against any check on this day. Endpoint Security went from 91 to 89.

  • 14 Nov 26 0
    • Tool “update_artifact” rewrote its description, which is the text the model reads security
    • Tool “update_artifact” is now declared destructive security
    • “create_artifact” added an optional parameter “expires_at” cosmetic
    • “create_artifact” added an optional parameter “expires_in_days” cosmetic
    • “update_artifact” added an optional parameter “expires_at” cosmetic
    • “update_artifact” added an optional parameter “expires_in_days” cosmetic
  • 13 Nov 26 0
    • Tool “create_artifact” rewrote its description, which is the text the model reads security
    • Schema quality: 5272 → 5860 ▼ functional
    • New tool “edit_board” functional
    • New tool “read_board” functional
    • “create_artifact” added an optional parameter “board” cosmetic
    • “create_artifact” added an optional parameter “spec” cosmetic
    • “create_artifact” reworded the description of “content” cosmetic
    • “create_artifact” made “content” optional cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
    • New tool “pin_artifact” functional
    • New tool “unpin_artifact” functional
  • 10 Nov 26 +1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: pass → 0.97 functional
    • New tool “get_presentation_source” functional
Diagnostics

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 22 Nov 2026 · Probed https://bisque.cloud/presentations/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bisque.cloud CN=WR3,O=Google Trust Services,C=US 25 Oct 2026 23 Jan 2027 RSA 2048 SHA256-RSA 15d82dda6a64af73106f31d475c74c87
SANs: bisque.cloud, *.bisque.cloud
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bisque.cloud. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cloud. DS published 7041 13 Verified
bisque.cloud. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://bisque.cloud/.well-known/oauth-protected-resource/presentations/mcp", error="invalid_token"

Bearer resource_metadata="https://bisque.cloud/.well-known/oauth-protected-resource/presentations/mcp", error="invalid_token"

Protected resource metadata

Document https://bisque.cloud/.well-known/oauth-protected-resource/presentations/mcp
Retrieved Yes
Resource https://bisque.cloud/presentations/mcp
Authorisation server https://bisque.cloud

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bisque.cloud/presentations/mcp Verified 200
http (plaintext) http://bisque.cloud/presentations/mcp HTTPS enforced 301 https://bisque.cloud:443/presentations/mcp
MCP tools · 26 exposed · ~6,124 tokens

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 →

Tool Tokens
create_artifact ~951

Publish an HTML page or a Markdown document as a Bisque Artifact: a persistent, versioned page at a stable URL that people can open, comment on, and that you can update later with update_artifact. Pass the whole document as content. The call waits for the page to be ready and returns its URL. It is private to you unless you pass audience or share_with. A page that should remember what people do on it (a checklist, a poll, a sign-up sheet) declares capabilities ['state.read','state.write'] and, when some paths need different access, state.rules; it then reads and writes JSON documents through window.bisque.state. For a Whiteboard that people and agents draw on together, pass spec 'bisque-canvas/v1' with no content, and board.shapes to start it with frames, stickies, boxes and arrows; read it back with read_board and change it with edit_board. For a narrated presentation use create_presentation instead.

NameTypeReqDescription
audiencestring–Who can open the link. owner: only you. users: the people in share_with. public: anyone with the link.
boardobject–A Whiteboard's starting shapes.
capabilitiesarray–What the page may do at run time. state.read and state.write give it JSON documents at window.bisque.state (get, patch, list, subscribe); viewer.identity tells it who is viewing (window.bisque.viewer…
contentstring–The full document; required except for a Whiteboard. For html: a complete page in a sandboxed frame. Styles, scripts and images are inline, except libraries from cdnjs.cloudflare.com, cdn.jsdelivr.ne…
descriptionstring–One sentence saying what the page is; shown in listings.
expires_atstring–The same as expires_in_days, as an RFC 3339 moment. Pass one or the other.
expires_in_daysinteger–Delete the Artifact this many days from now, as delete_artifact would: it sits in the owner's Trash for 30 days, then its files go. Only when the user asks for it to go away (a scratch page, a one-we…
iconstring–An emoji that stands for the page, e.g. 📊. The tab and Home Screen show icon_image, not this.
icon_imagestring–The page's own icon: the favicon in the browser tab and the icon a phone puts on its Home Screen. A data URL: an SVG (data:image/svg+xml,<svg …>) or a base64 PNG, JPEG, WebP, or GIF, at most 512 KB,…
listedboolean–Show it in listings (the company library, public discovery) rather than link-only. Default true for a company audience (audience org with organization_id), false otherwise.
share_witharray–People to grant access by email (or uid), with a role. [{ "email": "ana@acme.com", "role": "viewer" }]. viewer opens it; editor can also publish new content. Implies audience "users" when audience is…
specstring–bisque-canvas/v1 makes a Whiteboard: an infinite board people edit live and you read and draw on. Leave content out.
stateobject–Who may read and write which paths of the page's data, by the minimum role: viewer (can open), contributor (a data grant, separate from editing the page), owner. Absent means: everyone who can open r…
titlestringyesA short name, the way a document or app is named.
typestring–Default html.
NameTypeReqDescription
artifact_idstringyes–
audience_modestringyesWho can open it: owner, users, org, or public.
created_atstring––
descriptionstring––
discoverabilitystringyes–
expires_atstring–When it is deleted, as its owner asked; absent when it is kept.
group_idstring––
iconstring––
icon_image_urlstring|null–The page icon set with icon_image; null for the Bisque icon.
latest_version_idstring––
organization_idstring––
publication_errorobject|null––
publication_statusstringyesready means the URL serves this content now. queued or processing means it is still being prepared; call get_artifact to check. failed carries publication_error.
published_version_idstring|nullyesThe Version viewers see; null until a publication is ready.
titlestringyes–
typestringyes–
updated_atstring––
urlstringyesThe viewer page.
version_idstringyesThe Version this call authored.
version_numberinteger––
viewer_version_modestring––

No examples provided.

create_artifact_thread ~203

Leave a new comment thread on one of your Artifacts, as the agent. Without an anchor the thread is a general comment on the page. The thread is activated from the start, so you can reply to it and resolve it later. Mention a person with @[Name](mention:uid) using ids from the Artifact's mentionables.

NameTypeReqDescription
anchorobject–Optional pin. { kind: "page", slideId, slideIndex, timeSec } for a slide or time; { kind: "element", selector, xFrac, yFrac, snapshot: { tag, text }, slideId, slideIndex, cueTarget, timeSec } for an…
artifact_idstringyesThe Artifact id (art_…).
bodystringyesMarkdown subset: bold, italic, code, links, lists.
NameTypeReqDescription
agent_activatedbooleanyesTrue once someone mentioned the agent; only then may the agent reply or resolve.
anchorobjectyesWhere the thread is pinned: kind element (selector, snapshot, slide), text (quote), or page.
artifact_idstringyes–
created_atstringyes–
created_byobjectyesWho wrote it: { kind: "user", uid, name, handle, avatarUrl } or { kind: "agent", principal, name, via }.
last_message_atstringyes–
mentionsarray––
message_countintegeryes–
messagesarrayyes–
participantsarray––
previewstringyes–
resolved_atstring|null––
root_message_idstring––
statusstringyes–
thread_idstringyes–
updated_atstring––
version_idstring––
version_numberintegeryes–

No examples provided.

create_presentation ~714

Generate a narrated presentation from an html-presentation/v1 document. BEFORE authoring, call get_presentation_spec and follow it exactly — slides without its narration markup publish SILENT. Returns a presentationId and the watch URL. Narration runs in the background and the inline player tracks it on its own, so reply to the user as soon as this returns and do not call get_presentation_status unless the user asks whether it is done.

NameTypeReqDescription
assetsarray–Files the document references relative to itself — fonts, images, Lottie/Rive animations, sound-effect audio, video clips. The SERVER fetches each https url at create time and stores it in the bundle…
audioarray–Optional. One entry per slide YOU narrated, from the JSON `bisque-voice` prints — word timings, duration, size and digest. Send it and your audio is used (free, unlimited, any OS); leave it out and t…
contextMdstring–Shared-with-viewer context.md.
designMdstring–Design frontmatter mapped to theme tokens.
dryRunboolean–Sandbox: run every check a real create runs (format, slug and org conflicts, tier cap, credit preflight) and write nothing. The reply has status "validated" and the webUrl a real create would publish…
handlestring–Publish under a specific channel handle you own.
indexHtmlstringyesFull html-presentation/v1 document (the presentation-format meta gate applies).
madeWitharray–Credit the models that made this: the model you are running as, and the narration engine or voice service if you know it — e.g. ["Claude Opus 5", "Kokoro af_heart"]. Shown to viewers in the watch pag…
presentationIdstring–Stable id for idempotent re-creates; defaults to slug-<hash(userId:slug)>.
slugstring–URL slug; defaults to a slugified title.
speechSpeednumber–Narration speed multiplier passed to the voice. Omit for the server default.
titlestring–Display title for the watch page and listings. Omit to use the title parsed from the document.
visibilitystring–unlisted (the default) is shareable by link and plays in chat-embedded players; private requires the owner to sign in, so an inline chat player shows a sign-in wall instead of playing — choose privat…
voiceIdstring–Narration voice. ElevenLabs: a bare id or cloud:<id>. Self-hosted Kokoro: kokoro:<id> (e.g. kokoro:af_heart); local:<id> is accepted as a synonym. Omit to use the voice saved on the account (bisque.c…
voiceStabilitynumber–Voice stability setting passed to the narration engine. Omit for the server default.
NameTypeReqDescription
narrationobjectyes–
presentationIdstringyes–
statusstringyesready = nothing needed narration; queued = narration runs in the background — poll get_presentation_status.
statusUrlstringyes–
webUrlstringyesShareable watch URL (live once status is ready).

No examples provided.

delete_artifact ~74

Delete an Artifact you own. Its URL stops working for everyone. Confirm with the user before calling this.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
NameTypeReqDescription
already_deletedboolean––
artifact_idstringyes–
deletedbooleanyes–

No examples provided.

edit_board ~306

Add, move, restyle or remove shapes on a Whiteboard. Shapes are keyed by an id you choose; sending the same id again changes that shape, and null removes it. People with the board open see the change within a second, and it is recorded as yours. Shapes people drew themselves are read with read_board but not changed here.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
shapesobjectyesShapes by id (1–64 letters, digits, - or _), each { type, x, y, w, h, z?, color?, text?, frame?, points? }, or null to remove one you drew. type is rect, ellipse, sticky, text, arrow (a line from x,y…
NameTypeReqDescription
artifact_idstringyes–
changedintegeryes–
urlstring––

No examples provided.

get_artifact ~118

Read one Artifact: title, who can open it, the Version viewers see (published_version_id, null while a publication is still being prepared), its URL, and for a markdown document its text (content), so a linked document is read in one call. Pass the art_… id from the end of the link.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
NameTypeReqDescription
artifact_idstringyes–
audience_modestringyesWho can open it: owner, users, org, or public.
contentstring|nullyesThe Markdown source of a markdown Artifact's published Version. null for an html page, a presentation, an Artifact that is not yet published, or a sold one you only view.
created_atstring––
descriptionstring––
discoverabilitystringyes–
expires_atstring–When it is deleted, as its owner asked; absent when it is kept.
group_idstring––
iconstring––
icon_image_urlstring|null–The page icon set with icon_image; null for the Bisque icon.
latest_version_idstring––
organization_idstring––
published_version_idstring|nullyesThe Version viewers see; null until a publication is ready.
titlestringyes–
typestringyes–
updated_atstring––
urlstringyesThe viewer page.
viewer_version_modestring––

No examples provided.

get_artifact_thread ~81

Read one comment thread on an Artifact with every message, oldest first. Mentions in a body look like @[Name](mention:uid); a mention of the agent is @[Agent](mention:agent).

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…).
thread_idstringyesThe thread id (thr_…).
NameTypeReqDescription
agent_activatedbooleanyesTrue once someone mentioned the agent; only then may the agent reply or resolve.
anchorobjectyesWhere the thread is pinned: kind element (selector, snapshot, slide), text (quote), or page.
artifact_idstringyes–
created_atstringyes–
created_byobjectyesWho wrote it: { kind: "user", uid, name, handle, avatarUrl } or { kind: "agent", principal, name, via }.
last_message_atstringyes–
mentionsarray––
message_countintegeryes–
messagesarrayyes–
participantsarray––
previewstringyes–
resolved_atstring|null––
root_message_idstring––
statusstringyes–
thread_idstringyes–
updated_atstring––
version_idstring––
version_numberintegeryes–

No examples provided.

get_presentation_analytics ~81

Watch analytics for one of your presentations: views, likes, completion rate, per-slide retention funnel, traffic sources, distinct signed-in/anonymous viewers, and organization email domains (personal providers filtered). Lets an agent read how its own published briefings performed.

NameTypeReqDescription
presentationIdstringyesThe presentationId whose view counts and survey responses you want.
NameTypeReqDescription
anonViewersintegeryes–
completedCountintegeryes–
completionRatenumber|nullyescompletedCount / viewCount, 0..1; null when no views.
likeCountintegeryes–
orgDomainsarrayyesOrganization email domains of signed-in viewers (personal providers filtered), sorted desc.
presentationIdstringyes–
slideReacharrayyesRetention funnel ordered by slide index.
slugstringyes–
sourcesobjectyesTraffic source → view count.
titlestringyes–
uniqueViewersintegeryesDistinct signed-in viewers.
viewCountintegeryes–
webUrlstring––

No examples provided.

get_presentation_context ~183

Load any shared Bisque presentation for reading: its metadata, the full per-slide narration transcript with timestamps, and the context.md file its author shipped for agents (extra background the slides summarize). Target it by watch URL (https://bisque.today/p/{handle}/{slug}) or by handle + slug — it does not have to be yours. Use this to read, summarize, cite, or answer questions about a presentation: ground your answers in the returned transcript and context, and cite slides as [slide N].

NameTypeReqDescription
handlestring–Channel handle (leading @ allowed).
slugstring–URL slug, the last path segment of the watch URL. Use with handle, or pass url instead.
urlstring–Watch URL, e.g. https://bisque.today/p/{handle}/{slug}. Provide this OR handle + slug.
NameTypeReqDescription
contextMdstring|nullyesThe bundle's context.md (shared agent-facing background); null when the presentation ships none.
contextTruncatedbooleanyes–
descriptionstring|null––
handlestringyes–
presentationIdstringyes–
publishedAtstring|null–ISO 8601, null when unknown.
slugstringyes–
titlestringyes–
transcriptarrayyesPer-slide narration, ordered by slide index.
transcriptTruncatedSlidesintegeryesContent slides the size-capped transcript dropped; 0 = complete.
visibilitystringyes–
webUrlstringyes–

No examples provided.

get_presentation_source ~211

Read the HTML a presentation was published from, so you can edit it and publish it back to the same URL. Only for a presentation this account may republish; anyone else's reads as not found, including a public one (use get_presentation_context to read those). Target it by presentationId, or by watch URL or handle + slug. To republish, change only what you were asked to in indexHtml and call create_presentation with the same presentationId, slug and visibility, plus each entry of assets as {path, url}; slides whose narration did not change keep their audio.

NameTypeReqDescription
handlestring–Channel handle (leading @ allowed).
presentationIdstring–From list_presentations or get_presentation_context.
slugstring–URL slug, the last path segment of the watch URL.
urlstring–Watch URL, e.g. https://bisque.today/p/{handle}/{slug}. Provide this, handle + slug, or presentationId.
NameTypeReqDescription
assetsarrayyesEvery file under assets/, with a download link that works for one hour. A republish that leaves one out loses it.
contextMdstring|nullyes–
descriptionstring|null––
handlestring|null––
indexHtmlstringyesThe HTML as published, complete.
madeWitharray––
presentationIdstringyes–
publishedAtstring|null––
slugstringyes–
titlestringyes–
versionintegeryesThe version this source is.
visibilitystringyes–
voiceobjectyesThe voice and speed the slides were spoken in. Republishing in them keeps the audio of every unchanged slide.
webUrlstringyes–

No examples provided.

get_presentation_spec ~60

Fetch the html-presentation/v1 authoring contract: document structure, the dual landscape/vertical layout rule, and the narration markup that makes slides speak. Call this BEFORE authoring for create_presentation — documents written without it publish with missing audio.

Input schema present but exposes no named parameters.

NameTypeReqDescription
formatstringyes–
specstringyesThe full authoring recipe + format contract, markdown.

No examples provided.

get_presentation_status ~45

Fetch the build state and result URL for a presentationId.

NameTypeReqDescription
presentationIdstringyesThe presentationId returned by create_presentation or publish_narrated_presentation.
NameTypeReqDescription
keptVersioninteger–Set when the latest republish failed (publishStatus failed) and the presentation still plays this earlier version at webUrl.
narrationobject–Narration progress: status (complete | partial | failed | waiting | …) and per-slide errors when partial/failed. waiting = the rest of the audio is still coming; the slides are viewable and it lands…
presentationIdstringyes–
publishStatusstringyes–
readybooleanyesTrue once the presentation is viewable.
visibilitystring––
webUrlstring–Shareable watch URL.

No examples provided.

list_artifact_threads ~153

List the comment threads people left on one of your Artifacts, newest activity first. Pass activated_only: true to get only the threads where someone mentioned the agent, which are the ones you may reply to and resolve. Each thread carries its anchor (what it is pinned to), the version it was left on, a preview, and agent_activated.

NameTypeReqDescription
activated_onlyboolean–Only threads where the agent was mentioned.
afterstring–RFC 3339 date-time; only threads with activity after it.
artifact_idstringyesThe Artifact id (art_…).
cursorstring–next_cursor from a prior page.
statusstring–Default open.
NameTypeReqDescription
artifact_idstringyes–
itemsarrayyes–
next_cursorstring|nullyes–

No examples provided.

list_artifacts ~98

List Artifacts you own (scope owned, the default), ones shared with you (shared), or both (all), newest first. Each item carries its id, title, who can open it, and its URL.

NameTypeReqDescription
cursorstring–next_cursor from a prior page.
limitinteger–Page size, default 25.
scopestring–Default owned.
typestring–Only this type.
NameTypeReqDescription
itemsarrayyes–
next_cursorstring|nullyes–

No examples provided.

list_presentations ~144

List the authenticated user's presentations, newest first. One call returns at most `limit` of them. A non-null `nextCursor` in the response means more presentations remain: call again with `cursor` set to that value to get the page after this one, and keep going until `nextCursor` is null.

NameTypeReqDescription
cursorstring–The `nextCursor` from a previous call, to read the page after that one. Omit it to start at the newest presentation.
limitinteger–Maximum number of presentations to return per page.
visibilitystring–Return only presentations with this visibility. Omit to return every one of them.
NameTypeReqDescription
nextCursorstring|nullyesPass this back as `cursor` for the next page. Null when this page is the last one.
presentationsarrayyesNewest first.

No examples provided.

pin_artifact ~126

Pin an Artifact to the top of the user's own Artifacts library, the same as the Pin button there. Use it when the user asks you to pin something, so they can find it again. A pin is only for the user: it changes nothing about the Artifact and does not share it. Pinning one that is already pinned moves it to the top.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
NameTypeReqDescription
artifact_idstringyes–
pinnedbooleanyes–
titlestring––
urlstring––

No examples provided.

publish_narrated_presentation ~821

DEPRECATED: call create_presentation with an `audio` array instead — it is the same thing in one call, and the slides are viewable while the narration lands. Publish an html-presentation/v1 document using audio YOU synthesized locally (e.g. with `bisque-voice`) — free, unlimited, and works on macOS, Linux and Windows. Send each narrated slide's word timings and MP3 metadata; the server assembles presentation.json (recomputing cues from your narration markers) and returns one upload URL per MP3. Then PUT each file and POST the returned completeUrl with the returned `files` array. RE-PUBLISHING: `audio` is optional — any narrated slide you omit reuses the audio from the last publish whenever its narration text and speechSpeed are unchanged, so an HTML-only edit needs no synthesis at all. The response reports `reused`, `synthesized`, and `staleSlides` (narrated slides whose text changed and have no audio — synthesize exactly those and publish again). Use create_presentation instead to have the server narrate.

NameTypeReqDescription
assetsarray–Files the document references relative to itself — fonts, images, SVG, Lottie, Rive, bundled audio cues. html-presentation/v1 requires these to be self-hosted, so a presentation that renders locally…
audioarray–One entry per slide you synthesized, from the JSON `bisque-voice` prints on stdout. `words`, `durationMs`, `size` and `hash` map across verbatim. Optional: omit a slide (or the whole array) and its a…
contextMdstring–Shared-with-viewer context.md.
designMdstring–Design frontmatter mapped to theme tokens.
handlestring–Publish under a specific channel handle you own.
indexHtmlstringyesFull html-presentation/v1 document (the presentation-format meta gate applies).
madeWitharray–Credit the models that made this: the model you are running as, and the engine that synthesized the audio you are uploading — e.g. ["Claude Opus 5", "Kokoro af_heart"]. Shown to viewers in the watch…
presentationIdstring–Stable id for idempotent re-publishes; defaults to slug-<hash(userId:slug)>.
slugstring–URL slug; defaults to a slugified title.
speechSpeednumber–Must match the speed you synthesized at — it is part of the audio cache key, so changing it on a re-publish makes every slide stale instead of carrying forward.
titlestring–Display title for the watch page and listings. Omit to use the title parsed from the document.
visibilitystring–unlisted (the default) is shareable by link and plays in chat-embedded players; private requires the owner to sign in, so an inline chat player shows a sign-in wall instead of playing — choose privat…
voiceIdstring–Records what actually spoke, e.g. kokoro:af_heart for a locally synthesized Kokoro voice. No audio is generated server-side.
voiceStabilitynumber–Records the stability setting you synthesized at. No audio is generated server-side.
NameTypeReqDescription
completeUrlstringyesPOST here after every PUT, echoing `files` back verbatim.
filesarrayyesEcho back verbatim as the complete call's `files`.
presentationIdstringyes–
publishIdstringyes–
reusedarrayyesSlide keys whose audio carried forward — no upload.
staleSlidesarrayyesNarrated slide keys that will publish SILENT — synthesize exactly these and publish again.
synthesizedarrayyesSlide keys this request supplied audio for.
uploadUrlsarrayyesOne pre-signed PUT per file to upload.
warningsarrayyes–
webUrlstringyesShareable watch URL.

No examples provided.

read_artifact_analytics ~161

Who opened a document or page you own, edit, or published: views, signed-in readers, and which Version each last opened. On a company document or page it names every member who can open it, with their opens and, for a document, whether they read the latest version; company admins read it for every company item. Use it to answer 'who has read the policy?' or 'has the team opened the dashboard?'. A reader list carries email addresses, so answer the question asked rather than pasting it.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
NameTypeReqDescription
artifact_idstringyes–
last_viewed_atstring|null––
published_version_numberinteger|null––
readersarray|nullyesCompany items only; null on a personal one.
typestring––
unique_viewersintegeryes–
versionsarray––
view_countintegeryes–

No examples provided.

read_artifact_results ~143

Every answer a page collected, by name: a survey's responses (one per person, with the questions), or the page's data documents with who wrote each. Only the page's owner, or an admin of the company that owns it, may read them. Use it to summarize a survey, count sign-ups, or say who has not answered. Answers carry names and email addresses: report what the user asked, not the raw rows.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
NameTypeReqDescription
artifact_idstringyes–
documentsarray|null––
kindstringyes–
published_version_numberinteger|null––
questionsarray|null––
responsesarray|null––
titlestring––
truncatedbooleanyes–

No examples provided.

read_board ~172

Read a Whiteboard (an Artifact made with spec bisque-canvas/v1) as structure: its frames, every shape with its text and the frame it sits in, what each arrow connects, and an outline with frames as headings, shapes as bullets and arrows as A → B. Pass region to read one area. Use it before changing a board, to answer a comment about it, or to turn the board into a document or a presentation.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
regionobject–Board coordinates of an area, as a comment pinned to a region carries them; only what overlaps it is returned.
NameTypeReqDescription
artifact_idstringyes–
framesarrayyes–
outlinestringyes–
shapesarrayyes–
truncatedbooleanyes–
urlstring––

No examples provided.

reply_to_artifact_thread ~95

Post a reply in a comment thread as the agent. Allowed only on activated threads (agent_activated true): someone mentioned the agent, or the agent started the thread. People see it as "Agent · via <your name>".

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…).
bodystringyes–
thread_idstringyesThe thread id (thr_…).
NameTypeReqDescription
artifact_idstring––
attachmentsarray––
authorobjectyesWho wrote it: { kind: "user", uid, name, handle, avatarUrl } or { kind: "agent", principal, name, via }.
bodystringyes–
created_atstringyes–
edited_atstring|null––
mentionsarray––
message_idstringyes–
reactionsobject––
thread_idstringyes–

No examples provided.

resolve_artifact_thread ~100

Mark a comment thread resolved (resolved: true) or reopen it (resolved: false), as the agent. Allowed only on activated threads. Resolve after you have addressed the comment, usually after republishing the Artifact; reply first so the person can see what changed.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…).
resolvedbooleanyes–
thread_idstringyesThe thread id (thr_…).
NameTypeReqDescription
agent_activatedbooleanyesTrue once someone mentioned the agent; only then may the agent reply or resolve.
anchorobjectyesWhere the thread is pinned: kind element (selector, snapshot, slide), text (quote), or page.
artifact_idstringyes–
created_atstringyes–
created_byobjectyesWho wrote it: { kind: "user", uid, name, handle, avatarUrl } or { kind: "agent", principal, name, via }.
last_message_atstringyes–
mentionsarray––
message_countintegeryes–
participantsarray––
previewstringyes–
resolved_atstring|null––
root_message_idstring––
statusstringyes–
thread_idstringyes–
updated_atstring––
version_idstring––
version_numberintegeryes–

No examples provided.

share_artifact ~262

Set who can open an Artifact you own. audience picks the rule; share_with is the complete list of named people (it replaces the previous list; omit it to keep the current one). Going public deletes every comment thread, so a public change on an Artifact with threads is refused unless delete_threads is true. Returns the URL to send.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
audiencestringyesWho can open the link. owner: only you. users: the people in share_with. public: anyone with the link.
delete_threadsboolean–Allow going public on an Artifact that has comment threads, deleting them.
listedboolean–Show it in listings (the company library, public discovery) rather than link-only. Default false.
share_witharray–People to grant access by email (or uid), with a role. [{ "email": "ana@acme.com", "role": "viewer" }]. viewer opens it; editor can also publish new content. Implies audience "users" when audience is…
NameTypeReqDescription
artifact_idstringyes–
audience_modestringyes–
discoverabilitystringyes–
external_sharing_allowedboolean––
grantsarrayyes–
public_sharing_allowedboolean––
urlstringyes–

No examples provided.

unpin_artifact ~76

Take an Artifact off the Pinned shelf of the user's own Artifacts library. The Artifact itself is untouched.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
NameTypeReqDescription
artifact_idstringyes–
pinnedbooleanyes–
titlestring––
urlstring––

No examples provided.

update_artifact ~599

Change an Artifact you own or edit. Pass content to publish a new Version of the page at the same URL (the whole document, not a diff; earlier Versions stay in the history). Pass title, description, icon, or icon_image to change those, and, in a call without content, expires_in_days or expires_at (null keeps it) to set when an Artifact you own is deleted. Any combination in one call. With content the call waits for the new Version to be live before returning. The new Version keeps the base Version's capabilities and state rules unless you pass capabilities or state.

NameTypeReqDescription
artifact_idstringyesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….
capabilitiesarray–What the page may do at run time. state.read and state.write give it JSON documents at window.bisque.state (get, patch, list, subscribe); viewer.identity tells it who is viewing (window.bisque.viewer…
contentstring–The complete new document, same type as before.
descriptionstring|null–null clears it.
expires_atstring|null–The same as expires_in_days, as an RFC 3339 moment. Pass one or the other. null cancels the expiry, so the Artifact is kept.
expires_in_daysinteger–Delete the Artifact this many days from now, as delete_artifact would: it sits in the owner's Trash for 30 days, then its files go. Only when the user asks for it to go away (a scratch page, a one-we…
iconstring|null–null clears it.
icon_imagestring|null–The page's own icon: the favicon in the browser tab and the icon a phone puts on its Home Screen. A data URL: an SVG (data:image/svg+xml,<svg …>) or a base64 PNG, JPEG, WebP, or GIF, at most 512 KB,…
stateobject–Who may read and write which paths of the page's data, by the minimum role: viewer (can open), contributor (a data grant, separate from editing the page), owner. Absent means: everyone who can open r…
titlestring––
NameTypeReqDescription
artifact_idstringyes–
audience_modestringyesWho can open it: owner, users, org, or public.
created_atstring––
descriptionstring––
discoverabilitystringyes–
expires_atstring–When it is deleted, as its owner asked; absent when it is kept.
group_idstring––
iconstring––
icon_image_urlstring|null–The page icon set with icon_image; null for the Bisque icon.
latest_version_idstring––
organization_idstring––
publication_errorobject|null––
publication_statusstring–ready means the URL serves this content now. queued or processing means it is still being prepared; call get_artifact to check. failed carries publication_error.
published_version_idstring|nullyesThe Version viewers see; null until a publication is ready.
titlestringyes–
typestringyes–
updated_atstring––
urlstringyesThe viewer page.
version_idstring–The Version this call authored.
version_numberinteger––
viewer_version_modestring––

No examples provided.

update_channel ~147

Update one of your channels. Set the description — the line a stranger reads in a search result or a link unfurl, at most 160 characters, empty to clear it and go back to naming the newest presentations. Set the avatar from an image URL, which is fetched, center-cropped square and resized. Pass either or both. Omit handle to use your default channel.

NameTypeReqDescription
descriptionstring–What the channel publishes, in the owner's words. Empty clears it.
handlestring–Which of your channel handles to update; defaults to your default username.
image_urlstring–https URL of the avatar image (any common format, ≤10 MB).
NameTypeReqDescription
channelUrlstringyesPublic channel page carrying the update.
descriptionstring|null–The stored line, or null when the write cleared it.
failedarray–Fields that did not apply, each with the reason. A field listed here left the channel unchanged; the ones in updated still took effect.
handlestringyes–
updatedarrayyesField names that were written.

No examples provided.

Install

How do I install the Bisque Presentations MCP server?

Bisque Presentations is a hosted endpoint at https://bisque.cloud/presentations/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 · bisque.cloud

# add to Claude Code
claude mcp add --transport http cloud-bisque-presentations 'https://bisque.cloud/presentations/mcp'
Common questions

What is the Bisque Presentations MCP server?

Bisque Presentations is an MCP server listed in the public MCP registry as cloud.bisque/presentations. Create narrated presentations from HTML, poll build status, list them, read one back as text. This page covers its hosted endpoint (https://bisque.cloud/presentations/mcp).

Is the Bisque Presentations MCP server safe to use?

Bisque Presentations scores 92 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 Bisque Presentations MCP server expose?

Bisque Presentations exposes 26 tools: get_presentation_spec, create_presentation, publish_narrated_presentation, get_presentation_status, list_presentations, and 21 more. Their descriptions and schemas cost roughly 6,124 tokens of context every time the server is loaded.

Does the Bisque Presentations MCP server require authentication?

Yes. Bisque Presentations asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Bisque Presentations MCP server still maintained?

Bisque Presentations is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Bisque Presentations MCP server?

VerifyMCP ran 14 checks on Bisque Presentations, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.