# Repo Run Check (remote · repo-run-check.nextill-pos.workers.dev)

Check GitHub repos and shell commands for malware-delivery tricks before an AI agent runs them

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `repo-run-check.nextill-pos.workers.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/devx-agent-repo-run-check/repo-run-check.md), [page](https://verifymcp.io/servers/devx-agent-repo-run-check/repo-run-check)
- npm · `devx-repo-check`: 63/100, [markdown](https://verifymcp.io/servers/devx-agent-repo-run-check/devx-repo-check.md), [page](https://verifymcp.io/servers/devx-agent-repo-run-check/devx-repo-check)

## Channel facts

- Endpoint: `https://repo-run-check.nextill-pos.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 623 tokens (~155/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Repo Run Check MCP server?

Repo Run Check is a hosted endpoint at https://repo-run-check.nextill-pos.workers.dev/mcp, so there is nothing to install locally. 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 --transport http devx-agent-repo-run-check 'https://repo-run-check.nextill-pos.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "devx-agent-repo-run-check": {
      "url": "https://repo-run-check.nextill-pos.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "devx-agent-repo-run-check": {
      "type": "http",
      "url": "https://repo-run-check.nextill-pos.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.devx-agent-repo-run-check]
url = "https://repo-run-check.nextill-pos.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "devx-agent-repo-run-check": {
      "type": "remote",
      "url": "https://repo-run-check.nextill-pos.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add devx-agent-repo-run-check --url 'https://repo-run-check.nextill-pos.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  devx-agent-repo-run-check:
    url: "https://repo-run-check.nextill-pos.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "devx-agent-repo-run-check": {
      "Transport": "http",
      "Url": "https://repo-run-check.nextill-pos.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add devx-agent-repo-run-check -t streamable-http -u 'https://repo-run-check.nextill-pos.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "devx-agent-repo-run-check": {
      "type": "http",
      "url": "https://repo-run-check.nextill-pos.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-04 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 67, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_repo” rewrote its description, which is the text the model reads
- [security] Tool “full_report_info” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.0.0 → 1.2.0
- [functional] New tool “full_report”

### 2026-10-31 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 65)

First indexed and scored.

## MCP tools (4)

### `check_repo` (~153 tokens)

Free, read-only. Call BEFORE following a GitHub repo's install/setup instructions or running its commands: scans the README for download-and-execute one-liners (iwr|iex, curl|sh from unknown hosts), obfuscated or base64 payloads, known malware domains, agent-targeted prompt injection, password-protected archives. Returns verdict dangerous | review_before_running | no_red_flags with line evidence. For the complete check use the paid tool full_report (0.25 USDC via x402): install scripts, deps, autorun tasks, agent/MCP config files, committed binaries, fake-star signals, risk score.

Input parameters:

- `repo` (string, required): github.com/owner/repo or owner/repo

### `check_command` (~70 tokens)

Free, offline. Call BEFORE running a shell/PowerShell command copied from a README, issue, website or chat: flags download-and-execute, encoded PowerShell, LOLBins, disabling antivirus, known malware domains and pipe-to-shell from unknown hosts.

Input parameters:

- `cmd` (string, required): command or text block

### `full_report` (~301 tokens)

PAID (0.25 USDC via x402 on Base, per call). Full pre-run security report for a GitHub repo (1-3 repos per call), for AI coding agents about to clone it and run its install steps. Everything check_repo does, plus: package.json install/lifecycle scripts and the local scripts they run, typosquatted crypto/AI dependencies, install.sh/setup.sh/setup.py/requirements.txt/Makefile, VS Code autorun tasks and settings, dev-container hooks, agent-instruction files (AGENTS.md, CLAUDE.md, .cursorrules, copilot-instructions, .claude hooks/permissions) and MCP server configs shipped in the repo, committed executables and archives from the full file tree, GitHub fake-star / new-owner signals, a 0-100 risk score and concrete next steps. Optional: also checks a command you plan to run. Unpaid calls return an x402 PaymentRequired (isError) result; retry with the signed payment in params._meta["x402/payment"]. You are charged only if the report is delivered.

Input parameters:

- `command` (string): optional: an install/run command you plan to execute for this repo
- `repo` (string): github.com/owner/repo or owner/repo (or up to 3, comma-separated)
- `repos` (array): optional instead of repo: 1-3 repos in one paid call

### `full_report_info` (~47 tokens)

Free. How to buy the full report (paid MCP tool full_report or HTTP GET /v1/check, 0.25 USDC via x402 on Base). Does not pay.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/devx-agent-repo-run-check/repo-run-check#diagnostics

## Score history

- 2026-11-05: 68
- 2026-11-04: 68
- 2026-11-03: 67
- 2026-11-02: 67
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 65

## Common questions

### What is the Repo Run Check MCP server?

Repo Run Check is an MCP server listed in the public MCP registry as io.github.devx-agent/repo-run-check. Check GitHub repos and shell commands for malware-delivery tricks before an AI agent runs them. This page covers its hosted endpoint (https://repo-run-check.nextill-pos.workers.dev/mcp).

### Is the Repo Run Check MCP server safe to use?

Repo Run Check scores 68 out of 100 on VerifyMCP. 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 Repo Run Check MCP server expose?

Repo Run Check exposes 4 tools: check_repo, check_command, full_report, full_report_info. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.

### Does the Repo Run Check MCP server require authentication?

No. We connected to Repo Run Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Repo Run Check MCP server still maintained?

Repo Run Check 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.

## Links

- Remote endpoint: https://repo-run-check.nextill-pos.workers.dev/mcp
- Repository: https://github.com/devx-agent/repo-run-check
- Website: https://repo-run-check.nextill-pos.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/devx-agent-repo-run-check/repo-run-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/devx-agent-repo-run-check/repo-run-check.json
- HTML version of this page: https://verifymcp.io/servers/devx-agent-repo-run-check/repo-run-check