Secapi

ai.secapiPublished by secapi.aiOfficial publisherv0.3.0Updated Oct 30, 2026

SEC & financial-data MCP: filings, financials, ownership, factors, fund letters, prompts.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Remote Secapi MCP server that gives an assistant access to SEC filings, financial data, ownership, factors and fund letters.

What you can do
  • Retrieve SEC filings and related company documents
  • Look up financial statements and financial data
  • Inspect ownership information and factor data
  • Access fund letters and prompt resources
When to use it
Useful when an assistant needs SEC filing research, company financials, ownership or factor data, or fund letters, without building its own data pipeline.
Requirements
A remote streamable HTTP endpoint at api.secapi.ai; no local install. Requires a secapi.ai API key (secapi_live_ or secapi_test_ prefix) created in the secapi.ai dashboard and sent in the x-api-key header on every request.
Before you install
The API key is a secret sent on every request; keep it out of logs and shared configs. The tool list is not published, so confirm which data the server reads and whether any calls consume paid quota before relying on it.

Installation

In SourceWeft

  1. Open Secapi in the dashboard and add it to a workspace.
  2. Connect x-api-key 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/ai.secapi%2Fsecapi/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.

{
  "mcpServers": {
    "secapi": {
      "type": "http",
      "url": "https://api.secapi.ai/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

60% 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 listedRequired15 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

    Declare a license in the repository or the registry entry.