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.

SuperSaaS Slots

PYPI · SUPERSAAS-SLOTS-MCP

Find available appointments on public SuperSaaS resource schedules

0 this week 92 Trust /100

Last scanned (14 hours ago)

Scores higher than 93% of PyPI servers

Category Productivity and Notes

Trust breakdown (7 categories)

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 Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects fastmcp 4.0.10, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to RichieB2B/supersaas-slots-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 54 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 250 tokens (~250/item across 1 items; 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed pypi/supersaas-slots-mcp@0.3.1

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo RichieB2B/supersaas-slots-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/RichieB2B/supersaas-slots-mcp/.github/workflows/release.yml@refs/tags/v0.3.1
Rekor log index 2979811073
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:cd26654bebc66bd6e69016f3e9f6c87ae02470d9637da265631127a2dd830326

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-7xgj-8392-5q4r medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-vqqp-x5qm-5qp4 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 15 packages
Packages resolved 15
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~250 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
find_available_slots ~250

List available slots in a public SuperSaaS resource or capacity schedule. Accepts a SuperSaaS schedule URL directly, or any public HTTPS page that links to exactly one schedule on supersaas.nl, supersaas.com or supersaas.co.uk, such as a salon's own booking page. Supports explicit, repeating-grid, and per-weekday start times, fixed duration, weekly opening hours, exceptions, booked appointments, buffer time, and booking-window limits. Capacity schedules list classes with remaining seats, their titles, locations, and counts. Date-only schedules such as nightly rentals report whole nights from check-in to check-out and add a `stays` summary of merged consecutive nights. Unsupported schedule rules are reported as errors.

NameTypeReqDescription
from_datestringyesFirst date, YYYY-MM-DD
max_resultsinteger–Maximum number of slots returned
respect_booking_windowboolean–Apply minimum and maximum advance-booking limits
schedule_urlstringyesPublic HTTPS SuperSaaS /schedule/ URL, or a business page linking to one
through_datestringyesLast date, inclusive, YYYY-MM-DD

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the SuperSaaS Slots MCP server?

SuperSaaS Slots runs locally as a PyPI package, launched with uvx supersaas-slots-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · supersaas-slots-mcp

# add to Claude Code
claude mcp add richieb2b-supersaas-slots-mcp -- uvx supersaas-slots-mcp
Common questions

What is the SuperSaaS Slots MCP server?

SuperSaaS Slots is an MCP server listed in the public MCP registry as io.github.RichieB2B/supersaas-slots-mcp. Find available appointments on public SuperSaaS resource schedules. This page covers its PyPI package (supersaas-slots-mcp).

Is the SuperSaaS Slots MCP server safe to use?

SuperSaaS Slots scores 92 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 21 November 2026. 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 SuperSaaS Slots MCP server expose?

SuperSaaS Slots exposes 1 tool: find_available_slots. Their descriptions and schemas cost roughly 250 tokens of context every time the server is loaded.

Is the SuperSaaS Slots MCP server still maintained?

SuperSaaS Slots 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 SuperSaaS Slots MCP server under?

SuperSaaS Slots 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 SuperSaaS Slots MCP server?

VerifyMCP ran 16 checks on SuperSaaS Slots, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.