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.

404.directory

NPM · @MMVV1638/404-DIRECTORY-MCP · 2 COMPONENTS · SCANNED SEP 26

Risk preflight for AI Agent tool actions and Polymarket settlement and execution checks.

Available components

remote · 404.directory 24 npm · @mmvv1638/404-directory-mcp 50
0 this week 50 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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to MM-sheng/404-directory). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 26 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the 404.directory MCP server?

404.directory runs locally as an npm package, launched with npx -y @mmvv1638/404-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 · @mmvv1638/404-directory-mcp

# add to Claude Code
claude mcp add mm-sheng-404-directory -- npx -y @mmvv1638/404-directory-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mm-sheng-404-directory": {
      "command": "npx",
      "args": [
        "-y",
        "@mmvv1638/404-directory-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mm-sheng-404-directory": {
      "command": "npx",
      "args": [
        "-y",
        "@mmvv1638/404-directory-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mm-sheng-404-directory -- npx -y @mmvv1638/404-directory-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mm-sheng-404-directory": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mmvv1638/404-directory-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mm-sheng-404-directory --command npx --arg -y --arg @mmvv1638/404-directory-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mm-sheng-404-directory:
    command: "npx"
    args: ["-y", "@mmvv1638/404-directory-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mm-sheng-404-directory": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mmvv1638/404-directory-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mm-sheng-404-directory -t stdio -c npx -a -y @mmvv1638/404-directory-mcp
// mcp.json
{
  "mcpServers": {
    "mm-sheng-404-directory": {
      "command": "npx",
      "args": [
        "-y",
        "@mmvv1638/404-directory-mcp"
      ]
    }
  }
}
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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Aug 26 0
    • Package version: 0.10.2 → 0.10.3 functional
  • 29 Aug 26 0
    • Package version: 0.10.1 → 0.10.2 functional
  • 28 Aug 26 50
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 27 Aug 26 0
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: pass → unverified ▼ functional
    • Package version: 0.9.3 → 0.10.1 functional
    • Package version: 0.9.3 → 0.10.0 functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
    • Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
  • 24 Aug 26 0
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.9.2 → 0.9.3 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 26 Sept 2026 · Analysed npm/@mmvv1638/404-directory-mcp@0.10.3

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 MM-sheng/404-directory
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/MM-sheng/404-directory/.github/workflows/publish-mcp.yml@refs/tags/v0.10.3
Rekor log index 2647559791
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:67a3300b8b8f23031a091aacd7f02c28f9623b72273ac81df6e522a8027fe60da316b9cee40a804447416f064ed99dced7c769a792fbe140cc3f74842

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the 404.directory MCP server?

404.directory is an MCP server listed in the public MCP registry as io.github.MM-sheng/404-directory. Risk preflight for AI Agent tool actions and Polymarket settlement and execution checks. This page covers its npm package (@mmvv1638/404-directory-mcp).

Is the 404.directory MCP server safe to use?

404.directory scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 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.

Is the 404.directory MCP server still maintained?

404.directory is still listed as active in the MCP registry. We last reached this channel on 26 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 404.directory MCP server under?

404.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.