Server data from the Official MCP Registry
CREHQ chain-location tools for brands, sites, franchise data, credit signals, and whitespace.
CREHQ chain-location tools for brands, sites, franchise data, credit signals, and whitespace.
Remote endpoints: streamable-http: https://mcp.crehq.com/mcp
The CREHQ MCP server is a well-structured API wrapper with proper authentication and reasonable permissions aligned to its purpose. The codebase demonstrates good security practices including environment-based credential management, input validation via Zod, and error handling. Minor code quality concerns around broad exception handling do not significantly impact the overall security posture. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
4 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: CREHQ_API_KEY
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
A Model Context Protocol server that turns CREHQ's live location-intelligence REST API into native tools for Claude and other AI agents. Ask an agent "where should Chipotle open next?", "who has ever occupied this address?", "what are Aspen Dental's credit signals?", or "what are Planet Fitness's franchise fees and where are they expanding?" — and it can actually answer, backed by CREHQ's canonical, multi-source government-verified database of franchise & multi-unit brands, individual storefronts, FDD financials, credit signals, and site-level tenancy history.
This is a thin wrapper over CREHQ's existing production API
(https://crehq.com/wp-json/crehq/v1). It does not store data or modify
anything server-side — it authenticates with your API key and forwards calls.
Upgrade / paywall routing
crehq_request_upgrade — use when a sandbox user asks for premium data such as credit signals, FDD/Item 19, site-selection criteria, real-estate requirements, contacts, source provenance, change history, bulk downloads, whitespace, co-tenancy, or site timeline. With a free sandbox key, this records upgrade intent in CREHQ and returns the user a clear upgrade path instead of saying the data does not exist.Companies / brands
crehq_companies_list — list brands, filter by category & expansion statuscrehq_companies_search — resolve a brand name → CREHQ company id (start here)crehq_company_get — canonical brand profile, verified unit count, ownershipcrehq_company_credit_signals — credit profile, sponsor/issuer context, ratings, capital structurecrehq_company_franchise — FDD fees, royalties, investment, Item 19 figurescrehq_company_real_estate — site-selection criteria & target geographiescrehq_company_contacts — real-estate / development decision-maker contactsLocations
crehq_locations_list — store records by brand / state / categorycrehq_location_get — one location with full attributes & verification tracecrehq_locations_search — fuzzy multi-field location searchcrehq_locations_nearby — radius search around a lat/lng (trade-area mapping)crehq_locations_bulk — bulk pull by id list, brand list, or GeoJSON polygoncrehq_locations_events — cross-brand open/close/relocate lifecycle streamcrehq_location_history — full event log for one physical storeHistory & flagship differentiators
crehq_company_changes — date-bounded change feed for one brandcrehq_company_occupancy — point-in-time roster (footprint on a past date)crehq_site_timeline — every brand that ever occupied an address, over timePremium intelligence (Intel & Enterprise tiers)
crehq_whitespace — markets where competitors are present but the brand isn'tcrehq_co_tenancy — which brands cluster near this brand's storescrehq_location_site_profile — CREHQ Modeled Site Profile for one locationcrehq_company_site_pattern — empirical brand site pattern from observed footprint/contextcrehq_recent_location_context — recent observed/opening rows with traffic, demographics, and coverage flagsModeled Site Profile outputs must be described as CREHQ-modeled from observed location/context data, not as company-stated site requirements unless the response includes explicit stated-requirement provenance.
The Modeled Site Profile REST routes are staged pending explicit production
approval. Until those routes are published, these three tools may return a
404 even though the MCP catalog advertises them for local testing.
Datasets
crehq_datasets_list / crehq_dataset_get / crehq_dataset_download / crehq_dataset_categoriesTrends
crehq_trends_company — outlet/fee/financial time series for a brandcrehq_trends_geographic — metro/state concentration & velocitycrehq_live_xxxxxxxx….
Sandbox keys can run bounded location lookups (crehq_locations_list by
brand, and crehq_locations_nearby by radius). If the user asks for premium
intelligence, call crehq_request_upgrade; it records the requested topic
for CREHQ follow-up and tells the user what to upgrade.https://mcp.crehq.com/mcp and authorize
with that key.npx -y crehq-mcp-server and set
CREHQ_API_KEY.Use CREHQ to list five Planet Fitness locations in Illinois, then ask what premium CREHQ data is available for credit signals.Free sandbox keys expose bounded location lookup tools plus
crehq_request_upgrade. Paid/Intel keys expose broader API tools according to
the key's CREHQ tier.
Requires Node.js ≥ 18.
Install the published stdio server with npx:
CREHQ_API_KEY=crehq_live_xxxxx npx crehq-mcp-server
Or build from source:
git clone <this-repo> crehq-mcp-server
cd crehq-mcp-server
npm install
npm run build # compiles TypeScript → dist/
cp .env.example .env # then edit .env and set CREHQ_API_KEY
Verify your key against the live API before wiring up a client:
export CREHQ_API_KEY=crehq_live_xxxxx
./test.sh # exercises 6 read endpoints with curl
Run the server standalone (it speaks MCP over stdio, so it will wait for a client on stdin — Ctrl-C to exit):
CREHQ_API_KEY=crehq_live_xxxxx node dist/index.js
Add this to your claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"crehq": {
"command": "npx",
"args": ["-y", "crehq-mcp-server"],
"env": {
"CREHQ_API_KEY": "crehq_live_your_key_here"
}
}
}
}
Restart Claude Desktop. The CREHQ tools appear under the tools (🔌) menu.
Any stdio-capable MCP client (Claude Code, Cursor, Cline, Continue, the
mcp CLI, custom @modelcontextprotocol/sdk clients, etc.) connects the same
way — run node dist/index.js as the server command with CREHQ_API_KEY in
the environment.
Claude Code:
claude mcp add crehq --env CREHQ_API_KEY=crehq_live_xxxxx -- npx crehq-mcp-server
The hosted Cloudflare Worker version is kept in remote/. It provides the
same CREHQ connector as a remote MCP server at https://mcp.crehq.com/mcp, with
OAuth/key exchange and scope gating for premium tools. Its own deploy notes are
in remote/DEPLOY.md and connector-submission copy is in
remote/CONNECTOR-SUBMISSION.md.
The MCP Registry metadata lives in server.json, with registry ownership
declared by mcpName in package.json.
GitHub Actions owns the repeatable release path:
CI builds and tests the stdio package and the hosted Worker on every push.Deploy Remote MCP deploys remote/ changes to Cloudflare Workers and then
verifies https://mcp.crehq.com/health.Publish npm publishes the stdio package from a vX.Y.Z tag or manual
workflow dispatch. It skips safely when that package version already exists.Required repository secrets are already named:
NPM_TOKENCLOUDFLARE_API_TOKENCLOUDFLARE_ACCOUNT_ID| Env var | Required | Default | Purpose |
|---|---|---|---|
CREHQ_API_KEY | yes | — | Your crehq_live_… key |
CREHQ_API_BASE | no | https://crehq.com/wp-json/crehq/v1 | Override API base (staging/proxy) |
CREHQ_TIMEOUT_MS | no | 30000 | Per-request timeout in ms |
CREHQ_API_SURFACE | no | auto | Auto-detect sandbox vs full key; can be selfserve or full for debugging |
Tools never crash the agent's turn — failures come back as a readable message with a fix-it hint:
CREHQ_API_KEY and links the sandbox.crehq_request_upgrade.Retry-After; reminds you of the free-tier 2 req/s limit.Pagination, cache, and stream cursors (X-WP-Total, X-CREHQ-Next-Since,
X-CREHQ-Cache, rate-limit headers) are surfaced in a response metadata
footer on each result so the agent can paginate and poll correctly.
The build, typecheck, MCP protocol handshake, tool catalog, argument
validation, and the full HTTP request/response/error pipeline are verified
end-to-end against the live production API (a real request returns a real
403 Invalid or revoked API key with the correct hint). Fetching real data
rows requires a valid key — the sandbox key is delivered by email, so set
CREHQ_API_KEY and run ./test.sh to confirm live data responses.
MIT. CREHQ data is licensed separately per your API tier/contract.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.