SecBot

trade.secbotPublished by secbot.tradeOfficial publisherv1.0.1Updated Oct 30, 2026

US market data from public filings: SEC, insiders, 13F, Congress trades, lobbying, FDA, contracts.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint giving assistants access to US market data drawn from public filings such as SEC, insider, 13F, congressional trade, lobbying, FDA and…

What you can do
  • Retrieve US market data sourced from public filings.
  • Look up SEC filings, insider transactions and 13F holdings.
  • Check congressional trades and lobbying disclosures.
  • Consult FDA and government contract records.
  • No tool list is published, so exact operations are not documented.
When to use it
Useful when an assistant needs to research US equities or public-record signals — filings, insider activity, institutional holdings, political trades or regulatory and contract data — without building its own data pipeline.
Requirements
A remote streamable HTTP endpoint at secbot.trade; OAuth authentication is required. No environment variables, headers or local packages are declared.
Before you install
Access requires OAuth sign-in to a third-party service, so account data is shared with the provider. The tool list and any usage limits, pricing or data licensing terms are not documented here; verify them before relying on the data for decisions.

Installation

In SourceWeft

  1. Open SecBot 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/trade.secbot%2Fsecbot/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": {
    "secbot": {
      "type": "http",
      "url": "https://secbot.trade/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

2
  1. v1.0.1LatestOct 30, 2026
  2. v1.0.0Oct 26, 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.