CivicDataForge โ Official Public-Records Data for AI Agents
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: https://civicdataforge.pages.dev
Government data catalog: https://civicdataforge.pages.dev/government-data-api
Machine-readable catalog: https://civicdataforge.pages.dev/api-catalog.json
Apify Store: https://apify.com/civicdataforge
Live STR proof: https://apify.com/civicdataforge/str-permit-registry/examples/check-orlando-str-permits
Dated product proof: https://civicdataforge.pages.dev/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: https://civicdataforge.pages.dev/pricing.md
Add the remote MCP server
Use this Streamable HTTP endpoint:
https://civicdataforge.pages.dev/mcp
In Claude Code:
claude mcp add --transport http civicdataforge 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 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:
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. 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.
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.
{
"mcpServers": {
"civicdataforge": {
"command": "npx",
"args": ["-y", "github:equinoxaifinance-rgb/civicdataforge-mcp"],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN"
}
}
}
}
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 ็ๆบ่ฝไฝๆไพ็ปๆๅๆฟๅบๅ
ฌๅผ่ฎฐๅฝใ้ป่ฎค็ฝๅ
ณๅ
ๅซ็ปไธ่ฏๆฎ่ทฏ็ฑๅจไธไนไธช่็ฆๅทฅๅ
ท๏ผ่ฆ็
ๆฟไบงๅ่งใๅป็ๆ้คๅๅใๅ็็ฎก่ฎพๆฝๅฎๅ
จไธๆชๅจไผไธ่ฏๆฎใๆฏๆก็ปๆ้ฝๅบไฟ็ๅฎๆนๆฅๆบ้พๆฅใ่ฆ็่ๅดไธๅฏนๅบ
Actor ็ๆฐๆฎ้ๅถ๏ผ่ฟไบๆฐๆฎ็จไบ็ ็ฉถๅๅ่ง่พ
ๅฉ๏ผไธๆฟไปฃไธป็ฎกๆบๅ
ณ็ๆ็ป่ฎคๅฎใ
ๅฝๅๅฏ็จ็่ฟ็จ Streamable HTTP ๆฅๅ
ฅๅฐๅไธบ๏ผ
https://civicdataforge.pages.dev/mcp
ๅ
ฌๅผ็ initialize ไธ tools/list ๆ ้ๅญ่ฏใ้ฆๆฌกไฝฟ็จๅฏๅ
่ฎฟ้ฎ ๅ
่ดน่ฏทๆฑๆฃๆฅ๏ผๅฎไธๆฃ็ดข่ฎฐๅฝ๏ผไนไธๅ่ตทไปๆฌพใ
ๆ็ฎก่ฏๆฎ็ฝๅ
ณไฝฟ็จๅทฒๆฟๆดป็ CivicDataForge ๅฏ้ฅ๏ผ้่ฟ Authorization: Bearer YOUR_CIVICDATAFORGE_KEY ไผ ้ใ
ๅฆ้ๆฉ็ดๆฅ่ฟ่ก Apify Actor๏ผๅไฝฟ็จ่ฐ็จๆน่ชๅทฑ็ X-Apify-Token: YOUR_APIFY_TOKENใๅไธ่ฏทๆฑไธ่ฆๅๆถๅ้ไธค็ฑปๅฏ้ฅใ
CivicDataForge ไธๅจไปๅบใnpm ๅ
ๆ่ฟๅ็ปๆไธญๅตๅ
ฅๅๅธ่
Tokenใ
็ฎไฝไธญๆๅฎๆดๆฅๅ
ฅๆๅๆไพไธคไธชไปๅไธๆ ่ฏ็ฌฆๅฐ่ฏๆฎๅญ่ฏ็ๅฏๅคๅถ่ทฏๅพ๏ผไธไธชๅทฒๆฏๆ็พๅฝ่พๅบ็
็ฉไธๅฐๅ๏ผไปฅๅไธไธชๅฐๅบฆๅ
ฌๅธ CINใๆๅๆ็กฎๅๅบๅๆญฅ REST ็ซฏ็นใ่พๅ
ฅใๆฅๆบๅญๆฎตใๆฐ้ฒๅบฆๅญๆฎตใ
SHA-256 ๅญ่ฏๅ็ไบงๅผๆญฅ่ฟ่กๆนๅผ๏ผ
https://civicdataforge.pages.dev/zh-cn-developer
ๆบๅจๅฏ่ฏป็ๆฌ๏ผhttps://civicdataforge.pages.dev/zh-cn-developer.json
ๅฐๅบฆๅ
ฌๅธ Actor ไธๅจๅๅทฅๅ
ท้ป่ฎค็ฝๅ
ณไธญ๏ผ้่ฆๆถๅฏ้่ฟ็ปไธ่ฏๆฎ่ทฏ็ฑๅจ่ฐ็จๆๅ็ฌๅ ่ฝฝ๏ผ
https://mcp.apify.com/?tools=civicdataforge/india-company-registry
่ฏฅไธญๆๅ
ฅๅฃๅชๆไพ็ฐๆ็พๅฝๆฟไบง่ฏๆฎๅๅฐๅบฆๅ
ฌๅธ่ฏๆฎ๏ผไธๅฃฐ็งฐไธญๅฝไผไธ็ป่ฎฐๆฐๆฎๅบใGSXT ๆน้
API ๆไธญๅฝๆฌๅฐๅฎๆน่ฎฐๅฝ่ฆ็ใ
ModelScope ไธๆฌๅฐ MCP ๅฎขๆท็ซฏๅฏ็ดๆฅไปๅฎๆน GitHub ไปๅบๅฎ่ฃ
ๅผๆพ็ฝๅ
ณ๏ผ
{
"mcpServers": {
"civicdataforge": {
"command": "npx",
"args": ["-y", "github:equinoxaifinance-rgb/civicdataforge-mcp"],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN"
}
}
}
}
่ฏฅ GitHub ๅฎ่ฃ
ๆนๅผๅไธๆน Apify ๆ็ฎก็ฝๅ
ณๅไธบๅฝๅๅฏ็จ่ทฏๅพใๅไธช้ป่ฎคๅทฅๅ
ทๅ
ๆฌ็ปไธ่ฏๆฎ่ทฏ็ฑๅจใ็ญ็ง่ฎธๅฏใไฝ็ฝ้่พพๅทไฝๅฎฟๆง็
งใ
ๆฟไบง่ฟ่งใHHS-OIG LEIE ๅป็ๆ้คๅๅใ้คๅ
ๆฃๆฅใๅคๅทไธๅพทๅทๆ่ฒ่ฎธๅฏใEPA ECHO ่ฎพๆฝ่ฏๆฎๅๆชๅจไผไธ่ฏๆฎใ
ๆชๅจไผไธๆฐๆฎ้็จ NLOD 2.0๏ผๅฏๅจ้ตๅฎ็ฝฒๅใๅๆด่ฏดๆๅๅ
ถไป่ฎธๅฏๆกไปถไธๅไธๅๅฉ็จ๏ผไฝ่ฅ่ฎฐๅฝๅซไธชไบบๆฐๆฎ๏ผ
่ดญไนฐๆนไป้กป้ๅฏน่ชๅทฑ็ๅค็็ฎ็ๅฎกๆฅ้็งไนๅกไธๅๆณไพๆฎใ่ฏฅ Actor ๆ้ค่ช็ถไบบ่ง่ฒใ่็ณปไบบๅ่ก้ๅฐๅ่ก๏ผ
ไธไธ่พๅบ KYCใ้่ดญใๅถ่ฃๆ่ตๆ ผ่ฃๅณใ
่ฟไบๅทฅๅ
ทไธๆฏๆถ่ดน่
ๆฅๅ๏ผไธๅพไฝไธบไฟก่ดทใไฟ้ฉใๅฐฑไธใไฝๆฟๆๅ
ถไป่ตๆ ผๅณๅฎ็ๅฏไธไพๆฎใ
ไฝฟ็จ่
ๅบๆ ธๅฏนๅๅงๆฟๅบ่ฎฐๅฝ๏ผๅนถ้ตๅฎๆฏไธชๆฐๆฎๆบ็้็จๆกๆฌพๅ้ๅถใ
| Tool | What it returns | Typical workflow |
|---|
civicdataforge-evidence-gateway | One minimized, rights-labeled packet across U.S., India, global screening, EPA, or China-facing intake tasks, with monitoring and optional transaction state | Route one identifier to the correct evidence workflow without losing provenance or uncertainty |
str-permit-registry | Self-service address evidence decisions plus official STR permit/license records, dates, source links, and normalized jurisdiction fields across 32 supported US jurisdictions | Property verification, portfolio research, registry monitoring, and municipal research |
fl-dbpr-vacation-rentals | Florida DBPR lodging-license records across seven official district files | State-license validation and property diligence |
property-violations | Normalized code and building-violation records from supported municipal sources | Property compliance research and monitoring |
leie-exclusion-screening | HHS-OIG LEIE records filtered by name, NPI, state, specialty, or exclusion type | Healthcare compliance and credentialing support |
restaurant-inspection-scores | Official restaurant inspection and violation records across seven supported jurisdictions | Facility safety research and monitoring |
multistate-childcare-licensing | Supported state childcare licensing, inspection, and deficiency fields | Multi-state facility research |
texas-childcare-licensing | Licensed childcare operations with inspection and deficiency fields where the state publishes them | Facility research and compliance support |
epa-echo-facility-compliance | Bounded EPA ECHO facility identity, published compliance status, inspections, enforcement summaries, and evidence receipts | Facility research with environmental-safety verdict fixed to UNKNOWN |
norway-company-evidence | Exact nine-digit organisation-number or bounded company-name evidence from Brรธnnรธysundregistrene, with NLOD attribution, explicit match states, and receipt hashes | Norwegian entity verification, supplier onboarding evidence, and procurement research without an eligibility verdict |
The official bundle is intentionally limited to the unified gateway plus nine focused tools. India company-registry, cross-border restricted-party evidence, and NYC
film-permit products remain available through their Actor pages and focused suite-specific MCP URLs in the
public catalog.
Norway source-rights and availability boundary
The Norway Actor uses the official Brรธnnรธysundregistrene Central Coordinating Register for Legal Entities and labels output under the Norwegian Licence for Open Government Data (NLOD) 2.0. NLOD permits commercial copying, modification, combination, and distribution subject to attribution, change disclosure, and its exclusions. That permission does not replace a buyer-specific privacy and legal-basis review where a record bears personal data. The Actor deliberately omits natural-person roles, direct contacts, and street address lines.
The 2026-08-23 logged-out readback returned HTTP 200 for both the public Store page and Actor API. The API identifies public Actor L9veafufAtLFNgiWP and binds both latest and norway-public-candidate to successful build mnKblLCjPc0BdqrME, version 0.1.3. The provider deployment receipt records bounded owned canary run 6xyIIolQYf3d1u0KR as SUCCEEDED with one exact-identifier MATCH for organisation number 974760673; this is deployment verification, not external customer usage. The canary run and dataset objects are not public evidence surfacesโtheir logged-out API routes returned HTTP 403โso use the public Actor/API metadata plus caller-owned run receipts for downstream verification.
Fastest proof path
The public Orlando task runs the STR Actor with a bounded input and exposes the resulting official records,
field structure, source links, and integration routes:
https://apify.com/civicdataforge/str-permit-registry/examples/check-orlando-str-permits
For a downloadable evaluation artifact, the website publishes a 100-row STR sample covering the verified
29-jurisdiction evaluation release together with a SHA-256 checksum:
https://civicdataforge.pages.dev/str-permit-sample
Use boundary
These tools support research and compliance workflows. They are not consumer reports and must not be used as
the sole basis for credit, insurance, employment, housing, or other eligibility decisions. Preserve the
official source links and review the source-specific limitations documented by each Actor.
Reliability before execution
Agents can inspect the public, receipt-bound reliability surfaces before spending compute or treating a
publisher response as usable:
The China-facing route is a Simplified-Chinese integration layer over the named U.S. and India products. It
does not claim a China-native registry or bulk access to Chinese government records.
Repository scope and license
This repository publishes discovery metadata for the hosted remote MCP endpoint and an installable stdio
gateway that dispatches the same ten tools to Apify; the data Actors still run on Apify. Gateway code,
metadata, and documentation are licensed under the included MIT License. Government-source terms
and record-level use restrictions remain source-specific and are documented on the corresponding Actor pages.
The open bridge is deliberately not the CivicDataForge core. Source acquisition adapters, reconciliation
pipelines, field-presence and drift monitors, source-rights controls, evidence-graph implementation, partner
connectors, operational ledgers, and deployment configuration are maintained separately and are not licensed
under this repository's MIT license. See SECURITY.md for the disclosure boundary and private
evaluation route.