FilingSpy

com.filingspyPublished by filingspy.comOfficial publisherv1.0.0Updated Oct 27, 2026

SEC filings as tools: 13F superinvestor portfolios, Form 4 insider trades, XBRL and filing text

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant access to SEC filings: 13F superinvestor portfolios, Form 4 insider trades, XBRL data and filing text.

What you can do
  • Retrieve 13F holdings to see superinvestor portfolios
  • Look up Form 4 insider trades
  • Query XBRL financial data from filings
  • Read filing text for detail and context
When to use it
Useful when you want an assistant to research US public companies through official SEC disclosures — tracking what large investors hold, following insider buying and selling, or pulling structured financial figures and filing text without visiting EDGAR manually.
Requirements
A remote MCP endpoint at filingspy.com over streamable HTTP. OAuth authentication is required, so an account with the provider is needed. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth sign-in with the provider, so review what account data and scopes are shared. The server is hosted by a third party, and any queries you make are sent to it. Filing data is informational and should not be treated as investment advice.

Installation

In SourceWeft

  1. Open FilingSpy in the dashboard and add it to a workspace.
  2. Connect the required 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/com.filingspy%2Fmcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "filingspy": {
      "type": "http",
      "url": "https://filingspy.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 17, 2026

Score

67% 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 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.