GoldenCheck
REMOTE · GOLDENCHECK-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED SEP 21
Auto-discover validation rules from data — scan, profile, health-score. No rules to write.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.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.
How do I install the GoldenCheck MCP server?
GoldenCheck is a hosted endpoint at https://goldencheck-mcp-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 · goldencheck-mcp-production.up.railway.app
claude mcp add --transport http benseverndev-oss-goldencheck 'https://goldencheck-mcp-production.up.railway.app/mcp/'
{
"mcpServers": {
"benseverndev-oss-goldencheck": {
"url": "https://goldencheck-mcp-production.up.railway.app/mcp/"
}
}
} {
"servers": {
"benseverndev-oss-goldencheck": {
"type": "http",
"url": "https://goldencheck-mcp-production.up.railway.app/mcp/"
}
}
} [mcp_servers.benseverndev-oss-goldencheck] url = "https://goldencheck-mcp-production.up.railway.app/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"benseverndev-oss-goldencheck": {
"type": "remote",
"url": "https://goldencheck-mcp-production.up.railway.app/mcp/",
"enabled": true
}
}
} openclaw mcp add benseverndev-oss-goldencheck --url 'https://goldencheck-mcp-production.up.railway.app/mcp/' --transport streamable-http
mcp_servers:
benseverndev-oss-goldencheck:
url: "https://goldencheck-mcp-production.up.railway.app/mcp/" {
"McpServers": {
"benseverndev-oss-goldencheck": {
"Transport": "http",
"Url": "https://goldencheck-mcp-production.up.railway.app/mcp/"
}
}
} assistant mcp add benseverndev-oss-goldencheck -t streamable-http -u 'https://goldencheck-mcp-production.up.railway.app/mcp/'
{
"mcpServers": {
"benseverndev-oss-goldencheck": {
"type": "http",
"url": "https://goldencheck-mcp-production.up.railway.app/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 27 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Aug 26 −15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 24 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.83 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
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 27 Aug 2026 · Probed https://goldencheck-mcp-production.up.railway.app/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of goldencheck-mcp-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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 502 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://goldencheck-mcp-production.up.railway.app/mcp/ | HTTP error | 502 | |
| http (plaintext) | http://goldencheck-mcp-production.up.railway.app/mcp/ | HTTPS enforced | 301 | https://goldencheck-mcp-production.up.railway.app/mcp/ |
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 →
analyze_data ~63
Analyze a data file to detect its domain, profile columns, and recommend a scanning strategy. Returns domain detection, column count, row count, strategy decisions, and alternative approaches.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the data file (CSV, Parquet, Excel) |
No output schema declared.
No examples provided.
approve_reject ~80
Approve (pin) or reject (dismiss) a review queue item. Decision must be 'pin' or 'dismiss'.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | yes | Decision: 'pin' (approve) or 'dismiss' (reject) |
| item_id | string | yes | Review item ID to update |
| reason | string | – | Optional reason for the decision |
No output schema declared.
No examples provided.
auto_configure ~79
Scan a data file, triage findings by confidence, and generate goldencheck.yml content from the pinned findings. Optionally accepts constraints to filter or adjust the generated config.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | object | – | Optional constraints: {min_confidence, severity_filter, include_columns, exclude_columns} |
| file_path | string | yes | Path to the data file |
No output schema declared.
No examples provided.
compare_domains ~48
Scan a file with every available domain pack (plus base/no-domain) and compare health scores. Recommends the best-fitting domain.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the data file |
No output schema declared.
No examples provided.
explain_column ~57
Get a natural-language health narrative for a specific column. Scans the file, profiles the column, and explains all findings.
| Name | Type | Req | Description |
|---|---|---|---|
| column | string | yes | Column name to explain |
| file_path | string | yes | Path to the data file |
No output schema declared.
No examples provided.
explain_finding ~80
Explain a single finding in natural language. Requires the finding as a JSON dict and the file_path to load a profile for context.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the data file (needed for profile context) |
| finding | object | yes | Finding dict with keys: severity, column, check, message, affected_rows, confidence, sample_values |
No output schema declared.
No examples provided.
get_column_detail ~43
Get detailed profile and findings for a specific column.
| Name | Type | Req | Description |
|---|---|---|---|
| column | string | yes | Column name to inspect |
| file_path | string | yes | Path to the data file |
No output schema declared.
No examples provided.
get_domain_info ~50
Get detailed info about a specific domain pack — lists all semantic types, their name hints, and suppression rules.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain pack name (e.g., healthcare, finance, ecommerce) |
No output schema declared.
No examples provided.
health_score ~46
Get the health score (A-F, 0-100) for a data file. Quick summary of overall data quality.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the data file |
No output schema declared.
No examples provided.
install_domain ~57
Download a community domain pack from the goldencheck-types repository and save it for use in future scans.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain pack name to install |
| output_path | string | – | Output path (default: goldencheck_domain.yaml) |
No output schema declared.
No examples provided.
list_checks ~22
List all available profiler checks and what they detect. No arguments needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_domains ~35
List all available domain packs (healthcare, finance, ecommerce, etc.). Domain packs provide specialized semantic type definitions for specific data domains.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pipeline_handoff ~76
Generate a structured quality attestation JSON for a data file. Includes health score, findings summary, pinned rules, and attestation status (PASS, PASS_WITH_WARNINGS, REVIEW_REQUIRED, FAIL).
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the data file |
| job_name | string | yes | Job name for the handoff record |
No output schema declared.
No examples provided.
profile ~76
Profile a data file and return column-level statistics: type, null%, unique%, min/max, top values, detected formats. Also returns a health score (A-F) based on finding severity.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the data file |
| sample_size | integer | – | Max rows to sample (default 100000) |
No output schema declared.
No examples provided.
review_queue ~43
List all pending review items for a given job. Returns items that need human decision (medium-confidence findings).
| Name | Type | Req | Description |
|---|---|---|---|
| job_name | string | yes | Job name to filter review items |
No output schema declared.
No examples provided.
review_stats ~40
Get review queue statistics for a job — counts of pending, pinned, and dismissed items.
| Name | Type | Req | Description |
|---|---|---|---|
| job_name | string | yes | Job name to get stats for |
No output schema declared.
No examples provided.
scan ~127
Scan a data file (CSV, Parquet, Excel) for data quality issues. Returns findings with severity, confidence, affected rows, and sample values. No configuration needed — rules are discovered from the data.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the data file (CSV, Parquet, Excel) |
| llm_boost | boolean | – | Enable LLM enhancement (requires API key env var) |
| llm_provider | string | – | LLM provider: 'anthropic' or 'openai' |
| sample_size | integer | – | Max rows to sample (default 100000) |
No output schema declared.
No examples provided.
suggest_fix ~69
Preview fixes for a data file without applying them. Shows what would change (columns, fix types, rows affected, before/after samples).
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the data file |
| mode | string | – | Fix mode: 'safe' (default) or 'aggressive' |
No output schema declared.
No examples provided.
validate ~69
Validate a data file against pinned rules in goldencheck.yml. Returns validation findings (existence, required, unique, enum, range checks).
| Name | Type | Req | Description |
|---|---|---|---|
| config_path | string | – | Path to goldencheck.yml (default: ./goldencheck.yml) |
| file_path | string | yes | Path to the data file |
No output schema declared.
No examples provided.
What is the GoldenCheck MCP server?
GoldenCheck is an MCP server listed in the public MCP registry as io.github.benseverndev-oss/goldencheck. Auto-discover validation rules from data, scan, profile, health-score. No rules to write. This page covers its hosted endpoint (https://goldencheck-mcp-production.up.railway.app/mcp/).
Is the GoldenCheck MCP server safe to use?
GoldenCheck scores 0 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 GoldenCheck MCP server expose?
GoldenCheck exposes 19 tools: scan, validate, profile, health_score, list_checks, and 14 more. Their descriptions and schemas cost roughly 1,160 tokens of context every time the server is loaded.
Does the GoldenCheck MCP server require authentication?
No. We connected to GoldenCheck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GoldenCheck MCP server still maintained?
GoldenCheck has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 20 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.