mcpbeat

CREHQ Location Intelligence MCP Server

io.github.groundroof/crehq-mcp-server
answering

CREHQ Location Intelligence is answering right now. Last checked 7 min ago. 53 installs a week from npm. Last commit 11 Jul 2026.

CREHQ entity affiliation, brand, site, franchise, credit, and location-intelligence tools.

Installs per day peak 192 · avg 18 · -4% w/w
a month agotoday
Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
129 ms
Response time
average over 24h
53
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add crehq-mcp-server --transport http https://mcp.crehq.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "crehq-mcp-server": {
      "url": "https://mcp.crehq.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.crehq-mcp-server]
url = "https://mcp.crehq.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "crehq-mcp-server": {
      "url": "https://mcp.crehq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "crehq-mcp-server": {
      "url": "https://mcp.crehq.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.crehq.com/mcp streamable-http needs key 137 ms 7 min ago

CREHQ Location Intelligence — questions

Answers built from our own checks of this server.

Why is there no tool list for CREHQ Location Intelligence?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is CREHQ Location Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 129 ms. The bar chart above shows every period we have measured.
How do I connect CREHQ Location Intelligence?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does CREHQ Location Intelligence need an API key?
Yes. Every time we knock, CREHQ Location Intelligence answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is CREHQ Location Intelligence?
It answers our handshake in 129 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use CREHQ Location Intelligence?
The npm package crehq-mcp-server was installed 53 times in the last week. Week over week that is -4%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is CREHQ Location Intelligence open source?
Yes — it is published under the NOASSERTION licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.