InfoSlides — put content on a TV or screen
MCPB · INFOSLIDES-MCP-V1.9.0.MCPB
Put a PowerPoint, PDF, photo, or live data on any smart TV, menu board, or lobby screen.
Available components
Last scanned (6 hours ago)
Scores higher than 95% of MCPB 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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to arnibj/InfoSlides.MCP). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 16943 tokens (~141/item across 120 items; 120 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 Management70
- Stability observed for 21 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
- Structured output schemas are declared (97% 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 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 121 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- 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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +11
- Provenance: fail → pass ▲ security
- The attested source repository moved: arnibj/InfoSlides.MCP security
- Schema quality: 10543 → 16943 ▼ functional
- First check of Tool coverage: 97 functional
- Package version: 1.7.3 → 1.9.0 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Stability: unverified → 0.23 ▲ 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 5 Nov 2026 · Analysed mcpb/https://github.com/arnibj/InfoSlides.MCP/releases/download/v1.9.0/infoslides-mcp-v1.9.0.mcpb@1.9.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | mcpb |
| Reason | Verified |
| Discovered via | GitHub artifact attestations |
| Source repo | arnibj/InfoSlides.MCP |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/arnibj/InfoSlides.MCP/.github/workflows/release.yml@refs/tags/v1.9.0 |
| Rekor log index | 3649901072 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:f36a3060d3f9591c0facb0dfaa86d9f20dcb4e734858124596b94f683dcc1d8c |
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 →
show_media_on_device Show photo or clip on screen ~218
"Show this photo on the lobby screen for an hour." Puts a photo or video on a screen as a temporary takeover, then the normal schedule returns. Give filePath (a local file) or mediaUrl (a public address), not both. The screen switches once processing finishes (seconds for a photo, longer for video): poll get_show_status with the returned ids and report the percent. A photo whose shape does not match the screen gets a blurred fill, not black bars.
| Name | Type | Req | Description |
|---|---|---|---|
| caption | string|null | – | Optional name for the slideshow that is created. |
| deviceId | string | yes | Id of the screen. |
| filePath | string|null | – | Absolute path to a photo or video on disk. |
| mediaUrl | string|null | – | Public address of a photo or video to download instead. |
| until | string|null | – | How long it stays, e.g. '2026-10-01T17:00' (workspace local time) or with Z/offset; default 30 minutes from now. |
Structured output declared, but exposes no named fields.
No examples provided.
start_ai_studio_trial Start AI Studio trial ~52
Start the workspace's free AI Studio trial (7 days or 3 slides, prompt handler only). Once per workspace, so ask the person first. Calling it again while it runs returns the same trial.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
test_source_config Test content source settings ~112
Try a source's settings against the live service without saving anything, e.g. whether an RSS address works. Returns success and a plain-language message; a failed test is still an answer, not an error. Use before create_source. Limited to 10 calls a minute per workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| adapterType | string | yes | Adapter type from list_adapters, e.g. 'RssFeed'. |
| config | object|null | – | Config object as JSON, e.g. {"feedUrl":"https://..."}. |
Structured output declared, but exposes no named fields.
No examples provided.
undo_change Undo previous change ~142
Undo the last change: puts back what an earlier call changed. Calls that change something return an undo field; pass its body.token here within 24 hours. A deleted slide comes back, an added slide, takeover or paired screen is removed. Not covered: deleting a slideshow (restore_slideshow brings one back), and screen settings. If the same thing was changed again since, the answer is NeedsClarification: ask the person before sending force=true, which overwrites that later change.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | True to overwrite a later change; only after the person agreed. |
| token | string | yes | The token from the undo field of the earlier result. |
Structured output declared, but exposes no named fields.
No examples provided.
update_brand_guide Update brand guide draft ~183
Replace the brand guide DRAFT with the whole guide given (admin only). It never changes what slides use: a person confirms it on the Brand page, so say it is waiting for their approval and give them brandPageUrl. Colours are #rrggbb; low text contrast comes back as a warning. Values are typed in, nothing is read from files. Call get_brand_guide first and send back the full guide with your changes.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | object | yes | The whole guide as JSON, e.g. {"palette":{"primary":"#0a5c36","accent":"#e11d48","background":"#ffffff","text":"#111827"},"type":{"headingFontKey":"montserrat"},"voice":{"tone":"Friendly","preferredP… |
Structured output declared, but exposes no named fields.
No examples provided.
update_device Update screen details ~180
Rename a screen, change its resolution (use 1080x1920 for a screen turned on its end), or save where it is so "this screen" can be found later with list_devices near the person's position (do that once, right after pairing). Send only what should change.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | Id of the screen. |
| height | integer|null | – | New height in pixels; give with width. |
| latitude | number|null | – | Latitude in degrees; give with longitude. |
| locationName | string|null | – | Optional label for the location, e.g. 'Front lobby entrance'. |
| longitude | number|null | – | Longitude in degrees; give with latitude. |
| name | string|null | – | New name, e.g. 'Lobby TV'. |
| width | integer|null | – | New width in pixels; give with height. |
Structured output declared, but exposes no named fields.
No examples provided.
update_media Rename, move or share media file ~166
Rename a file in the media library, move it to a folder, or share it with other workspaces. Send only what should change. folderId moves it (moveToRoot puts it back at the top level); shared true lets other workspaces use it, false stops that. Only the workspace's own files can be changed.
| Name | Type | Req | Description |
|---|---|---|---|
| folderId | string|null | – | Folder to move it to (ids from list_media_folders). |
| mediaAssetId | string | yes | Id of the media file. |
| moveToRoot | boolean | – | True to move it out of its folder to the top level. |
| name | string|null | – | New name, up to 200 characters. |
| shared | boolean|null | – | True shares it with other workspaces, false stops sharing. |
Structured output declared, but exposes no named fields.
No examples provided.
update_schedule_entry Update schedule entry ~169
Change a daily time window in place (ids from get_schedule): what it plays, its start or end (HH:mm, workspace time zone) or its priority. Send only what should change. A window that would overlap another is refused. Returns the entry with the same warnings as add_schedule_entry and an undo token. The default content has no times: change it with assign_schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | Id of the screen. |
| endTime | string|null | – | New end, HH:mm. |
| entryId | string | yes | Id of the schedule entry. |
| priority | integer|null | – | New priority where windows overlap. |
| slideshowId | string|null | – | The slideshow to play in the window instead. |
| startTime | string|null | – | New start, HH:mm. |
Structured output declared, but exposes no named fields.
No examples provided.
update_slide Update slide properties ~383
Change one slide that is already in a slideshow: make it stay on screen longer or shorter (durationSeconds, 1 to 300), or hide it and bring it back (hidden), like "hide the Christmas slide", "show the offer for 20 seconds". For a live-data slide it can also change what it shows: switch to another template (templateId) or content source (sourceId), change the value on it (overrideData, e.g. {"price":"1.990 kr"}; only the fields you send change, and null removes one), or set its countdown. Text inside an uploaded PowerPoint page cannot be edited this way: say so, and offer to replace the file with replace_slideshow_file. Only what you pass changes. To take the slide out for good use delete_slide.
| Name | Type | Req | Description |
|---|---|---|---|
| countdown | array|null | – | Dynamic slides only: an array of countdown objects; [] clears the countdowns. |
| durationSeconds | number|null | – | How long the slide stays on screen, in seconds (1 to 300). |
| fieldMapping | object|null | – | Dynamic slides only: template field to source path mapping, replacing the current one. Generated automatically when the template or source changes and this is left out. |
| hidden | boolean|null | – | true hides the slide from playback, false shows it again. |
| overrideData | object|null | – | Dynamic slides only: values to change on the slide, as a JSON object with the template's field names. Merged into the current values; a null value removes a field. |
| slideId | string | yes | Id of the slide. |
| sourceId | string|null | – | Dynamic slides only: id of the content source to take data from (from list_sources). |
| templateId | string|null | – | Dynamic slides only: id of the template to switch to (from list_templates). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object|null | yes | – |
| undo | object | – | – |
| warnings | array|null | – | – |
No examples provided.
update_slide_design Update text slide design ~160
Change a slide made with add_designed_slide, such as new wording or another background. Send the whole design: read it with get_slide_design, change what you need and send all of it back, since a field left out is not kept. The slide is drawn again in place and keeps its position, hidden state and visibility rules. The same length and colour checks apply as when adding it. The result carries an undo token that puts the old design back.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | yes | The whole design as JSON, the design object from get_slide_design with your changes, e.g. {"heading":"Lunch moved to 1pm","backgroundColor":"#0F172A"}. |
| slideId | string | yes | Id of the slide. |
Structured output declared, but exposes no named fields.
No examples provided.
update_slideshow Update slideshow settings ~516
Change what is already playing on a screen: rename it, switch it between landscape and portrait, reorder the slides, turn the news ticker or the on-screen clock on or off, make every slide show for the same number of seconds, or force how it plays. Pass slideOrder as the complete list of slide ids in the sequence you want them shown. playbackMode overrides the usual rendered-video stream with a smooth HTML/CSS loop (or back again) for this one slideshow; pass "inherit" to drop the override and go back to whatever the workspace normally uses. Only what you pass changes. The screen picks the change up after a re-render: read the slideshow with get_slideshow until renderStatus is Completed before telling the person it is live.
| Name | Type | Req | Description |
|---|---|---|---|
| clockBackgroundColor | string|null | – | Clock background as a hex colour, e.g. #000000 or #00000080. |
| clockEnabled | boolean|null | – | true shows the on-screen clock, false hides it. |
| clockPosition | string|null | – | Where the clock sits: TopLeft, TopRight, BottomLeft or BottomRight. |
| clockShowDate | boolean|null | – | Whether the date shows under the time. |
| clockTextColor | string|null | – | Clock text as a hex colour, e.g. #ffffff. |
| defaultDurationSeconds | integer|null | – | How many seconds each slide shows unless it has its own duration, 1 to 300. "Make every slide show 15 seconds" is this. |
| height | integer|null | – | New height in pixels, if changing (requires width too). |
| playbackMode | string|null | – | "VideoStream" or "Html" to force how this slideshow plays; "inherit" to clear the override and fall back to the workspace default; omit to leave the current setting untouched. |
| shared | boolean|null | – | Whether other slideshows in the workspace may import slides from this one. |
| slideOrder | array|null | – | Complete ordered list of slide ids, if reordering. |
| slideshowId | string | yes | Id of the slideshow to update. |
| tickerEnabled | boolean|null | – | true shows the news ticker along the bottom of the screen, false turns it off (and clears its sources). |
| tickerSourceIds | array|null | – | Content sources whose headlines scroll in the ticker (ids from list_sources). |
| title | string|null | – | New title, if changing. |
| width | integer|null | – | New width in pixels, if changing (requires height too). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object|null | yes | – |
| undo | object | – | – |
| warnings | array|null | – | – |
No examples provided.
update_source Update live slide data ~181
Put fresh information on the screen: send today's menu, the new price, the current total, the updated opening hours. The display re-renders itself server-side — nobody has to touch the TV. The data must match the shape the template's example defines (see list_templates). For a slide on a push source the data goes to that source, exactly as push_data would send it. A restricted push-only (isk_dp_) key bound to the slide can call this, which is how an external system safely feeds one slide. Set dryRun=true to check the data without changing what is on screen.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | The new values, as a JSON object matching the template's example data. |
| dryRun | boolean | – | Check the data without changing what is on screen. |
| slideId | string | yes | Id of the slide to update. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object|null | yes | – |
| undo | object | – | – |
| warnings | array|null | – | – |
No examples provided.
update_source_settings Update source configuration ~112
Change a content source's name, config, fetch interval, or pause and resume it (ids from list_sources). To send data to a push source, use push_data instead.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object|null | – | New config object as JSON. |
| fetchIntervalSeconds | integer|null | – | New fetch interval in seconds. |
| isEnabled | boolean|null | – | False pauses fetching, true resumes it. |
| name | string|null | – | New display name. |
| sourceId | string | yes | Id of the source. |
Structured output declared, but exposes no named fields.
No examples provided.
update_template Update slide template ~177
Change a layout the workspace owns: title, html, css and/or schema (the data fields, e.g. {"fields":[{"name":"sales","type":"number"}]}). Send only what should change; new html without a schema takes its fields from the {{field}} tokens. Slides already using it pick up the change, so check get_template_usage first. A built-in layout cannot be changed: copy it with clone_template and change the copy.
| Name | Type | Req | Description |
|---|---|---|---|
| css | string|null | – | New stylesheet. |
| html | string|null | – | New HTML with {{field}} placeholders. |
| schema | object|null | – | The data fields as JSON, e.g. {"fields":[{"name":"sales","type":"number"}]}. |
| templateId | string | yes | Id of the template. |
| title | string|null | – | New title. |
Structured output declared, but exposes no named fields.
No examples provided.
update_tenant Update workspace settings ~109
Set the workspace time zone and/or locale. The time zone decides when schedules switch, what TV clocks show and when time-based slide conditions apply; set it early for a workspace outside Iceland. The locale sets number and date formats in rendered slides (changing it re-renders them).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string|null | – | Locale, e.g. 'en-GB' or 'is-IS'. |
| timeZone | string|null | – | IANA time zone, e.g. 'Europe/London'. |
Structured output declared, but exposes no named fields.
No examples provided.
upgrade_subscription Upgrade subscription ~249
Get the checkout link when the plan runs out: a second screen is needed, or the user wants self-updating slides fed by live data. Reach for this after a DeviceLimitReached or EntitlementRequired error rather than telling the user the thing cannot be done. Ask monthly or annual first and pass plan and billingPeriod: the result is then a Paddle checkout (/checkout?_ptxn=...) with its price, which needs no InfoSlides sign-in and pays for this workspace only. Without billingPeriod the link opens the plans page. Paying needs the person's clear yes to this plan at this price. Before they commit, tell them the price from the result, that it renews every month or year until cancelled, that they can cancel at any time and keep the plan until the period ends, and link https://infoslides.app/refund-policy. Then hand them the link, or open it and pay once they have said yes. A workspace that already pays gets its billing page, which needs a signed-in admin. The plan unlocks by itself once payment goes through.
| Name | Type | Req | Description |
|---|---|---|---|
| billingPeriod | string|null | – | monthly or annual. |
| plan | string|null | – | Starter, Professional or Business. |
Structured output declared, but exposes no named fields.
No examples provided.
upload_brand_logo Upload brand logo ~101
Put a logo image from the user's computer (up to 5 MB) into the brand guide draft, for light backgrounds (slot light), dark backgrounds (dark) or as a small square mark (icon). Returns the brand guide. A person still confirms the draft on the Brand page. Workspace admins only.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute path to the logo image on disk. |
| slot | string | – | light (default), dark or icon. |
Structured output declared, but exposes no named fields.
No examples provided.
upload_media Upload media file ~104
Send a picture or video from the user's own computer to their workspace — a photo of the specials board, a poster, a logo, a promo clip. Use this when the file is local and has no public web address. Returns an asset id; pass it to add_media_slide as mediaAssetId to put it on the screen. For a large file, check get_upload_limits first.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute path to the image or video file on disk. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object|null | yes | – |
| undo | object | – | – |
| warnings | array|null | – | – |
No examples provided.
upload_pptx Upload PowerPoint or PDF ~120
Put an existing PowerPoint or PDF on a screen. Uploads a .pptx or .pdf from the local disk and turns it into screen content — the server reads the slide/page count and the file's own resolution and starts rendering it into a video stream. This is usually the quickest route when the user says they already have a presentation or a PDF deck.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute path to a .pptx or .pdf file on disk. |
| title | string|null | – | Display name; defaults to the file name. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object|null | yes | – |
| undo | object | – | – |
| warnings | array|null | – | – |
No examples provided.
upload_slideshow Upload presentation file ~193
Create the content that will play on a screen — the lunch menu, this week's offers, opening hours, staff notices, a welcome message for a hotel lobby. A slideshow is a deck of slides that loops on the display. Resolution defaults to 1920x1080 for a normal wall-mounted TV; use 1080x1920 for a portrait screen standing on its end, which is common for menu boards and shop windows. Slides can be added inline here or later with add_media_slide.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | – | Screen height in pixels (default 1080 — landscape TV). |
| slides | array|null | – | Optional initial slides (mediaUrl and/or templateId, optional durationSeconds). |
| title | string | yes | What this content is, e.g. 'Lunch menu' or 'Reception welcome screen'. |
| width | integer | – | Screen width in pixels (default 1920 — landscape TV). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object|null | yes | – |
| undo | object | – | – |
| warnings | array|null | – | – |
No examples provided.
How do I install the InfoSlides — put content on a TV or screen MCP server?
InfoSlides — put content on a TV or screen ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, f36a3060d3f9591c0facb0dfaa86d9f20dcb4e734858124596b94f683dcc1d8c; the commands to do that are on this page. If it does not match, do not open it.
mcpb · infoslides-mcp-v1.9.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
f36a3060d3f9591c0facb0dfaa86d9f20dcb4e734858124596b94f683dcc1d8c
macOS / Linux
echo "f36a3060d3f9591c0facb0dfaa86d9f20dcb4e734858124596b94f683dcc1d8c infoslides-mcp-v1.9.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\infoslides-mcp-v1.9.0.mcpb).Hash -eq "f36a3060d3f9591c0facb0dfaa86d9f20dcb4e734858124596b94f683dcc1d8c"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the InfoSlides — put content on a TV or screen MCP server?
InfoSlides — put content on a TV or screen is an MCP server listed in the public MCP registry as io.github.arnibj/infoslides. Put a PowerPoint, PDF, photo, or live data on any smart TV, menu board, or lobby screen. This page covers its MCPB bundle (https://github.com/arnibj/InfoSlides.MCP/releases/download/v1.9.0/infoslides-mcp-v1.9.0.mcpb).
Is the InfoSlides — put content on a TV or screen MCP server safe to use?
InfoSlides — put content on a TV or screen scores 61 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 InfoSlides — put content on a TV or screen MCP server expose?
InfoSlides — put content on a TV or screen exposes 120 tools: invite_team_member, update_template, test_source_config, report_issue, list_brand_previews, and 115 more. Their descriptions and schemas cost roughly 16,532 tokens of context every time the server is loaded.
What licence is the InfoSlides — put content on a TV or screen MCP server under?
InfoSlides — put content on a TV or screen 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 InfoSlides — put content on a TV or screen MCP server?
VerifyMCP ran 12 checks on InfoSlides — put content on a TV or screen, 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 InfoSlides — put content on a TV or screen: 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 an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.