CivicDataForge Government Evidence

What CivicDataForge Government Evidence does

CivicDataForge Government Evidence MCP server gives MCP-compatible agents a fixed set of government-record workflows backed by Apify Actors. The default bundle contains a unified evidence gateway and nine focused tools. Together they cover short-term-rental permits, Florida lodging licenses, property violations, HHS-OIG LEIE exclusions, restaurant inspections, childcare licensing, EPA ECHO facility records, and Norwegian company evidence.

The tools return structured records rather than a general-purpose web search. Outputs can include official source links, normalized jurisdiction fields, dates, match states, evidence receipts, source limitations, and status information. The Norway workflow uses Brønnøysundregistrene data and labels applicable output under NLOD 2.0. The EPA workflow reports bounded facility and compliance information while keeping its environmental-safety verdict as UNKNOWN.

How it works

CivicDataForge Government Evidence MCP server is available at https://civicdataforge.pages.dev/mcp as a Streamable HTTP service. Clients can call initialize and tools/list without credentials. Actual tool calls pass the caller’s Apify token in the X-Apify-Token header; each underlying Actor has its own input schema, pricing, source notes, and usage limits.

The local distribution runs as a Node-based stdio gateway. It forwards requests using the installer’s own APIFY_TOKEN, does not embed the publisher’s credential, and does not return that token in results. Successful runs provide an Apify run ID, dataset ID, status, and up to 1,000 dataset rows. Larger results remain in the caller-owned Apify dataset. Additional products, including India company-registry and other specialized workflows, are cataloged separately and are not all part of the default ten-tool bundle.

Setup and configuration

For a remote MCP client, configure the endpoint at https://civicdataforge.pages.dev/mcp and send an Apify token when invoking tools. An Apify account and token are required for execution.

For local use, install from the project’s GitHub route with npx, then provide the token through the client’s secret environment configuration:

{
  "mcpServers": {
    "civicdataforge": {
      "command": "npx",
      "args": ["-y", "github:equinoxaifinance-rgb/civicdataforge-mcp"],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_TOKEN"
      }
    }
  }
}

The repository also documents an alternative local start after dependency installation: APIFY_TOKEN=YOUR_APIFY_TOKEN npm start. A direct Node command can run the gateway from a checked-out copy.

Tools and capabilities

CivicDataForge Government Evidence MCP server includes these documented workflows:

• Route an identifier to a minimized evidence packet with the unified gateway.
• Check short-term-rental permits across 32 supported U.S. jurisdictions.
• Query Florida DBPR lodging-license files.
• Research municipal property code and building violations.
• Screen healthcare entities against HHS-OIG LEIE records.
• Review restaurant inspections and violations in supported jurisdictions.
• Inspect childcare licensing, inspection, and deficiency fields.
• Retrieve bounded EPA ECHO facility evidence.
• Verify Norwegian organizations by exact number or bounded company name.

The tools are intended to preserve source context and uncertainty for research and compliance assistance. They do not replace an agency’s final determination, and the results should not serve as the sole basis for credit, insurance, employment, housing, or other eligibility decisions.

Limitations and notes

Coverage is limited to the jurisdictions and fields published by each underlying source. Caller-side review is required for source terms, freshness, privacy obligations, and legal basis, especially where records contain personal data. The Norway Actor omits natural-person roles, direct contacts, and street-address lines. Its data may be commercially reused under NLOD 2.0 subject to attribution, change-disclosure, and other license conditions.

The gateway’s result size is capped at 1,000 dataset rows in successful responses. Some products remain outside the default tool set and must be accessed through their Actor pages or focused MCP URLs. Government-record output should be checked against the original source before making a consequential decision.