# SEC Filing Evidence MCP Server (`nexgenwatch/sec-filing-evidence-mcp`) Actor

Locate the SEC filing behind a claim. Every answer carries the accession number, the filing date and a direct SEC URL, so an agent's claim about a public company is checkable at source.

- **URL**: https://apify.com/nexgenwatch/sec-filing-evidence-mcp.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Agents, Business
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 tool calls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## SEC Filing Evidence MCP Server

Locate the SEC filing behind a claim. Every answer carries the **accession number, the filing
date and a direct SEC URL**, so anything an agent says about a public company can be checked at
source by a human afterwards.

This is an **evidence locator, not a summariser**. It does not paraphrase filings and it does
not give financial advice — it tells you exactly which document to open.

### Tools

| tool | what it answers |
|---|---|
| `lookup_company` | Turn a ticker, name or CIK into SEC identifiers. Start here. |
| `list_filings` | Recent filings for a company, filterable by form and date, each with a document URL |
| `get_filing` | One filing, located precisely, by accession number |
| `search_filings` | Full-text search across filings; returns documents containing your phrase |

### Sources — public, logged-out, no key

| what | endpoint |
|---|---|
| company index (10,432 companies) | `www.sec.gov/files/company_tickers.json` |
| filing history | `data.sec.gov/submissions/CIK##########.json` |
| full-text search | `efts.sec.gov/LATEST/search-index` |

### SEC fair access

SEC asks automated clients for a declarative User-Agent with a contact address and a ceiling of
**10 requests per second**. This server sends the User-Agent and paces **every** outbound call
through one shared token bucket at **8 requests per second**.

That limiter is load-bearing, not decorative: measured on the build runtime, five *sequential*
unpaced calls ran at about **12 requests a second** — already over the cap with no concurrency
at all. A standby server answering several agents at once would be far over it.

### Honest limits

- The submissions feed carries the **most recent 1,000 filings** inline. Responses report
  `older_files_available`, so an empty result for an old date range reads as a **window limit,
  not an absence**.
- `get_filing` says when an accession is outside that window rather than implying it does not
  exist.
- Full-text search covers **2001 onward** and indexes filing documents, not every exhibit format.

### Pricing

| Event | Price |
|---|---|
| Server start (`apify-actor-start`) | $0.05, charged once per server run by the platform |
| Tool call (`mcp-tool-call`) | **$0.05 flat per completed tool call** |

No other events. **Errors and notices are not charged** — a bad CIK, a SEC read failure, or an
accession outside the window returns without billing. A sourced answer, including a well-evidenced
"no filings match", **is** charged.

If a tool call cannot be billed correctly, **the call fails** rather than serving free.

# Actor input Schema

## `note` (type: `string`):

This Actor runs as an MCP server in Standby mode. Connect an MCP client to the server URL with path /mcp; there is no batch input to fill in.

## Actor input object example

```json
{
  "note": "standby"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "note": "standby"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/sec-filing-evidence-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "note": "standby" }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/sec-filing-evidence-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "note": "standby"
}' |
apify call nexgenwatch/sec-filing-evidence-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/sec-filing-evidence-mcp"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Z72UAX40hwztzufxd/builds/3WfAQaeKLBLwSfZZD/openapi.json