Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.allourthings/mcp-server

NPM · @ALLOURTHINGS/MCP-SERVER · SCANNED SEP 21

AI-powered household inventory — query everything you own via natural language

0 this week 91 Trust /100
Trust breakdown (7 categories)

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
  • 31 of 97 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 139 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 Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Install

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

# add to Claude Code
claude mcp add io-allourthings-mcp-server -- npx -y @allourthings/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "io-allourthings-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@allourthings/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-allourthings-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@allourthings/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add io-allourthings-mcp-server -- npx -y @allourthings/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-allourthings-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@allourthings/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-allourthings-mcp-server --command npx --arg -y --arg @allourthings/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  io-allourthings-mcp-server:
    command: "npx"
    args: ["-y", "@allourthings/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-allourthings-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@allourthings/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add io-allourthings-mcp-server -t stdio -c npx -a -y @allourthings/mcp-server
// mcp.json
{
  "mcpServers": {
    "io-allourthings-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@allourthings/mcp-server"
      ]
    }
  }
}
Changelog

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.

  • 21 Sept 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.

  • 19 Sept 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.

  • 16 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 13 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 11 Sept 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.

  • 10 Sept 26 −3
    • Stability: pass → 0.83 functional
Diagnostics

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 21 Sept 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 https://slsa.dev/provenance/v1
Subject digest sha512:2ba04928810a5025b0b3d420300670c613fa4864b2bdce1a9cd397553e508c22369029dac255a6ae3ecb7c6dc95ab372ac98736e45ccfcd3d7ea6de2e

Background: How many MCP packages publish verified provenance →

Dependencies 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~350 tokens

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 →

Tool Tokens
add_item ~169

Add a new item to the household inventory

NameTypeReqDescription
brandstring
categorystringCategory (e.g. appliance, furniture, subscription)
currencystringe.g. USD, GBP
featuresarray
imagesarrayImage file paths or URLs
locationstringWhere the item is kept
manual_refstringURL or filename of the manual
modelstring
namestringyesName of the item
notesstring
purchase_datestringISO date string
purchase_pricenumber
retailerstring
tagsarray
warranty_expiresstringISO date string

No output schema declared.

No examples provided.

delete_item ~25

Delete an item by ID

NameTypeReqDescription
idstringyesItem ID to delete

No output schema declared.

No examples provided.

get_item ~34

Get a single item by ID or name

NameTypeReqDescription
id_or_namestringyesItem ID or name (fuzzy match)

No output schema declared.

No examples provided.

list_items ~55

List all items, optionally filtered by category or tags

NameTypeReqDescription
categorystringFilter by category
locationstringFilter by location/room
tagsarrayFilter by tags (all must match)

No output schema declared.

No examples provided.

search_items ~31

Full-text search across all item fields

NameTypeReqDescription
querystringyesSearch query — matches across all item fields

No output schema declared.

No examples provided.

update_item ~36

Update fields on an existing item

NameTypeReqDescription
idstringyesItem ID to update
updatesobjectyesFields to update

No output schema declared.

No examples provided.

Common questions

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 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 21 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.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.