civicdataforge-mcp

CivicDataForge provides structured government public records for MCP-enabled agents, achieving stable access through an Apify-based credential-secure MCP relay. The default official gateway includes a unified evidence router and nine focused tools, covering the following domains: unified evidence routing, short-term rental (STR) permits, Florida lodging licenses, property violations, the HHS-OIG LEIE healthcare exclusion list, restaurant inspections, multi-state and Texas childcare licensing, EPA ECHO facility evidence, and Norwegian business evidence. These tools are used for research and compliance assistance; each result should retain the official source link, coverage scope, and the corresponding Actor's data limitations, and does not replace the final determination of the competent authority.

Main capabilities:

• Provides structured government records access, covering U.S. and Norwegian data sources.
• Exposes ten focused tools by default, avoiding default MCP toolset bloat.
• Supports remote Streamable HTTP access and an installable stdio gateway.
• Public initialize and tools/list allow tool discovery without credentials.
• Supports two credential paths: the hosted evidence gateway uses a CivicDataForge key (Authorization: Bearer or X-CivicDataForge-Key); direct Apify Actor calls use the caller's own X-Apify-Token.
• Successful calls return the Apify run ID, dataset ID, status, and up to 1000 rows of dataset data.

Usage:

• Remote MCP server: use the Streamable HTTP endpoint. It can be added directly in Claude Code. Public initialize and tools/list require no credentials. The hosted gateway uses an activated CivicDataForge key. Direct Apify Actor calls use the caller's own Apify Token. Do not send both types of keys in the same request.
• Installable stdio gateway: the repository includes a credential-secure stdio distribution, with the command node /absolute/path/to/server.mjs, and APIFY_TOKEN is provided through the client secret environment configuration. The gateway does not embed developer Tokens, nor does it return Tokens in results.
• GitHub and ModelScope configurationNote: MCP clients and ModelScope can install the open bridge directly from the official GitHub repository. The bridge does not include CivicDataForge or Apify credentials. Tool discovery requires no token; each caller must provide an APIFY_TOKEN to actually run an Actor.
• Free request check: first-time users can start with the free request check, which does not retrieve records and does not initiate payment.
• Pricing: Apify Store (Government Evidence Gateway) charges $0.01 per Actor start plus $0.10 per evidence package (Free plan), with lower rates on paid Apify plans; AWS Marketplace API/MCP charges $0.10 per successful evidence request, with failed requests and idempotent retries not billed. One-time audits and weekly license monitoring are also available. Current pricing and terms are on the pricing page.

Use cases:

• Property compliance research: short-term rental permits, accommodation licenses, property violations.
• Healthcare compliance: HHS-OIG LEIE healthcare exclusion list screening.
• Regulated facility safety: restaurant inspections, childcare licensing, EPA ECHO facility evidence.
• Norwegian business evidence: using the Brønnøysundregistrene Central Coordinating Register, under the NLOD 2.0 license.
• China developer access: provides a complete Simplified Chinese onboarding manual, including copyable paths from a single identifier to an evidence credential (US property address, Indian company CIN).

Limitations:

• These tools are not consumer reports and must not be used as the sole basis for credit, insurance, employment, housing, or other eligibility decisions.
• Users should verify against original government records and comply with the applicable terms and restrictions of each data source.
• The India company Actor is not in the ten-tool default gateway; when needed, it can be called through the unified evidence router or loaded separately.
• The Chinese entry point only provides existing US property evidence and Indian company evidence, and does not claim coverage of Chinese enterprise registration databases, the GSXT bulk API, or local official Chinese records.
• Norwegian business data is subject to NLOD 2.0, and commercial reuse must comply with conditions such as attribution and change notices; if records contain personal data, buyers must still review privacy obligations and legal bases for their own processing purposes. This Actor excludes natural-person roles, contacts, and street address lines, and does not output KYC, procurement, sanctions, or eligibility determinations.
• The repository only publishes discovery metadata for the hosted remote MCP endpointand an installable stdio gateway; the data Actors still run on Apify. The gateway code, metadata, and documentation use the MIT license; government source terms and record-level usage restrictions remain source-specific and are documented on the corresponding Actor pages.
• The open bridge is not the CivicDataForge core. Source acquisition adapters, reconciliation pipelines, field presence and drift monitoring, source rights controls, evidence graph implementation, partner connectors, operational ledgers, and deployment configurations are maintained separately and are not under this repository's MIT license.
• Some run receipts and dataset objects are not public evidence surfaces; downstream verification should use public Actor/API metadata and caller-owned run receipts.