Vigia Edgar

io.github.filingtapePublished by GitHub account filingtapev1.0.0Updated Oct 28, 2026

Always-on SEC EDGAR watcher: ~45s alerts when an insider files a Form 4 or a firm drops an 8-K.

The publisher's own server: edgar.tools SEC Intelligence

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that watches SEC EDGAR and alerts an assistant about new insider Form 4 and 8-K filings for a ticker watchlist.

What you can do
  • Register US tickers to monitor, resolving each to its SEC CIK and reporting any that could not be found
  • Retrieve new Form 4 and 8-K filings detected for the watched tickers since the previous call, with a per-user cursor so alerts are not repeated
  • Each alert carries ticker, company, form type, category, accession number, acceptance and detection times, latency and a direct filing link
When to use it
Useful when you want an assistant to surface insider-trading and material-event filings for specific US-listed companies without polling EDGAR yourself, for example during monitoring of a small watchlist of tickers.
Requirements
A remote endpoint reached over streamable HTTP; OAuth authentication is required. The free tier covers one ticker; more tickers need a paid Pro plan, with billing handled by the hosting platform. The README also lists engine-side settings (WORKER_URL, VIGIA_KEY, WATCH_NAMESPACE) for self-hosting the server layer.
Before you install
Alerts are near-real-time but not instant: about 45 seconds median and under roughly two minutes worst case after the SEC accepts a filing. The free tier is limited to one ticker and further tickers require a paid subscription. The README notes that per-user isolation depends on setting a WATCH_NAMESPACE key, which defaults to a shared value, and that the engine records aggregate usage counters per namespace.

Installation

In SourceWeft

  1. Open Vigia Edgar 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/io.github.filingtape%2Fvigia-edgar/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": {
    "vigia-edgar": {
      "type": "http",
      "url": "https://vigia-edgar.mcpize.run/mcp"
    }
  }
}

README

vigía EDGAR — Always-on SEC EDGAR watcher (Form 4 / 8-K alerts)

Public copy & quickstart live in mcp/README.md. This root README is the developer/architecture doc for the two-layer system (engine + skin).

An always-on engine that watches US SEC EDGAR for you and queues an alert about ~45 seconds (median, under ~2 min worst case — fast polling, not instant/real-time) after the SEC accepts an insider Form 4 or a company's 8-K. Set a ticker watchlist (AAPL, TSLA, NVDA…) and your AI agent gets insider-trading and material-event alerts on Claude, Cursor, or any MCP client — no setup on your side. Free: 1 ticker. Pro ($29): unlimited tickers.

Latency, stated honestly: about 45 seconds median from when the SEC accepts a filing, under ~2 minutes worst case (measured on the EDGAR getcurrent feed). The engine polls fast and never sleeps.

Why this needs an MCP server (the moat)

An LLM agent on its own cannot watch EDGAR 24/7. The value here is infrastructure that never sleeps: a cron-driven engine continuously polls the SEC, dedupes every filing, and keeps a per-user cursor so your agent only ever sees what's new. The agent just asks; the engine has already been watching.

Tools

watch_insider(tickers: string[])

Register US tickers to monitor (Form 4 + 8-K). Resolves each ticker to its SEC CIK and starts watching. Returns the resolved list and any tickers it couldn't find.

get_alerts()

Return new filings detected for your watched tickers since your last call (a per-user cursor advances automatically, so you never get duplicates). Each alert includes: ticker, company, formType, category (insider | material_event), accession, acceptanceTime, detectedTime, latencySeconds, and a direct filingUrl.

Architecture

Two layers:

  • Engine (Cloudflare Worker + D1): a cron trigger polls EDGAR's getcurrent atom feed every minute (two polls ~30s apart per tick → ~30s effective cadence). It dedupes accession numbers, matches filings to watched companies by CIK (robust to name changes), and stores matches in D1. State: seen (dedupe), watches (per-user CIKs), alerts, cursors (per-user delivery), ticker_map (refreshed daily from company_tickers.json).
  • Skin (this MCP server, hosted on MCPize): exposes the two tools and reads/writes the engine over an authenticated HTTP API (/watch, /alerts). MCPize handles auth and billing.

Per-user isolation: set WATCH_NAMESPACE (your own key) in the MCP server config to keep your watchlist and cursor private. Defaults to default.

SEC compliance

All requests to the SEC use the required identifiable User-Agent and stay well under the 10 req/s limit (the EDGAR feed is polled once per cron cycle).

Configuration (env / secrets)

  • WORKER_URL — base URL of the Cloudflare engine.
  • VIGIA_KEY — shared secret the skin uses to call the engine.
  • WATCH_NAMESPACE — per-user watchlist namespace (optional; defaults to default).

Funnel instrumentation

The engine counts four product numbers in the D1 funnel table (one aggregate row per namespace, idempotent upserts — negligible cost):

  1. installs — namespace connected the MCP (first /watch)
  2. activations — actually used it (resolved a ticker, or pulled /alerts)
  3. wall_hits — bounced off the Free 1-ticker cap (hunger for Pro)
  4. conversions — paid → Pro active (Stripe-verified)

Read them (admin, needs X-Vigia-Key):

GET /admin/funnel            -> { funnel: { installs, activations, wall_hits, total_wall_hits, conversions } }GET /admin/funnel?detail=1   -> also returns per-namespace rows

Or straight from D1:

SELECT COUNT(installed_utc)  installs,       COUNT(activated_utc)  activations,       COUNT(first_wall_utc) wall_hits,       COUNT(converted_utc)  conversionsFROM funnel;

Repo layout

worker/   Cloudflare Worker engine (cron + D1)  — npx wrangler deploymcp/      MCPize MCP server (the 2 tools)        — npx mcpize deploy

Source: README.md at commit 472400a

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.0LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Edgar integrations

edgar.tools SEC Intelligence

tools.edgarOfficial publisher

Remote MCP server giving assistants 23 tools and 5 recipes for SEC filings, financials, insider trades, 13F holdings and funds.

Streamable HTTPWeb executableAuth
FinanceCredential requiredOct 24, 2026

SEC EDGAR Filings

Published by GitHub account SudiptoHaldar

Read-only SEC EDGAR filing metadata by stock ticker: latest filing, calendar-year filing history, and form-type codes, with official sec.gov links.

STDIODesktop only
Finance3 toolsNov 5, 2026

SEC EDGAR — Recent Company Filing Index by CIK

Published by GitHub account kriton-dev

SEC EDGAR — Recent Company Filing Index by CIK's hosted MCP server; credential required; Streamable HTTP.

Streamable HTTPWeb executableAuth
FinanceCredential requiredNov 3, 2026

Sec Edgar Mcp

Published by GitHub account mrfentmen

Local MCP server that gives an assistant access to SEC EDGAR filings and XBRL financial concepts, including company profiles by CIK and full-text search.

STDIODesktop only
FinanceNot validated · the server did not startOct 30, 2026

SEC EDGAR Insider Trades & Financials

Published by GitHub account monriah-studio

Remote MCP server for U.S. SEC EDGAR data, letting an assistant look up insider trades, filings, XBRL financials and full-text filing search.

Streamable HTTPWeb executable
Web Search & Scraping7 toolsOct 24, 2026