Is the Kylehawke Stack Locationlists MCP server down?

mcp-registry/io.github.kylehawke-stack/locationlists · v1.3.0

Also listed as github/kylehawke-stack/locationlists-mcp

healthy
Last checked 2026-10-22 22:41 UTC · handshake 382ms

As of 2026-10-22 22:41 UTC, the Kylehawke Stack Locationlists MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 13.5 hours.

uptime (30d checks)
99.5%
checks observed
3,828
outages (90d)
6
tools
16

US business location data: search, sample, count, query rows or buy CSVs (Stripe or x402 USDC).

Install Kylehawke Stack Locationlists MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http kylehawke-stack-locationlists-mcp-server https://locationlists.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "kylehawke-stack-locationlists-mcp-server": {
      "type": "http",
      "url": "https://locationlists.com/mcp"
    }
  }
}

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

Agent-readiness: C (71/100)

C (71/100): 1 error(s), 2 warning(s) across 16 tool(s); ~52,909 tokens of tool definitions.
Scores higher than 6% of 15,575 MCP servers Glimind has audited.
Its tool list costs an agent ~52,909 tokens per session — more than 99% of servers.
70 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions73
Safety hints100
Token cost0
Client compatibility70
Protocol100
Reliability100
Stability20

What to fix (5)

Loading this server's tool list costs an agent ~52,909 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 →

8 tool definition(s) exceed ~1,200 tokens each (largest: count_by_area, ~8,780).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~45,981 tokens every session. How to fix →

Tools: count_by_area, relate_locations, query_locations, create_query_checkout, count_locations and 3 more · saves ~45,981 tokens/session

14 parameter(s) across 4 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: count_by_area, create_query_checkout, query_locations, relate_locations

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 61 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

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

Agents: watch_tool({"toolId": "mcp-registry/io.github.kylehawke-stack/locationlists"}) 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. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kylehawke-stack%2Flocationlists.svg)](https://glimind.com/server/mcp-registry%2Fio.github.kylehawke-stack%2Flocationlists?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.kylehawke-stack%2Flocationlists?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kylehawke-stack%2Flocationlists.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kylehawke-stack%2Flocationlists.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.kylehawke-stack%2Flocationlists?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:b1bcc5f7950cb580…, first seen 2026-10-17, included at leaf 3983 of 48,558. Version history · verify what your client received.

Tools (16)

Compare: most reliable payments servers · most reliable data servers · most reliable email servers · most reliable search servers · most reliable communication 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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Kylehawke Stack Locationlists MCP server down right now?

As of 2026-10-22 22:41 UTC, the Kylehawke Stack Locationlists MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 13.5 hours.

How many tools does Kylehawke Stack Locationlists MCP server provide?

Kylehawke Stack Locationlists MCP server advertises 16 tools, including buy_dataset, check_order, cotenancy, count_by_area, count_locations.

How do I install Kylehawke Stack Locationlists MCP server?

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

Is the Kylehawke Stack Locationlists MCP server safe to connect to an AI agent?

Glimind scanned all 16 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 Kylehawke Stack Locationlists 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