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.github.Srishesh-Archik/dyer-md

NPM · DYER-MD-MCP · SCANNED SEP 20

Access your dyer.md Markdown vault as a knowledge source for AI agents.

Available components

npm · dyer-md-mcp 0
0 this week 0 Trust /100

Recent critical change

CVE-2026-41242 affects this package (7 Aug 2026). See the changelog before you install this server.

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 Security72
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 400 of 473 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 163 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 run of this package 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 io.github.Srishesh-Archik/dyer-md MCP server?

io.github.Srishesh-Archik/dyer-md runs locally as an npm package, launched with npx -y dyer-md-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 · dyer-md-mcp

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

  • 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
  • 11 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
  • 7 Aug 26 0
    • CVE-2026-41242 affects this package: high ▼ critical
    • Score status: scored → failed ▼ critical
    • Known CVEs: CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. critical
    • GHSA-f88m-g3jw-g9cj no longer affects this package ▲ security
    • GHSA-p6gq-j5cr-w38f no longer affects this package ▲ security
    • CVE-2026-3520 no longer affects this package ▲ security
    • CVE-2026-5038 no longer affects this package ▲ security
    • CVE-2025-48997 no longer affects this package ▲ security
    • CVE-2026-3304 no longer affects this package ▲ security
    • CVE-2026-41907 no longer affects this package ▲ security
    • CVE-2026-39244 no longer affects this package ▲ security
    • CVE-2025-7338 no longer affects this package ▲ security
    • CVE-2026-5079 no longer affects this package ▲ security
    • CVE-2025-47935 no longer affects this package ▲ security
    • CVE-2025-47944 no longer affects this package ▲ security
    • CVE-2026-2359 no longer affects this package ▲ security
  • 2 Aug 26 0
    • CVE-2025-47944 affects this package: high ▼ security
    • CVE-2026-5038 affects this package: high ▼ security
    • GHSA-p6gq-j5cr-w38f affects this package: high ▼ security
    • CVE-2026-39244 affects this package: high ▼ security
    • CVE-2026-2359 affects this package: high ▼ security
    • CVE-2025-48997 affects this package: high ▼ security
    • CVE-2026-3304 affects this package: high ▼ security
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-5079 affects this package: high ▼ security
    • CVE-2026-3520 affects this package: high ▼ security
    • GHSA-f88m-g3jw-g9cj affects this package: high ▼ security
    • CVE-2025-47935 affects this package: high ▼ security
    • CVE-2025-7338 affects this package: high ▼ security
    • Provenance: unverified → fail ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • License: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Licence: MIT functional
  • 31 Jul 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
  • 27 Jul 26 0

    First indexed and scored.

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 20 Sept 2026 · Analysed npm/dyer-md-mcp@2.1.1

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 37 findings
ID CVE Severity Vector Fix available
GHSA-7q85-xj36-vmfc CVE-2026-77301 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vwc7-r8mq-g2x9 CVE-2026-76845 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N no
GHSA-xcpc-8h2w-3j85 CVE-2026-39244 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-7pqw-9j4j-h8q3 CVE-2026-19693 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H no
GHSA-jmr9-qjv8-65gv CVE-2026-56876 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N no
GHSA-44fp-w29j-9vj5 CVE-2025-47935 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4pg4-qvpc-4q3h CVE-2025-47944 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-535w-7cp7-47q4 CVE-2026-82333 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-5528-5vmv-3xc2 CVE-2026-3520 high yes
GHSA-72gw-mp4g-v24j CVE-2026-5079 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-fjgf-rc76-4x9p CVE-2025-7338 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-g5hg-p3ph-g8qg CVE-2025-48997 high yes
GHSA-qvfw-j98x-7q72 CVE-2026-77063 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-v52c-386h-88mc CVE-2026-2359 high yes
GHSA-wc9g-mqfw-jrwm CVE-2026-77078 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xf7r-hgr6-v32p CVE-2026-3304 high yes
GHSA-2x7j-588g-ccc2 CVE-2026-92596 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8m3c-c648-2xjj CVE-2026-92595 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-cc9r-2j5m-2m83 CVE-2026-92597 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-p6gq-j5cr-w38f CVE-2026-82659 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-wmmp-3585-3rmp CVE-2026-92598 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-2pr8-phx7-x9h3 CVE-2026-44294 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-66ff-xgx4-vchm CVE-2026-44293 high yes
GHSA-685m-2w69-288q CVE-2026-44289 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-75px-5xx7-5xc7 CVE-2026-44291 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-f38q-mgvj-vph7 CVE-2026-54269 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-fx83-v9x8-x52w CVE-2026-44292 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-jggg-4jg4-v7c6 CVE-2026-45740 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-jvwf-75h9-cwgg CVE-2026-44290 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-q6x5-8v7m-xcrf CVE-2026-44288 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-wcpc-wj8m-hjx6 CVE-2026-48712 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xq3m-2v4x-88gg CVE-2026-41242 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-f88m-g3jw-g9cj high yes
GHSA-rgj7-g3m4-5g8c high yes
GHSA-82x6-q7mm-w9cf CVE-2026-77465 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-v5mp-jgw5-2x6j CVE-2026-63376 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 400 packages
Packages resolved 400
Deprecated 3
Stale 167
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

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 io.github.Srishesh-Archik/dyer-md MCP server?

io.github.Srishesh-Archik/dyer-md is an MCP server listed in the public MCP registry as io.github.Srishesh-Archik/dyer-md. Access your dyer.md Markdown vault as a knowledge source for AI agents. This page covers its npm package (dyer-md-mcp).

Is the io.github.Srishesh-Archik/dyer-md MCP server still maintained?

io.github.Srishesh-Archik/dyer-md 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 io.github.Srishesh-Archik/dyer-md MCP server under?

io.github.Srishesh-Archik/dyer-md declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.