# TrustScan (remote · trust-scan-production.up.railway.app)

Security scanner for MCP servers and skills: Unicode injection, patterns, secrets.

- Trust score: 72/100 (medium)
- Change this week: −3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `trust-scan-production.up.railway.app`: 72/100 (this document), [markdown](https://verifymcp.io/servers/entradox-trust-scan/trust-scan-production.md), [page](https://verifymcp.io/servers/entradox-trust-scan/trust-scan-production)

## Channel facts

- Endpoint: `https://trust-scan-production.up.railway.app/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.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-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 370 tokens (~74/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 current MCP spec version (2026-07-28).

## Install

### How do I install the TrustScan MCP server?

TrustScan is a hosted endpoint at https://trust-scan-production.up.railway.app/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 entradox-trust-scan 'https://trust-scan-production.up.railway.app/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "entradox-trust-scan": {
      "url": "https://trust-scan-production.up.railway.app/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "entradox-trust-scan": {
      "type": "http",
      "url": "https://trust-scan-production.up.railway.app/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.entradox-trust-scan]
url = "https://trust-scan-production.up.railway.app/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "entradox-trust-scan": {
      "type": "remote",
      "url": "https://trust-scan-production.up.railway.app/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add entradox-trust-scan --url 'https://trust-scan-production.up.railway.app/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  entradox-trust-scan:
    url: "https://trust-scan-production.up.railway.app/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "entradox-trust-scan": {
      "Transport": "http",
      "Url": "https://trust-scan-production.up.railway.app/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add entradox-trust-scan -t streamable-http -u 'https://trust-scan-production.up.railway.app/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "entradox-trust-scan": {
      "type": "http",
      "url": "https://trust-scan-production.up.railway.app/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-09-18 (score 72, +1)

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

### 2026-09-16 (score 71, +1)

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

### 2026-09-15 (score 70, −5)

- [security regression] Authorization: partial → unverified
- [functional improvement] Schema quality: 101 → 74
- [functional] First check of Schema quality: 100
- [functional] New resource “trust-scan”
- [functional] New tool “read_skill”
- [functional] New tool “skills_list_tool”

### 2026-09-12 (score 75, +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-09-10 (score 74, +1)

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

### 2026-09-08 (score 73, +11)

- [security improvement] Authorization: unverified → partial
- [security] Tool “trust_scan_file” rewrote its description, which is the text the model reads
- [security] Tool “trust_scan_server” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 42 → 101
- [functional improvement] Tool coverage: 67% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “trust_scan_file” reworded the description of “filepath”
- [cosmetic] “trust_scan_server” reworded the description of “package_name”
- [cosmetic] Tool “trust_scan_file” changed its title: Trust Scan File → Scan Single File
- [cosmetic] Tool “trust_scan_server” changed its title: Trust Scan Server → Scan MCP Server or Skill Package

### 2026-09-07 (score 62)

First indexed and scored.

## MCP tools (4)

### `trust_scan_server` (~136 tokens)

Scan MCP Server or Skill Package

Security-scan an MCP server or skill package before trusting it.

Runs all four checks — invisible Unicode prompt-injection, dangerous code
patterns (MCP001–006), hardcoded secrets, typosquat package names — and
returns a 0-100 score, letter grade, and detailed findings. Run this on
any directory BEFORE wiring it into your agent. Read-only: never modifies
the scanned target.

Input parameters:

- `package_name` (string): package name for typosquat detection (e.g. "mcp-server")
- `path` (string, required): directory or file path to scan (on the TrustScan host)

### `trust_scan_file` (~66 tokens)

Scan Single File

Security-scan a single file for invisible Unicode, dangerous patterns, and secrets.

Returns a severity-weighted score and per-finding detail (rule, severity,
location). Read-only: the file is never modified.

Input parameters:

- `filepath` (string, required): absolute path of the file to scan

### `skills_list_tool` (~51 tokens)

Skills List Tool

List this product's skills. Each entry carries the SKILL.md URI,
its name and description, verbatim frontmatter, and a per-file
sha256 manifest. Read a body with `read_skill`.

### `read_skill` (~50 tokens)

Read Skill

Read a product skill file by its skill:// URI.

Input parameters:

- `uri` (string, required): e.g. skill://<product>/<skill-name>/SKILL.md  Get valid URIs from `skills_list_tool`.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/entradox-trust-scan/trust-scan-production#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 72
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 70
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 73
- 2026-09-08: 73
- 2026-09-07: 62

## Common questions

### What is the TrustScan MCP server?

TrustScan is an MCP server listed in the public MCP registry as io.github.entradox/trust-scan. Security scanner for MCP servers and skills: Unicode injection, patterns, secrets. This page covers its hosted endpoint (https://trust-scan-production.up.railway.app/mcp/).

### Is the TrustScan MCP server safe to use?

TrustScan scores 72 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 TrustScan MCP server expose?

TrustScan exposes 4 tools: trust_scan_server, trust_scan_file, skills_list_tool, read_skill. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.

### Does the TrustScan MCP server require authentication?

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

### Is the TrustScan MCP server still maintained?

TrustScan 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

- Remote endpoint: https://trust-scan-production.up.railway.app/mcp/
- Repository: https://github.com/entradox/trust-scan
- Changelog RSS feed: https://verifymcp.io/servers/entradox-trust-scan/trust-scan-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/entradox-trust-scan/trust-scan-production.json
- HTML version of this page: https://verifymcp.io/servers/entradox-trust-scan/trust-scan-production