io.github.getcroissant/croissant
NPM · CROISSANT-MCP-SERVER
Search and book coworking spaces and conference rooms via Croissant.
Available components
Last scanned (21 hours ago)
Scores higher than 53% of npm servers
Category Productivity and Notes
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 250 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 384 tokens (~76/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 −1
- Stability: pass → 0.93 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/croissant-mcp-server@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
book_space ~128
Book a workspace or conference room
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | number | – | Number of attendees |
| booker_email | string | yes | Email for booking confirmation |
| booker_name | string | yes | Name of the person booking |
| date | string | yes | Date in YYYY-MM-DD format |
| end_time | string | yes | End time in HH:MM format (24h) |
| notes | string | – | Special requests or notes for the host |
| space_id | string | yes | The space ID to book |
| start_time | string | yes | Start time in HH:MM format (24h) |
No output schema declared.
No examples provided.
cancel_booking ~36
Cancel an existing booking
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | The booking ID to cancel |
| reason | string | – | Reason for cancellation |
No output schema declared.
No examples provided.
get_space_details ~39
Get detailed information about a specific workspace including photos, reviews, and full pricing
| Name | Type | Req | Description |
|---|---|---|---|
| space_id | string | yes | The space ID from search results |
No output schema declared.
No examples provided.
list_bookings ~35
List upcoming bookings for a user
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email of the booker | |
| status | string | – | – |
No output schema declared.
No examples provided.
search_spaces ~146
Search for available workspaces and conference rooms
| Name | Type | Req | Description |
|---|---|---|---|
| amenities | array | – | Required amenities (e.g. 'whiteboard', 'projector', 'wifi') |
| capacity | number | – | Minimum number of seats needed |
| date | string | yes | Date in YYYY-MM-DD format |
| end_time | string | – | End time in HH:MM format (24h) |
| location | string | yes | City, neighborhood, or address (e.g. 'Midtown Manhattan') |
| max_price_per_hour | number | – | Maximum price per hour in USD |
| space_type | string | – | – |
| start_time | string | – | Start time in HH:MM format (24h) |
No output schema declared.
No examples provided.
How do I install the io.github.getcroissant/croissant MCP server?
io.github.getcroissant/croissant runs locally as an npm package, launched with npx -y croissant-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · croissant-mcp-server
claude mcp add getcroissant-croissant -- npx -y croissant-mcp-server
What is the io.github.getcroissant/croissant MCP server?
io.github.getcroissant/croissant is an MCP server listed in the public MCP registry as io.github.getcroissant/croissant. Search and book coworking spaces and conference rooms via Croissant. This page covers its npm package (croissant-mcp-server).
Is the io.github.getcroissant/croissant MCP server safe to use?
io.github.getcroissant/croissant scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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.getcroissant/croissant MCP server expose?
io.github.getcroissant/croissant exposes 5 tools: search_spaces, get_space_details, book_space, cancel_booking, list_bookings. Their descriptions and schemas cost roughly 384 tokens of context every time the server is loaded.
Is the io.github.getcroissant/croissant MCP server still maintained?
io.github.getcroissant/croissant is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.