AICD API

com.aicdapiv1.0.0Updated Sep 29, 2026

Search source-linked Dallas-Fort Worth local-government records for AI agents.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & AnalyticsKnowledge & Memory

Overview

AI-generated overview

Search and read source-linked Dallas-Fort Worth local-government agenda records, with coverage checks and missing-data reports.

What it does
AICD API is a remote MCP server exposing civic records tools: search_agenda finds ranked agenda records, get_agenda_item reads one record by id, get_coverage checks supported source health, report_missing_data reports a missing public record, and get_data_report reads the status of such a report. Results stay linked to the public source they came from, and source health is reported per source. Coverage starts with Dallas-Fort Worth, with broader Texas coverage planned.
When to use it
Use it when an assistant needs to look up local-government agendas and meeting items in the Dallas-Fort Worth area, or to check which sources are currently covered and healthy. It is a discovery and lookup tool rather than a full archive, so an empty result does not prove there was no government activity.
Requirements
A remote Streamable HTTP endpoint at no local package or runtime. An Authorization header is required with the full value Bearer , where keys start with aicd_ and the account needs current paid access for the civic tools. Keys are created and revoked through the provider's API-keys page, and network access to the endpoint is needed.
Before you install
The Authorization header carries a secret API key; treat it as a credential and avoid exposing it in logs or shared configuration. The account requires current paid access, so using the civic tools involves a paid subscription. report_missing_data submits information to the provider, and queries are sent to a third-party service.

Installation

In SourceWeft

  1. Open AICD API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "records": {
      "type": "http",
      "url": "https://aicdapi.com/api/v1/mcp"
    }
  }
}

README

AICD API — MCP discovery record

This repository holds the MCP discovery record for AICD API, a source-linked API and MCP server for Dallas-Fort Worth local-government records.

  • server.json — the record for the remote MCP server, following the official MCP Registry server.json schema (revision 2025-12-11). Registry name: com.aicdapi/records.

The record is served by AICD API at https://aicdapi.com/server.json, with a byte-identical, non-normative convenience alias at https://aicdapi.com/.well-known/mcp.json; the alias path is not part of any adopted MCP discovery standard. It is published in the Official MCP Registry — entry: https://registry.modelcontextprotocol.io/v0.1/servers/com.aicdapi%2Frecords/versions/1.0.0

Connection

Tools

ToolPurpose
search_agendaFind ranked civic agenda records
get_agenda_itemRead one agenda record by id
get_coverageCheck supported source health
report_missing_dataReport a missing public record
get_data_reportRead a missing-data report status

Public example (no key)

bash
curl https://aicdapi.com/api/v1/public/agenda-hits

Coverage

Dallas-Fort Worth is the first coverage area; broader Texas coverage is planned. Every result stays linked to the public source it came from, and source health is reported per source. An empty result does not prove there was no government activity.

Sources

Contact

[email protected]

Source: README.md at commit 24ab207

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestSep 29, 2026