io.allourthings/mcp-server
NPM · @ALLOURTHINGS/MCP-SERVER
AI-powered household inventory — query everything you own via natural language
Available components
Last scanned (13 hours ago)
Scores higher than 91% 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 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 94 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 matt-harding/allourthings-mcp). 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 350 tokens (~58/item across 6 items; 6 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 Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_item" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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
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 →
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.
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −3
- Stability: pass → 0.83 functional
- 14 Oct 26 +1
- Stability: 0.97 → pass security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 5 Nov 2026 · Analysed npm/@allourthings/mcp-server@0.2.0
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 | matt-harding/allourthings-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/matt-harding/allourthings-mcp/.github/workflows/publish.yml@refs/tags/v0.2.0 |
| Rekor log index | 1194336446 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2ba04928810a5025b0b3d420300670c613fa4864b2bdce1a9cd397553e508c22369029dac255a6ae3ecb7c6dc95ab372ac98736e45ccfcd3d7ea6de2e |
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 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
add_item ~169
Add a new item to the household inventory
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| category | string | – | Category (e.g. appliance, furniture, subscription) |
| currency | string | – | e.g. USD, GBP |
| features | array | – | – |
| images | array | – | Image file paths or URLs |
| location | string | – | Where the item is kept |
| manual_ref | string | – | URL or filename of the manual |
| model | string | – | – |
| name | string | yes | Name of the item |
| notes | string | – | – |
| purchase_date | string | – | ISO date string |
| purchase_price | number | – | – |
| retailer | string | – | – |
| tags | array | – | – |
| warranty_expires | string | – | ISO date string |
No output schema declared.
No examples provided.
delete_item ~25
Delete an item by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Item ID to delete |
No output schema declared.
No examples provided.
get_item ~34
Get a single item by ID or name
| Name | Type | Req | Description |
|---|---|---|---|
| id_or_name | string | yes | Item ID or name (fuzzy match) |
No output schema declared.
No examples provided.
list_items ~55
List all items, optionally filtered by category or tags
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category |
| location | string | – | Filter by location/room |
| tags | array | – | Filter by tags (all must match) |
No output schema declared.
No examples provided.
search_items ~31
Full-text search across all item fields
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query — matches across all item fields |
No output schema declared.
No examples provided.
update_item ~36
Update fields on an existing item
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Item ID to update |
| updates | object | yes | Fields to update |
No output schema declared.
No examples provided.
How do I install the io.allourthings/mcp-server server?
io.allourthings/mcp-server runs locally as an npm package, launched with npx -y @allourthings/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 · @allourthings/mcp-server
claude mcp add io-allourthings-mcp-server -- npx -y @allourthings/mcp-server
What is the io.allourthings/mcp-server server?
io.allourthings/mcp-server is listed in the public MCP registry as io.allourthings/mcp-server. AI-powered household inventory, query everything you own via natural language. This page covers its npm package (@allourthings/mcp-server).
Is the io.allourthings/mcp-server server safe to use?
io.allourthings/mcp-server scores 87 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. 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.allourthings/mcp-server server expose?
io.allourthings/mcp-server exposes 6 tools: add_item, get_item, list_items, update_item, delete_item, search_items. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.
Is the io.allourthings/mcp-server server still maintained?
io.allourthings/mcp-server 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 io.allourthings/mcp-server server under?
io.allourthings/mcp-server 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 io.allourthings/mcp-server server?
VerifyMCP ran 16 checks on io.allourthings/mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.