US Public Records (permits, grants, OSHA/EPA, recalls)

io.github.owlabeePublished by GitHub account owlabeev1.0.2Updated Nov 7, 2026

US public records as JSON: building permits, Grants.gov/SAM.gov, OSHA/EPA, recalls, licenses, PACER.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Hosted MCP endpoint that returns US public records as JSON: building permits, Grants.gov/SAM.gov, OSHA/EPA, recalls, licenses and PACER.

What you can do
  • Retrieve US public records as structured JSON
  • Look up building permits, licenses and PACER court records
  • Query Grants.gov and SAM.gov federal grant and registration data
  • Pull OSHA and EPA enforcement and compliance records
  • Search product recall data
When to use it
Useful when an assistant needs to research US government records — permits, federal grants, regulatory enforcement, recalls or court filings — without building scrapers for each source.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com with OAuth authentication; an Apify API token sent as a Bearer token in the Authorization header; an Apify account with billing.
Before you install
Runs are billed per result to your Apify account, so queries can cost money. The Apify API token is a secret sent in the Authorization header. Records are fetched through a third-party platform (Apify), and results may be incomplete or out of date relative to the official sources.

Installation

In SourceWeft

  1. Open US Public Records (permits, grants, OSHA/EPA, recalls) 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.owlabee%2Fus-public-records/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": {
    "us-public-records-permits-grants-osha-ep": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=owlabee/building-permits-scraper,owlabee/accela-energov-permit-scraper,owlabee/grants-gov-api,owlabee/grant-matching,owlabee/osha-epa-inspections,owlabee/product-recall-feed,owlabee/license-verification-api,owlabee/federal-court-docket-monitor"
    }
  }
}

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

1
  1. v1.0.2LatestNov 7, 2026

Score

70% 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