io.github.joeyough/mcpcheck
REMOTE · MCPCHECK.NETLIFY.APP · SCANNED OCT 1
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
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 Security63
- 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 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 234 tokens (~117/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.joeyough/mcpcheck MCP server?
io.github.joeyough/mcpcheck is a hosted endpoint at https://mcpcheck.netlify.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 · mcpcheck.netlify.app
claude mcp add --transport http joeyough-mcpcheck 'https://mcpcheck.netlify.app/mcp'
{
"mcpServers": {
"joeyough-mcpcheck": {
"url": "https://mcpcheck.netlify.app/mcp"
}
}
} {
"servers": {
"joeyough-mcpcheck": {
"type": "http",
"url": "https://mcpcheck.netlify.app/mcp"
}
}
} [mcp_servers.joeyough-mcpcheck] url = "https://mcpcheck.netlify.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joeyough-mcpcheck": {
"type": "remote",
"url": "https://mcpcheck.netlify.app/mcp",
"enabled": true
}
}
} openclaw mcp add joeyough-mcpcheck --url 'https://mcpcheck.netlify.app/mcp' --transport streamable-http
mcp_servers:
joeyough-mcpcheck:
url: "https://mcpcheck.netlify.app/mcp" {
"McpServers": {
"joeyough-mcpcheck": {
"Transport": "http",
"Url": "https://mcpcheck.netlify.app/mcp"
}
}
} assistant mcp add joeyough-mcpcheck -t streamable-http -u 'https://mcpcheck.netlify.app/mcp'
{
"mcpServers": {
"joeyough-mcpcheck": {
"type": "http",
"url": "https://mcpcheck.netlify.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.
- 1 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: 0.97 → pass security
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 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.
- 21 Sept 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.
- 19 Sept 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 1 Oct 2026 · Probed https://mcpcheck.netlify.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US | CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US | 16 Feb 2026 | 19 Mar 2027 | ECDSA 256 | SHA256-RSA | cd5d0afb0611b5bd9d692535c0ca7c4 |
| SANs: *.netlify.app, netlify.app | ||||||
| CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 30 Mar 2021 | 29 Mar 2031 | RSA 2048 | SHA256-RSA | cf5bd062b5602f47ab8502c23ccf066 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcpcheck.netlify.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| netlify.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 | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcpcheck.netlify.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcpcheck.netlify.app/mcp | HTTPS enforced | 301 | https://mcpcheck.netlify.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 →
check_mcp_trust ~136
Check if an MCP server is safe to install: returns a trust score (0-100, grade A-F). Accepts a registry name (io.github.x/y), a GitHub repo (owner/repo), or a remote MCP URL. For remote servers it live-connects and analyzes the actual exposed tools for tool-poisoning + capabilities, and checks the backing repo (maintenance, license, security policy, auth). Call BEFORE installing or recommending any MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Registry name (io.github.x/y), GitHub repo (owner/repo), or remote MCP URL (https://...). |
No output schema declared.
No examples provided.
scan_mcp_server ~98
Scan and inspect an MCP server for security issues before connecting it: live tool-poisoning analysis, exposed-tool inventory + capabilities, TLS, and repo trust signals. Same engine as check_mcp_trust. Accepts a registry name, GitHub repo, or remote MCP URL.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Registry name (io.github.x/y), GitHub repo (owner/repo), or remote MCP URL (https://...). |
No output schema declared.
No examples provided.
What is the io.github.joeyough/mcpcheck MCP server?
io.github.joeyough/mcpcheck is an MCP server listed in the public MCP registry as io.github.joeyough/mcpcheck. Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install. This page covers its hosted endpoint (https://mcpcheck.netlify.app/mcp).
Is the io.github.joeyough/mcpcheck MCP server safe to use?
io.github.joeyough/mcpcheck scores 81 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 io.github.joeyough/mcpcheck MCP server expose?
io.github.joeyough/mcpcheck exposes 2 tools: check_mcp_trust, scan_mcp_server. Their descriptions and schemas cost roughly 234 tokens of context every time the server is loaded.
Does the io.github.joeyough/mcpcheck MCP server require authentication?
No. We connected to io.github.joeyough/mcpcheck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.joeyough/mcpcheck MCP server still maintained?
io.github.joeyough/mcpcheck is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.