io.github.mafedelahoz/cuddlynest-mcp
NPM · CUDDLYNEST-MCP · SCANNED SEP 20
Search CuddlyNest hotels and read rooms, prices, availability and cancellation policies
Available components
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 Security92
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- 38 of 126 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mafedelahoz/mcp-cuddlynest). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 646 tokens (~323/item across 2 items; 2 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 Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the io.github.mafedelahoz/cuddlynest-mcp server?
io.github.mafedelahoz/cuddlynest-mcp runs locally as an npm package, launched with npx -y cuddlynest-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cuddlynest-mcp
claude mcp add mafedelahoz-cuddlynest-mcp -- npx -y cuddlynest-mcp
{
"mcpServers": {
"mafedelahoz-cuddlynest-mcp": {
"command": "npx",
"args": [
"-y",
"cuddlynest-mcp"
]
}
}
} {
"servers": {
"mafedelahoz-cuddlynest-mcp": {
"command": "npx",
"args": [
"-y",
"cuddlynest-mcp"
]
}
}
} codex mcp add mafedelahoz-cuddlynest-mcp -- npx -y cuddlynest-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mafedelahoz-cuddlynest-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"cuddlynest-mcp"
],
"enabled": true
}
}
} openclaw mcp add mafedelahoz-cuddlynest-mcp --command npx --arg -y --arg cuddlynest-mcp
mcp_servers:
mafedelahoz-cuddlynest-mcp:
command: "npx"
args: ["-y", "cuddlynest-mcp"] {
"McpServers": {
"mafedelahoz-cuddlynest-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"cuddlynest-mcp"
]
}
}
} assistant mcp add mafedelahoz-cuddlynest-mcp -t stdio -c npx -a -y cuddlynest-mcp
{
"mcpServers": {
"mafedelahoz-cuddlynest-mcp": {
"command": "npx",
"args": [
"-y",
"cuddlynest-mcp"
]
}
}
} 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.
- 19 Sept 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.
- 17 Sept 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.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/cuddlynest-mcp@0.2.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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mafedelahoz/mcp-cuddlynest |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mafedelahoz/mcp-cuddlynest/.github/workflows/publish-npm.yml@refs/tags/v0.2.1 |
| Rekor log index | 2754424665 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9179b26c44390115235677b8e221ad91ec7cc57dd5eaef94d3704a6df5a088c9699384bf082c011f40ef27229f5e7b957fe8cb44982e12f3ed70ecde8 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | playwright install chromium |
Background: Why install scripts are a supply-chain risk →
Dependencies 126 packages
| Packages resolved | 126 |
|---|---|
| Deprecated | 2 |
| Stale | 37 |
| 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 →
cuddlynest_listing_details Get CuddlyNest hotel rooms & prices ~302
Get details for a specific CuddlyNest hotel: static basics (name, location, description, amenities, images) from the listing page, plus room options, prices, availability and cancellation policies read from the public listing page rendered in a headless browser.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | number | – | Number of adults (default: 2) |
| checkin | string | – | Check-in date (YYYY-MM-DD) |
| checkout | string | – | Check-out date (YYYY-MM-DD) |
| childAges | array | – | Age of each child at check-in, e.g. [2, 7]. Sets `children` when given. |
| children | number | – | Number of children (default: 0, or derived from childAges) |
| currency | string | – | ISO 4217 currency code for prices (default: USD), e.g. USD, EUR, COP |
| hotel | string | yes | CuddlyNest hotel URL or numeric product_id. The product_id is the trailing number in a listing URL, e.g. https://www.cuddlynest.com/hotel/us/le-meridien-boston-cambridge-4264955 -> 4264955. |
| ignoreRobotsText | boolean | – | Ignore robots.txt for the listing-page fetch on this request. |
| infants | number | – | Number of infants (default: 0) |
| rooms | number | – | Number of rooms (default: 1) |
No output schema declared.
No examples provided.
cuddlynest_search Search CuddlyNest hotels ~344
Search CuddlyNest for a destination and the top hotels there. Returns place candidates (city/region + coordinates + total property count) and a list of hotels — name, listing URL, star + guest rating, and (when available) images, distance from the centre and key amenities. Pass a hotel's product_id from the results to cuddlynest_listing_details for live rooms and prices. The hotel list is top-matches scale (~10-60), not the full inventory.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | number | – | Number of adults (default: 2) |
| checkin | string | – | Check-in date (YYYY-MM-DD) |
| checkout | string | – | Check-out date (YYYY-MM-DD) |
| childAges | array | – | Age of each child at check-in, e.g. [2, 7]. Sets `children` when given. |
| children | number | – | Number of children (default: 0, or derived from childAges) |
| currency | string | – | ISO 4217 currency code for prices (default: USD), e.g. USD, EUR, COP |
| destination | string | yes | Destination to search (city / area), e.g. 'Santa Marta, Colombia'. |
| fullCityList | boolean | – | Also pull the broader city hotel list (~60) from the geo-page API when it can be resolved — a couple of extra requests. Default true. |
| hotelsOnly | boolean | – | Return only the hotel list, skipping place candidates (default false). |
| infants | number | – | Number of infants (default: 0) |
| rooms | number | – | Number of rooms (default: 1) |
No output schema declared.
No examples provided.
What is the io.github.mafedelahoz/cuddlynest-mcp server?
io.github.mafedelahoz/cuddlynest-mcp is listed in the public MCP registry as io.github.mafedelahoz/cuddlynest-mcp. Search CuddlyNest hotels and read rooms, prices, availability and cancellation policies. This page covers its npm package (cuddlynest-mcp).
Is the io.github.mafedelahoz/cuddlynest-mcp server safe to use?
io.github.mafedelahoz/cuddlynest-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.mafedelahoz/cuddlynest-mcp server expose?
io.github.mafedelahoz/cuddlynest-mcp exposes 2 tools: cuddlynest_search, cuddlynest_listing_details. Their descriptions and schemas cost roughly 646 tokens of context every time the server is loaded.
Is the io.github.mafedelahoz/cuddlynest-mcp server still maintained?
io.github.mafedelahoz/cuddlynest-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mafedelahoz/cuddlynest-mcp server under?
io.github.mafedelahoz/cuddlynest-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.