Open Data Actors Mcp
io.github.Mamoo85Published by GitHub account Mamoo85v0.1.0Updated Oct 24, 2026
24 public-data Apify actors (sanctions, SEC Form D, WARN, FMCSA, SEO, jobs) as MCP tools.
Overview
Exposes 24 public-data Apify actors — sanctions screening, SEC Form D leads, layoff notices, job boards, SEO audits and more — as MCP tools.
- What you can do
- A thin MCP server that forwards tool calls to the Apify API using your own token, exposing 24 fixed public-data actors as typed tools. Each tool accepts the actor's own input fields plus max_results (default 25, cap 200), runs synchronously with a 240-second timeout, and returns a count and items. Covered sources include sanctions lists, SEC Form D funding leads, WARN layoff notices, FMCSA carriers, job boards, building permits, domain and SEO audits, contact extraction and ad libraries. Secret or stateful fields such as proxy settings, API keys and webhook URLs are deliberately not exposed.
- When to use it
- Use it when you want an assistant to pull specific public-record or web datasets — compliance screening, funding or hiring leads, local business and permit data, SEO and domain checks — without wiring each Apify actor yourself. It suits a small fixed set of known actors rather than arbitrary Apify Store actors. Skip it if you need no paid data collection or prefer a general-purpose Apify server.
- Requirements
- Node 18+ and an Apify API token supplied as the APIFY_TOKEN environment variable (or an Authorization Bearer header / token query parameter for the hosted endpoint). The package is installed from GitHub via npx, or used through the hosted streamable-HTTP endpoint; network access to the Apify API is required. No account beyond Apify is declared.
Installation
In SourceWeft
- Open Open Data Actors Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
open-data-actors-mcp: MCP server for public-data Apify actors (sanctions, SEC Form D, WARN, FMCSA)
A thin Model Context Protocol server that exposes 29 public-data Apify actors as tools: sanctions screening, SEC Form D funding leads, WARN layoff notices, FMCSA new carriers, technical SEO audits, tech-stack detection, job boards, building permits, Google Maps places, TikTok profiles, YouTube comments, Amazon best sellers, SAM.gov federal bids, and more.
Disclosure: I am the author and maintainer of these actors. They run on Apify and are pay-per-result; the Apify free plan credit covers a trial. This server only forwards your tool call to the Apify API with your token. It has no backend of its own, stores nothing, and sends nothing anywhere else. If you want Apify's general-purpose MCP server (every Store actor), use mcp.apify.com; this one is a small, fixed, typed subset.
Hosted (no install)
Stateless streamable-HTTP endpoint: https://open-data-actors-mcp.vercel.app/mcp
Bring your own Apify token on every request (Authorization: Bearer <token>, or ?token=). Nothing is stored or logged by us; runs bill to your own Apify account. Rate limit: 30 requests/minute per token.
Verify with a real client: APIFY_TOKEN=... node test/http.test.mjs.
Install
You need Node 18+ and an Apify API token (https://console.apify.com/settings/integrations?fpr=rnmakg).
(Not on npm yet; the github: form installs straight from this repo.) Works in Claude Desktop, Claude Code (claude mcp add open-data-actors -e APIFY_TOKEN=... -- npx -y github:Mamoo85/open-data-actors-mcp), Cursor, and any stdio MCP client.
Tools
Each tool takes the actor's own input fields plus max_results (default 25, cap 200). Calls run synchronously (run-sync-get-dataset-items, 240 s timeout) and return {count, items}. Fields that are secrets or state (proxy settings, API keys, webhook URLs, incremental-state names) are intentionally not exposed.
Cost
Each call starts an Apify run and you pay Apify the actor's pay-per-result price for the rows it produces. Lower max_results to cap spend. See each Store page for current pricing.
Tests
npm test starts the server and drives it with the real MCP SDK client over stdio: lists tools, checks error handling, and (when APIFY_TOKEN is set) makes one live tools/call. Verified 2026-10-14: 29 tools listed, live sanctions_screening call returned data.
Development
python gen.py regenerates src/tools.json from the actors' published input schemas.
MIT licensed.
Some links are affiliate links.
Source: README.md at commit 408935a
Tools
0Version history
1- v0.1.0LatestOct 14, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts