Local Government Decision Lookup & Fact Check

io.github.catalyst-labs-devPublished by GitHub account catalyst-labs-devv1.0.1Updated Oct 26, 2026

Verify Iowa council/county votes from official minutes after a transcript search. Verdict, tally.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote Apify-hosted MCP server that lets an assistant verify Iowa city council and county votes against official minutes after a transcript search.

What you can do
  • Search transcripts to locate Iowa council or county meeting discussions.
  • Verify a recorded vote against the official minutes.
  • Return a verdict and a tally for the checked decision.
When to use it
Useful when checking whether a claim about an Iowa local government vote is accurate, or when a meeting transcript mentions a decision that should be confirmed against official minutes.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. An Apify API token sent as an Authorization bearer header, or OAuth sign-in with Apify if the client supports it. Network access required.
Before you install
Requires an Apify account credential (Authorization bearer token or OAuth sign-in); the token grants access to your Apify account. Coverage appears limited to Iowa local government records, so results may be incomplete elsewhere.

Installation

In SourceWeft

  1. Open Local Government Decision Lookup & Fact Check in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.catalyst-labs-dev%2Flocal-government-decision-lookup/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "local-government-decision-lookup-fact-ch": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=catalyst-labs/local-government-decision-lookup"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 26, 2026
  2. v1.0.0Oct 25, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Check integrations