CivicDataForge Public-Records Data MCP server

CivicDataForge — Official Public-Records Data for AI Agents

Developer guides: discover tools before billing · inspect the Bengaluru sample.

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:

Add the remote MCP server

Use this Streamable HTTP endpoint:

https://civicdataforge.pages.dev/mcp

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 YOURCIVICDATAFORGEKEY or X-CivicDataForge-Key: YOURCIVICDATAFORGEKEY.
• For direct Apify-backed Actor calls, send your own Apify token in X-Apify-Token:

X-Apify-Token: YOUR_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 or an Apify token to the hosted gateway.

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.

npm ci
APIFY_TOKEN=YOUR_APIFY_TOKEN npm start

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.

Shortened. The full README is on GitHub.