equinoxaifinance-rgb/civicdataforge-mcp

Developer guides: discover tools before billing · inspect the Bengaluru sample.
n8n: open our approved template in n8n's library · setup and result guide. Validate one public property request before a separate purchase; no credentials, evidence retrieval or automatic purchase in this bounded client.
**Start with one request:** try the no-charge input and purchase-option check, or copy the cURL walkthrough. This validates request syntax and current purchase options; it does not retrieve evidence, establish record coverage, or initiate payment.
CivicDataForge gives MCP-compatible agents structured access to official government records through a stable
credential-safe MCP relay backed by Apify. The official bundle exposes ten focused tools across unified evidence routing, property compliance, healthcare
integrity, regulated-facility safety, and Norwegian company evidence. Additional research products remain discoverable in the public
catalog without bloating the default MCP tool set.
Website:
Government data catalog:
Machine-readable catalog:
Apify Store:
Live STR proof:
Dated product proof:
Pricing at a glance
Tool discovery and the request check are free. Evidence calls are paid per result:
- Apify Store (Government Evidence Gateway): $0.01 per Actor start plus $0.10 per evidence packet on Apify's Free plan, lower on paid Apify plans.
- AWS Marketplace API/MCP: $0.10 per successful evidence request; failed requests and idempotent retries are not billed.
- One-off audits and weekly permit monitoring are also available.
Current prices and terms:
Add the remote MCP server
Use this Streamable HTTP endpoint:
In Claude Code:
Public initialize and tools/list discovery work without a credential. The hosted gateway supports two explicit caller-owned paths:
- For CivicDataForge's metered hosted evidence gateway, send the issued CivicDataForge key as either Authorization: Bearer YOUR_CIVICDATAFORGE_KEY or X-CivicDataForge-Key: YOUR_CIVICDATAFORGE_KEY.
- For direct Apify-backed Actor calls, send your own Apify token in X-Apify-Token:
The hosted CivicDataForge path meters successful bounded evidence requests through its active commercial route;
direct Actor calls remain caller-owned Apify usage. Each Actor has its own pricing, input schema, source notes,
and usage limits on its Store page. Never send a CivicDataForge key to an Actor endpoint. On the shared remote
MCP endpoint, keep the credential types in their documented headers and never send both in one request.
Run the installable stdio gateway
This repository also contains a credential-safe stdio distribution for MCP clients and Glama deployments.
Its ten schemas are available during discovery without a credential. Calls require the installing user's
own APIFY_TOKEN; the gateway never embeds a developer token and never returns the token in results.
For an MCP client, use node /absolute/path/to/server.mjs as the command and supply APIFY_TOKEN through
the client's secret environment configuration. Successful calls return the Apify run ID, dataset ID, status,
and up to 1,000 dataset rows. Larger outputs remain available from the caller-owned Apify dataset.
Portable GitHub and ModelScope configuration
MCP clients and ModelScope can install the open bridge directly from the canonical GitHub repository. The
bridge does not contain a CivicDataForge or Apify credential. Tool discovery works without a token; each
caller supplies APIFY_TOKEN for actual Actor runs.
This GitHub install route is the current portable STDIO path. Clients that support remote MCP directly can use
the hosted endpoint https://civicdataforge.pages.dev/mcp described above instead.
简体中文：接入与使用边界
CivicDataForge 为支持 MCP 的智能体提供结构化政府公开记录。默认网关包含统一证据路由器与九个聚焦工具，覆盖
房产合规、医疗排除名单、受监管设施安全与挪威企业证据。每条结果都应保留官方来源链接、覆盖范围与对应