# io.github.jmshinhwa/runtime-eol-deploy-block-audit (npm · @readystack/runtime-eol-deploy-block-audit)

Finds the end-of-life runtimes an AI assistant still writes for you — node:20, python3.9, ubuntu-22

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@readystack/runtime-eol-deploy-block-audit`: 64/100 (this document), [markdown](https://verifymcp.io/servers/jmshinhwa-runtime-eol-deploy-block-audit/readystack-runtime-eol-deploy-block-audit.md), [page](https://verifymcp.io/servers/jmshinhwa-runtime-eol-deploy-block-audit/readystack-runtime-eol-deploy-block-audit)

## Channel facts

- Registry: `npm`
- Package: `@readystack/runtime-eol-deploy-block-audit`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN LICENSE.txt) isn't a recognized OSI-approved license.
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 166 tokens (~55/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: 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.

## Install

### How do I install the io.github.jmshinhwa/runtime-eol-deploy-block-audit MCP server?

io.github.jmshinhwa/runtime-eol-deploy-block-audit runs locally as an npm package, launched with npx -y @readystack/runtime-eol-deploy-block-audit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add jmshinhwa-runtime-eol-deploy-block-audit -- npx -y @readystack/runtime-eol-deploy-block-audit
```

### Cursor

```json
{
  "mcpServers": {
    "jmshinhwa-runtime-eol-deploy-block-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@readystack/runtime-eol-deploy-block-audit"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jmshinhwa-runtime-eol-deploy-block-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@readystack/runtime-eol-deploy-block-audit"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add jmshinhwa-runtime-eol-deploy-block-audit -- npx -y @readystack/runtime-eol-deploy-block-audit
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jmshinhwa-runtime-eol-deploy-block-audit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@readystack/runtime-eol-deploy-block-audit"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jmshinhwa-runtime-eol-deploy-block-audit --command npx --arg -y --arg @readystack/runtime-eol-deploy-block-audit
```

### Hermes

```yaml
mcp_servers:
  jmshinhwa-runtime-eol-deploy-block-audit:
    command: "npx"
    args: ["-y", "@readystack/runtime-eol-deploy-block-audit"]
```

### Netclaw

```json
{
  "McpServers": {
    "jmshinhwa-runtime-eol-deploy-block-audit": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@readystack/runtime-eol-deploy-block-audit"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add jmshinhwa-runtime-eol-deploy-block-audit -t stdio -c npx -a -y @readystack/runtime-eol-deploy-block-audit
```

### Other

```json
{
  "mcpServers": {
    "jmshinhwa-runtime-eol-deploy-block-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@readystack/runtime-eol-deploy-block-audit"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 64)

First indexed and scored.

## MCP tools (3)

### `check_text` (~56 tokens)

Runtime EOL and Deploy-Block Audit for Docker, CI and AWS Lambda - run all 54 checks on a text (free)

Input parameters:

- `path` (string): optional file name for context
- `text` (string, required): file contents

### `check_file` (~42 tokens)

Runtime EOL and Deploy-Block Audit for Docker, CI and AWS Lambda - run all checks on one file by path (free)

Input parameters:

- `path` (string, required)

### `check_dir` (~68 tokens)

Runtime EOL and Deploy-Block Audit for Docker, CI and AWS Lambda - sweep a folder and return every finding (licence; the full run is free for 7 days)

Input parameters:

- `dir` (string, required)
- `ext` (string): optional extension filter, e.g. .html

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/jmshinhwa-runtime-eol-deploy-block-audit/readystack-runtime-eol-deploy-block-audit#diagnostics

## Score history

- 2026-09-20: 64
- 2026-09-19: 64

## Common questions

### What is the io.github.jmshinhwa/runtime-eol-deploy-block-audit MCP server?

io.github.jmshinhwa/runtime-eol-deploy-block-audit is an MCP server listed in the public MCP registry as io.github.jmshinhwa/runtime-eol-deploy-block-audit. Finds the end-of-life runtimes an AI assistant still writes for you, node:20, python3.9, ubuntu-22. This page covers its npm package (@readystack/runtime-eol-deploy-block-audit).

### Is the io.github.jmshinhwa/runtime-eol-deploy-block-audit MCP server safe to use?

io.github.jmshinhwa/runtime-eol-deploy-block-audit scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.jmshinhwa/runtime-eol-deploy-block-audit MCP server expose?

io.github.jmshinhwa/runtime-eol-deploy-block-audit exposes 3 tools: check_text, check_file, check_dir. Their descriptions and schemas cost roughly 166 tokens of context every time the server is loaded.

### Is the io.github.jmshinhwa/runtime-eol-deploy-block-audit MCP server still maintained?

io.github.jmshinhwa/runtime-eol-deploy-block-audit 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.

## Links

- npm package: https://www.npmjs.com/package/@readystack/runtime-eol-deploy-block-audit
- Socket report: https://socket.dev/npm/package/@readystack/runtime-eol-deploy-block-audit
- Repository: https://github.com/jmshinhwa/readystack-themes
- Changelog RSS feed: https://verifymcp.io/servers/jmshinhwa-runtime-eol-deploy-block-audit/readystack-runtime-eol-deploy-block-audit.xml
- Changelog JSON feed: https://verifymcp.io/servers/jmshinhwa-runtime-eol-deploy-block-audit/readystack-runtime-eol-deploy-block-audit.json
- HTML version of this page: https://verifymcp.io/servers/jmshinhwa-runtime-eol-deploy-block-audit/readystack-runtime-eol-deploy-block-audit