Is the Joeyough Check MCP server down?

mcp-registry/io.github.joeyough/mcpcheck · v1.0.0

As of 2026-10-19 13:35 UTC, the Joeyough Check MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.8 hours.

Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.

claude mcp add --transport http joeyough-check-mcp-server https://mcpcheck.netlify.app/mcp

{
  "mcpServers": {
    "joeyough-check-mcp-server": {
      "type": "http",
      "url": "https://mcpcheck.netlify.app/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (84/100)

What to fix (3)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.joeyough%2Fmcpcheck/fixes

{
  "name": "check_mcp_trust",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "target"
    ],
    "properties": {
      "target": {
        "type": "string",
        "description": "Registry name (io.github.x/y), GitHub repo (owner/repo), or remote MCP URL (https://...)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.joeyough/mcpcheck"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.joeyough/mcpcheck"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~323 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• check_mcp_trust ~183 tokens
• scan_mcp_server ~140 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.joeyough%2Fmcpcheck.svg)](https://glimind.com/server/mcp-registry%2Fio.github.joeyough%2Fmcpcheck?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.joeyough%2Fmcpcheck?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.joeyough%2Fmcpcheck.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.joeyough%2Fmcpcheck.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.joeyough%2Fmcpcheck?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:93aad27194dde50d…, first seen 2026-10-17, included at leaf 14625 of 26,946. Version history · verify what your client received.

Tools (2)

• check_mcp_trust
• scan_mcp_server

Compare: most reliable security servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Joeyough Check MCP server down right now?

As of 2026-10-19 13:35 UTC, the Joeyough Check MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.8 hours.

How many tools does Joeyough Check MCP server provide?

Joeyough Check MCP server advertises 2 tools, including check_mcp_trust, scan_mcp_server.

How do I install Joeyough Check MCP server?

Point your MCP client at this streamable-http endpoint: https://mcpcheck.netlify.app/mcp

Is the Joeyough Check MCP server safe to connect to an AI agent?

Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Joeyough Check MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.