Is the Taylorsmithgg Crawl Census MCP server down?

mcp-registry/io.github.taylorsmithgg/crawl-census · v1.0.0

Also listed as github/taylorsmithgg/crawl-census-client, glama/taylorsmithgg/crawl-census

As of 2026-10-24 02:59 UTC, the Taylorsmithgg Crawl Census MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

Ask before you fetch: will this domain serve your crawler, refuse it, or charge it?

claude mcp add --transport http taylorsmithgg-crawl-census-mcp-server https://crawlcensus.com/mcp

{
  "mcpServers": {
    "taylorsmithgg-crawl-census-mcp-server": {
      "type": "http",
      "url": "https://crawlcensus.com/mcp"
    }
  }
}

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

Agent-readiness: B (82/100)

What to fix (3)

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.taylorsmithgg%2Fcrawl-census/fixes

{
  "name": "census_stats",
  "description": "Corpus-level statistics: how many measured domains block each AI crawler, mean access score, llms.txt adoption.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "submit_domains",
  "description": "Queue domains the census has not measured yet so a later crawl_preflight can answer them. This closes the loop crawl_preflight starts: anything it returns as unknown with measurable true is worth submitting, and the reply names any that were already fresh or that this census will never measure, so a caller looping over its own unknowns converges instead of resubmitting the same set. Queueing is a database write rather than a fetch, so the allowance is far higher than scan_site and submitted doma",
  "inputSchema": {
    "type": "object",
    "required": [
      "domains"
    ],
    "properties": {
      "domains": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Hostnames to queue. Up to 50 per call anonymously; an over-large batch is refused outright rather than partly queued."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

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.taylorsmithgg/crawl-census"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.taylorsmithgg/crawl-census"}) 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 (~1,086 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

• crawl_preflight ~270 tokens
• submit_domains ~222 tokens
• agent_profile ~190 tokens
• census_facts ~152 tokens
• scan_site ~116 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.taylorsmithgg%2Fcrawl-census.svg)](https://glimind.com/server/mcp-registry%2Fio.github.taylorsmithgg%2Fcrawl-census?ref=badge)

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

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.taylorsmithgg%2Fcrawl-census.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.taylorsmithgg%2Fcrawl-census?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:54f979a501e6f14d…, first seen 2026-10-17, included at leaf 14736 of 56,155. Version history · verify what your client received.

Tools (7)

• agent_profile
• census_facts
• census_stats
• crawl_preflight
• scan_site
• site_report
• submit_domains

Compare: most reliable data servers · most reliable web servers · most reliable other servers

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

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

FAQ

Is the Taylorsmithgg Crawl Census MCP server down right now?

As of 2026-10-24 02:59 UTC, the Taylorsmithgg Crawl Census MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Taylorsmithgg Crawl Census MCP server provide?

Taylorsmithgg Crawl Census MCP server advertises 7 tools, including agent_profile, census_facts, census_stats, crawl_preflight, scan_site.

How do I install Taylorsmithgg Crawl Census MCP server?

Point your MCP client at this streamable-http endpoint: https://crawlcensus.com/mcp

Is the Taylorsmithgg Crawl Census MCP server safe to connect to an AI agent?

Glimind scanned all 7 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 Taylorsmithgg Crawl Census 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.