io.github.owlabee/us-public-records
US Public Records (permits, grants, OSHA/EPA, recalls)
Is the US Public Records (permits, grants, OSHA/EPA, recalls) MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Public records as JSON: US permits, grants, OSHA/EPA, recalls, licenses, PACER; EU/UK/AU tenders.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Missing or invalid access token. Pass an Apify API token in the - Endpoint
- 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/pacer-docket-monitor,owlabee/tenders-scraper (streamable-http)
- Host
- mcp.apify.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth 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/pacer-docket-monitor,owlabee/tenders-scraper registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server console-backend.apify.com, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes full_api_access.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/owlabee/owlabee
- Website
- https://owlabee.com/
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Other registry entries on mcp.apify.com, the ones next to this name; all of them.
- YouTube Transcripts & Creator Data io.github.omarkhandji-commits/youtube-data · needs auth
- Google Ads Transparency Center Scraper (orbots) - Apify Actor io.github.orbotshq/google-ads-transparency-scraper · needs auth
- Google Trends Scraper (orbots) - Apify Actor io.github.orbotshq/google-trends-scraper · needs auth
- Documents to Data (PDF to Markdown, document to JSON) io.github.owlabee/documents-to-data · needs auth
- Web & Business Monitoring (DMARC, sitemaps, Shopify, jobs) io.github.owlabee/web-monitoring · needs auth
- Website SEO Audit, Broken Links & Change Monitor (Apify, paid per audit) io.github.ozzie-bagadirov/seo-audit-change-monitor · needs auth
- Amazon Brasil Sellers com CNPJ — Leads B2B e Receita Federal io.github.paulovitorti/amazon-brasil-vendedores-cnpj · needs auth
- Hotéis e Pousadas no Booking Brasil — Leads com E-mail e CNPJ io.github.paulovitorti/booking-brasil-hoteis · needs auth
Servers that mention records.
- hood. — .hood name service ag.hood/name-service · alive
- GroundTruth - Environmental Records ai.agentlookups/groundtruth · alive
- Plumbline - Contractor License Checks ai.agentlookups/plumbline · alive
- Connie ai.connie/connie · needs auth
- Crub ai.crub/mcp · needs auth
- ENYAL by Greenland AI ai.enyal/enyal · alive
- Klaaro ai.klaaro/klaaro · needs auth
- IntoDNS.ai DNS & Email Security Scanner ai.intodns/scanner · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.