protogrid

Search / io.corrie/site-check

Corrie Site Check

R0· no sign-in

Score any public site's HTTPS, TLS certificate and security headers, with plain fixes. No auth.

v1.1.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality85new
Trust82of 100
Uptime, 30 days96%
Latency p50298 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "site-check": {
      "type": "http",
      "url": "https://corrie.io/mcp"
    }
  }
}
claude mcp add --transport http site-check https://corrie.io/mcp
[mcp_servers.site-check]
url = "https://corrie.io/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-check": {
      "type": "remote",
      "url": "https://corrie.io/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "site-check": {
      "type": "http",
      "url": "https://corrie.io/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=site-check&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vY29ycmllLmlvL21jcCJ9"
}
{
  "servers": {
    "site-check": {
      "type": "http",
      "url": "https://corrie.io/mcp"
    }
  }
}
{
  "mcpServers": {
    "site-check": {
      "httpUrl": "https://corrie.io/mcp"
    }
  }
}
extensions:
  "site-check":
    enabled: true
    name: "site-check"
    type: streamable_http
    uri: "https://corrie.io/mcp"
    timeout: 300

Quality 85 / 100new

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene93 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • warn
    tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations1 of 1 tools declare readOnlyHint or destructiveHint
  • pass
    tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
  • pass
    tools.token_costabout 503 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stabilityn/a · weight 15
  • n/a
    stability.changes, stability.rug_pulltool history recorded for 6 of the 7 days needed
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

1 tools, about 503 tokens to load them all · tool set f62364614206 · tools last changed 2026-10-14 · checked 2026-10-19 10:20 UTC

Tool changes

  • check_websitechangeddescription, input schema, output schemameaning changed
    before

    Loads the homepage of a public website once, the way a visitor's browser would, and reports its HTTPS setup and security headers (HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and others). Returns a score out of 100, a verdict, and each finding with its severity and a plain-English fix. Use it for questions like 'is example.com secure?' or 'what security headers is my site missing?'. It does not log in, submit forms, scan ports or test for vulnerabilities, and it refuses private or internal addresses.

    after · 43% of words in common

    Loads the homepage of one public website over HTTPS, the way a visitor's browser would, and reports its HTTPS setup, TLS certificate and security headers (Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, cookie flags, mixed content and server banners). Returns a score from 0 to 100, a verdict, the TLS certificate issuer and expiry date, and each finding with a severity (critical, high, medium or low) and a plain-English fix that includes nginx or Cloudflare examples. Use it for questions like 'is example.com secure?', 'what security headers is my site missing?', 'when does this site's certificate expire?' or 'why does Chrome say my site is not secure?'. Input is a bare domain (example.com) or an https:// address. A bare domain checks the homepage; if you include a path, that one page is loaded instead. It does not log in, submit forms, scan ports, crawl other pages or test for vulnerabilities, and nothing is stored. It refuses private, internal and local addresses, plain http://, ports other than 443 and addresses with a user name; those come back as an isError result with a message saying what to change. A check usually takes 1 to 10 seconds. Running it twice on the same site gives the same result unless the site changed. Read corrie://docs/scoring for how the score and verdict work.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 82 / 100

no-repository
provenance55
liveness98
freshness100
hygiene80

+dns-namespace +website +reachable +uptime-96% +updated-3d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://corrie.io/mcp streamable-httpnoneyes96%298 ms2025-06-182026-10-19

Tools (1)

check_websiteread-onlyLoads the homepage of one public website over HTTPS, the way a visitor's browser would, and reports its HTTPS setup, TLS certificate and security headers (Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, cookie flags, mixed content and server banners). Returns a score from 0 to 100, a verdict, the TLS certificate issuer and expiry date, and each finding with a severity (critical, high, medium or low) and a plain-English fix that includes nginx or Cloudflare examples. Use it for questions like 'is example.com secure?', 'what security headers is my site missing?', 'when does this site's certificate expire?' or 'why does Chrome say my site is not secure?'. Input is a bare domain (example.com) or an https:// address. A bare domain checks the homepage; if you include a path, that one page is loaded instead. It does not log in, submit forms, scan ports, crawl other pages or test for vulnerabilities, and nothing is stored. It refuses private, internal and local addresses, plain http://, ports other than 443 and addresses with a user name; those come back as an isError result with a message saying what to change. A check usually takes 1 to 10 seconds. Running it twice on the same site gives the same result unless the site changed. Read corrie://docs/scoring for how the score and verdict work.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "io.corrie/site-check",
  "title": "Corrie Site Check",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://corrie.io/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.1.0",
  "websiteUrl": "https://corrie.io/",
  "description": "Score any public site's HTTPS, TLS certificate and security headers, with plain fixes. No auth."
}