Is the SiteCheck MCP server down?

mcp-registry/io.github.bck-stack/sitecheck · v1.8.5

Also listed as github/bck-stack/sitecheck-x402

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 15:23 UTC · handshake 767ms

As of 2026-11-22 15:23 UTC, the SiteCheck MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
808
outages (90d)
0
tools
225

225 pay-per-call agent tools: Polymarket, chain reads, DeFi, web, SEC, KYB, geo, dev, AI. x402

Point your MCP client at this streamable-http endpoint: https://api.sitecheck-api.workers.dev/mcp?ref=registry

Agent-readiness: B (82/100)

B (82/100): 1 error(s), 3 warning(s) across 225 tool(s); ~50,971 tokens of tool definitions.
Scores higher than 28% of 27,589 MCP servers Glimind has audited.
Its tool list costs an agent ~50,971 tokens per session — more than 99% of servers.
82 → 82 since 2026-11-16
no tool-poisoning patterns
Descriptions100
Safety hints85
Schemas90
Protocol100
Stability100
Token cost5
Reliability100
Client compatibility100

What to fix (4)

Loading this server's tool list costs an agent ~50,971 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

225 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

15 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: address_parse, books, cron, crypto_orderbook, crypto_whales and 10 more

2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: embed, json_validate

Auto-fix: 2 corrected tool definitions

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.bck-stack%2Fsitecheck/fixes

embed 1 change
{
  "name": "embed",
  "description": "Multilingual text embeddings (BGE-M3, 1024 dimensions) for up to 100 texts per call. For search, RAG and clustering. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.",
  "inputSchema": {
    "type": "object",
    "required": [
      "text"
    ],
    "properties": {
      "text": {
        "description": "A string or an array of up to 100 strings",
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true
  },
  "title": "Create multilingual text embeddings"
}
json_validate 1 change
{
  "name": "json_validate",
  "description": "Validates JSON data against a JSON Schema (draft 2020-12): valid true or false, and up to 50 errors with the instance path, the keyword and the message. Schema and data are each limited to 200 KB. Remote $ref targets are not fetched. No network call. Related tools on this server, for a different need: json_repair when you need to convert broken JSON to valid JSON and check it on a schema. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls ",
  "inputSchema": {
    "type": "object",
    "required": [
      "schema",
      "data"
    ],
    "properties": {
      "data": {
        "description": "Any JSON value to validate",
        "type": "string"
      },
      "schema": {
        "type": "object",
        "description": "A JSON Schema (object or boolean)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true
  },
  "title": "Check JSON data against a JSON Schema"
}

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.bck-stack/sitecheck"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.bck-stack/sitecheck"}) over MCP.

Passed

Largest tool definitions

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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.bck-stack%2Fsitecheck.svg)](https://glimind.com/server/mcp-registry%2Fio.github.bck-stack%2Fsitecheck?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.bck-stack%2Fsitecheck?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.bck-stack%2Fsitecheck.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1de4a126d9b57624…, first seen 2026-11-18, included at leaf 336272 of 384,229. Version history · verify what your client received.

Tools (225)

Compare: most reliable search servers · most reliable web servers · most reliable finance servers · most reliable ml servers · most reliable code servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the SiteCheck MCP server down right now?

As of 2026-11-22 15:23 UTC, the SiteCheck MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does SiteCheck MCP server provide?

SiteCheck MCP server advertises 225 tools, including address_parse, ai_crawlers, airports, apps_search, arxiv.

How do I install SiteCheck MCP server?

Point your MCP client at this streamable-http endpoint: https://api.sitecheck-api.workers.dev/mcp?ref=registry

Is the SiteCheck MCP server safe to connect to an AI agent?

Glimind scanned all 225 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 SiteCheck 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.

Feedback
Help us improve