TrustScan
REMOTE · TRUST-SCAN-PRODUCTION.UP.RAILWAY.APP
Security scanner for MCP servers and skills: Unicode injection, patterns, secrets.
Available components
Last scanned (5 hours ago)
Scores higher than 81% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 13 Oct 26 0
- Server version: 4.0.11 → 4.1.0 functional
- 10 Oct 26 0
- Server version: 4.0.10 → 4.0.11 functional
- 8 Oct 26 +1
- Stability: 0.90 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 78
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.83 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Server version: 4.0.3 → 4.0.10 functional
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 5 Nov 2026 · Probed https://trust-scan-production.up.railway.app/mcp/
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trust-scan-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trust-scan-production.up.railway.app/mcp/ | Unreachable | ||
| http (plaintext) | http://trust-scan-production.up.railway.app/mcp/ | HTTPS enforced |
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 →
read_skill Read Skill ~50
Read a product skill file by its skill:// URI.
| Name | Type | Req | Description |
|---|---|---|---|
| uri | string | yes | e.g. skill://<product>/<skill-name>/SKILL.md Get valid URIs from `skills_list_tool`. |
Structured output declared, but exposes no named fields.
No examples provided.
skills_list_tool Skills List Tool ~51
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`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
trust_scan_file Scan Single File ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filepath | string | yes | absolute path of the file to scan |
Structured output declared, but exposes no named fields.
No examples provided.
trust_scan_server Scan MCP Server or Skill Package ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | – | package name for typosquat detection (e.g. "mcp-server") |
| path | string | yes | directory or file path to scan (on the TrustScan host) |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · trust-scan-production.up.railway.app
claude mcp add --transport http entradox-trust-scan 'https://trust-scan-production.up.railway.app/mcp/'
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 80 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?
Its publisher declares no required credentials for TrustScan. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the TrustScan MCP server still maintained?
TrustScan is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.