Slidingbox Hydrate/Dehydrate
NPM · @SLIDINGBOX/HYDRATE-DEHYDRATE-MCP · SCANNED SEP 20
Encrypted one-time secret handoff, x402 pre-flight, and web page change checks and watches.
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 Security99
- 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
- 31 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (ISC).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 519 tokens (~103/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 Management60
- Stability observed for 18 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 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
How do I install the Slidingbox Hydrate/Dehydrate MCP server?
Slidingbox Hydrate/Dehydrate runs locally as an npm package, launched with npx -y @slidingbox/hydrate-dehydrate-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 · @slidingbox/hydrate-dehydrate-mcp
claude mcp add ai-slidingbox-hydrate-dehydrate -- npx -y @slidingbox/hydrate-dehydrate-mcp
{
"mcpServers": {
"ai-slidingbox-hydrate-dehydrate": {
"command": "npx",
"args": [
"-y",
"@slidingbox/hydrate-dehydrate-mcp"
]
}
}
} {
"servers": {
"ai-slidingbox-hydrate-dehydrate": {
"command": "npx",
"args": [
"-y",
"@slidingbox/hydrate-dehydrate-mcp"
]
}
}
} codex mcp add ai-slidingbox-hydrate-dehydrate -- npx -y @slidingbox/hydrate-dehydrate-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-slidingbox-hydrate-dehydrate": {
"type": "local",
"command": [
"npx",
"-y",
"@slidingbox/hydrate-dehydrate-mcp"
],
"enabled": true
}
}
} openclaw mcp add ai-slidingbox-hydrate-dehydrate --command npx --arg -y --arg @slidingbox/hydrate-dehydrate-mcp
mcp_servers:
ai-slidingbox-hydrate-dehydrate:
command: "npx"
args: ["-y", "@slidingbox/hydrate-dehydrate-mcp"] {
"McpServers": {
"ai-slidingbox-hydrate-dehydrate": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@slidingbox/hydrate-dehydrate-mcp"
]
}
}
} assistant mcp add ai-slidingbox-hydrate-dehydrate -t stdio -c npx -a -y @slidingbox/hydrate-dehydrate-mcp
{
"mcpServers": {
"ai-slidingbox-hydrate-dehydrate": {
"command": "npx",
"args": [
"-y",
"@slidingbox/hydrate-dehydrate-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.
- 20 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 19 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 89 → 103 ▼ functional
- Package version: 0.2.3 → 0.3.0 functional
- 18 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 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.2 → 0.2.3 functional
- 16 Sept 26 +12
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.88 ▲ functional
- 15 Sept 26 −11
- Stability: 0.40 → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: 0.88 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.1 → 0.2.2 functional
- 14 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.
- 12 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.
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/@slidingbox/hydrate-dehydrate-mcp@0.3.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 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 31 |
| 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 →
has_page_changed Has this page changed? ~105
Check whether a public web page has changed since it was last checked, by anyone: HTTP status, redirect target, content type, which sections changed (by position), and whether the set of scripts it loads changed. Returns what was observed and from where, never the page itself and never a safe/unsafe verdict. A page's first check is free; later checks cost $0.05 over x402.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The http(s) page to check. |
No output schema declared.
No examples provided.
retrieve_secret Retrieve a secret ~76
Read a secret stored on Slidingbox, using the token from store_secret. This destroys it: the token is dead the instant this succeeds, and a second call returns nothing. Reading is paid (x402) unless an evaluation key is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The sb_<pointer>#<key> token from store_secret. |
No output schema declared.
No examples provided.
store_secret Store a secret ~106
Encrypt a secret locally and store the ciphertext on Slidingbox. Returns one token that carries both the pointer and the decryption key. Hand that token to whoever should read it: the first read delivers the secret and destroys it. Slidingbox never sees the plaintext or the key.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The secret to store. Encrypted before it leaves this machine. |
| ttl_seconds | integer | – | How long it may sit unread, 60-900 seconds (default 900). |
No output schema declared.
No examples provided.
verify_endpoint Verify an x402 endpoint ~87
Check an x402 endpoint before paying it: whether it is live and payable, whether its live price and payee still match the CDP Bazaar catalog listing, and when either last changed. Use before the first payment to an endpoint you have not used. Paid (x402) unless an evaluation key is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | Absolute URL of the x402 resource to check. |
No output schema declared.
No examples provided.
watch_page Watch this page for changes ~145
Watch a public web page for 7 days: it is checked hourly (168 checks), and each time a check finds a change, a POST signed with HMAC-SHA256 goes to your https callback. One payment of $0.50 over x402; it ends by itself, with nothing to renew or cancel. Returns the watch id and the secret that verifies callbacks (X-Drift-Signature: sha256=<hex HMAC of the raw body>). Keep the secret: it is shown once.
| Name | Type | Req | Description |
|---|---|---|---|
| callback | string | yes | An https URL that will receive a signed POST on each change. |
| url | string | yes | The http(s) page to watch. |
No output schema declared.
No examples provided.
What is the Slidingbox Hydrate/Dehydrate MCP server?
Slidingbox Hydrate/Dehydrate is an MCP server listed in the public MCP registry as ai.slidingbox/hydrate-dehydrate. Encrypted one-time secret handoff, x402 pre-flight, and web page change checks and watches. This page covers its npm package (@slidingbox/hydrate-dehydrate-mcp).
Is the Slidingbox Hydrate/Dehydrate MCP server safe to use?
Slidingbox Hydrate/Dehydrate scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Slidingbox Hydrate/Dehydrate MCP server expose?
Slidingbox Hydrate/Dehydrate exposes 5 tools: store_secret, retrieve_secret, verify_endpoint, has_page_changed, watch_page. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.
Is the Slidingbox Hydrate/Dehydrate MCP server still maintained?
Slidingbox Hydrate/Dehydrate 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 Slidingbox Hydrate/Dehydrate MCP server under?
Slidingbox Hydrate/Dehydrate declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.