Gov Financial Intel

SEC EDGAR filings, BLS employment stats, and USDA crop prices. 3 tools for federal financial intelligence.

Security Scan

The skill's instructions are coherent with its stated function but they rely on connecting your agent to a third-party MCP endpoint (an Apify actor) and instruct modifying local MCP config without describing what data is transmitted or retained — this creates privacy/exfiltration risk that isn't justified or documented.

Purpose & Capability

Name/description (SEC, BLS, USDA) match the provided tools and parameters. Requiring the mcporter binary and an MCP server is a plausible implementation choice for exposing these tools. However, calling a third-party proxy (https://federal-financial-intel-mcp.apify.actor/mcp) to access public US government APIs is not strictly necessary and is an architectural decision that should be justified; it's not obviously required by the stated purpose.

Instruction Scope

SKILL.md instructs the agent (or user) to add a remote MCP server and optionally write it into ~/.openclaw/mcp.json. It does not document what runtime context, prompts, or user data will be forwarded to that remote server, nor retention/logging policies. The transport 'streamable-http' implies an active network connection where the remote endpoint can receive queries and stream results, which could be used to exfiltrate sensitive information if the agent forwards it. The instructions are otherwise limited to invoking the declared tools and parameters (searches and query fields).

Install Mechanism

No install spec or code is shipped (instruction-only), so nothing is written by the skill itself. That lowers direct install risk. The runtime dependency on the external Apify-hosted MCP is the main operational risk: your agent will communicate with a third-party service (not the original government APIs). The skill requires the mcporter binary to establish that connection; ensure mcporter is from a trusted source.

Credentials

The registry declares no required environment variables or config paths, but the SKILL.md explicitly suggests modifying ~/.openclaw/mcp.json to add the remote server. This is an inconsistency: the skill will cause the agent/user to add a remote server entry to a local config file, which grants the remote endpoint a channel into the agent's MCP system. No credentials are requested, which is good, but there is no documentation about what gets transmitted across that channel (agent context, user prompts, files), so the lack of declared env/config requirements understates the practical access being requested.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request permanent/enforced inclusion. The skill does instruct adding a server entry to ~/.openclaw/mcp.json, which persists that configuration locally; that is normal for registering an MCP. This persistent config plus a remote streamable connection increases the blast radius compared with a purely local/in-process integration, but the privilege level requested is not unusually elevated by metadata alone.

What to consider before installing

This skill appears to be a thin wrapper that routes queries to a third-party MCP hosted on Apify rather than calling government APIs directly. Before installing or enabling it: 1) Inspect the referenced GitHub repo (https://github.com/martc03/gov-mcp-servers) and confirm the Apify actor owner and code are trustworthy. 2) Understand what data your agent will send to the MCP: prompts, system context, attached files, or secrets — avoid sending any sensitive data through the skill. 3) Prefer self-hosting the MCP or calling the official US government APIs directly if you want to minimize third-party exposure. 4) Verify TLS and the actor's privacy/retention policy (logs, caching). 5) If you must use it, add the MCP entry manually (don't run arbitrary scripts) and run mcporter in a restricted environment (sandbox/container) until you confirm behavior. Additional information that would raise confidence: the GitHub repo contents and owner identity, a privacy/data-flow statement showing exactly what the MCP receives/transmits, and assurances about logging/retention policies for the Apify actor.

Federal Financial Intel

Real-time access to SEC filings, BLS employment statistics, and USDA commodity prices.

Setup

mcporter add gov-finance --url https://federal-financial-intel-mcp.apify.actor/mcp --transport streamable-http

Or add to your OpenClaw MCP config (~/.openclaw/mcp.json):

{
  "servers": {
    "gov-finance": {
      "url": "https://federal-financial-intel-mcp.apify.actor/mcp",
      "transport": "streamable-http"
    }
  }
}

Available Tools

finance_search_sec_filings

Search SEC EDGAR for company filings (10-K, 10-Q, 8-K, etc).

Search SEC filings for Apple
Show 10-K annual reports for Tesla

Parameters: searchText, formTypes (array, e.g. ["10-K","10-Q","8-K"]), dateFrom, dateTo, limit

finance_get_employment_stats

Get BLS employment statistics: unemployment rate, nonfarm payrolls, CPI, hourly earnings.

Show current unemployment rate
Get BLS employment data for 2024-2025

Parameters: seriesIds (array, e.g. ["LNS14000000","CES0000000001"]), startYear, endYear

finance_get_crop_prices

Get USDA crop and commodity prices (corn, soybeans, wheat, etc).

Show corn prices for 2024
Get USDA soybean prices by state

Parameters: commodities (array, e.g. ["CORN","SOYBEANS","WHEAT"]), states (array), years (array), statisticCategory, limit

Data Sources

• SEC EDGAR — Securities and Exchange Commission (company filings)
• BLS — Bureau of Labor Statistics (employment, CPI)
• USDA NASS — National Agricultural Statistics Service (crop prices)

Use Cases

• Company financial research
• Economic indicator tracking
• Agricultural market analysis
• Investment due diligence

All data from free US government APIs. Zero cost. No API keys required.