Sandwich Public Care Directory
NPM · SANDWICH-DIRECTORY-MCP · 2 COMPONENTS
Read-only MCP server for Sandwich aging-parent care resources and cost data.
Available components
Last scanned (17 hours ago)
Scores higher than 13% of npm servers
Category Health and Science
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.Unverified
Stability & Change Management0
- Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 4 categories
Categories scored 0 because we could not verify them: 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 (10)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- 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.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 22
First indexed and scored.
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 npm/sandwich-directory-mcp@0.1.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
The sandbox run completed and this package exposed no tools.
How do I install the Sandwich Public Care Directory MCP server?
Sandwich Public Care Directory runs locally as an npm package, launched with npx -y sandwich-directory-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 · sandwich-directory-mcp
claude mcp add com-joinsandwich-directory -- npx -y sandwich-directory-mcp
What is the Sandwich Public Care Directory MCP server?
Sandwich Public Care Directory is an MCP server listed in the public MCP registry as com.joinsandwich/directory. Read-only MCP server for Sandwich aging-parent care resources and cost data. This page covers its npm package (sandwich-directory-mcp).
Is the Sandwich Public Care Directory MCP server safe to use?
Sandwich Public Care Directory scores 37 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 Sandwich Public Care Directory MCP server expose?
Sandwich Public Care Directory exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the Sandwich Public Care Directory MCP server still maintained?
Sandwich Public Care Directory is still listed as active in the MCP registry. We last reached this channel on 5 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 Sandwich Public Care Directory MCP server under?
Sandwich Public Care Directory 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 Sandwich Public Care Directory MCP server?
VerifyMCP ran 10 checks on Sandwich Public Care Directory, covering Malware scan, Known CVEs, Install scripts, Dependency health and 6 more. 4 items could not be completed, a gap on our side rather than a finding about Sandwich Public Care Directory: Schema quality, Stability, Tool coverage and Tool safety. 4 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.