Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Mit Google anmelden, um Bewertungen zu schreiben.Prototyp · alle 30 Min. aktualisiert
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt Anmelden

Sec Beneficial Ownership

von pipeworx-ioVersion 0.2.1i★ 0iComputer oder CloudOffizielle Website ↗
Name in der Registryio.github.pipeworx-io/sec-beneficial-ownership

So installierst du es

Was es kann

SEC Schedule 13D / 13G — structured beneficial-ownership filings.

Originaltext des Herstellers

  • Verbindung Computer oder Cloud
  • Konto oder Schlüssel Kein Schlüssel nötig
  • Kategorie Sonstiges

Warum es hier steht

Listen sind nach einem Nutzungswert (von 100) aus diesen Teilen sortiert

Beliebtheit0/80GitHub-Sterne oder wöchentliche Downloads: der größere Wert zählt 60, der kleinere 20
Aktualität12/12Volle Punkte für Release oder Codeänderung in 30 Tagen
Antwortet noch8/8Der Cloud-Endpoint antwortete bei der letzten Prüfung
Nutzungswert20/100

Qualität: 5/5 Basisprüfungen bestanden (angezeigt, nicht zur Sortierung) · Schwung: Noch keine Daten (Nur im Tab Im Trend verwendet)

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Mit einem Satz von deiner KI installieren lassen

Installiere bitte Sec Beneficial Ownership. Folge https://mcp.popnx.com/i/pipeworx-io-sec-beneficial-ownership.md, zeig mir die Befehle und warte auf mein OK, bevor du sie ausführst.

Füge ihn in eine KI ein, die auf deinem Rechner arbeitet (z. B. Claude Code oder Cursor). Sie liest unsere Schritte, zeigt dir die Befehle und wartet auf dein OK. Kein Schlüssel, keine Anmeldung. · Vollständigen Text ansehen

5/5 Prüfungen bestanden · Was du fragst, läuft über den Server des Anbieters (gateway.pipeworx.io) · ✓ Befehle geprüft am 14. Nov. 2026

Zuerst: Welche KI nutzt du?

Wähle deine App, dann erscheinen die Schritte unten.

Klappt mit Claude · etwa 2 Min.

Kein Schlüssel, nichts zu installieren · Einmal auf claude.ai oder in der Desktop-App einrichten, dann im Chat nutzen · kostenlose Konten können 1 hinzufügen · bei Team/Enterprise fügt ein Owner ihn hinzu

  1. Öffne die Connectors-Seite von Claude

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Klicke „Add“ → „Custom“ → „Web“ und fülle diese 2 Felder aus

    Kopiere jeden Wert in das gleichnamige Feld in Claude und klicke Continue

    Name · NameSec Beneficial Ownership
    Remote MCP server URL · Adressehttps://gateway.pipeworx.io/sec-beneficial-ownership/mcp

    Klicke auf der von Claude erkannten Anmelde-Seite auf Continue · wähle bei Authentication, was der Anbieter angibt (Sign in now, Sign in when needed oder No sign in), dann Add

  3. Im Chat einschalten

    +ConnectorsSec Beneficial Ownership

  4. Ausprobieren

    Nutze Sec Beneficial Ownership und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Claude sagt, dass es Sec Beneficial Ownership nutzt, oder ein Werkzeug von Sec Beneficial Ownership in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit ChatGPT je nach Tarif

Volles MCP: ChatGPT Business, Enterprise oder Edu im Web · Pro: verbindet mit Lese-/Abrufrechten, Werkzeuge, die Daten ändern, gehen evtl. nicht · Plus: in der Doku nicht bestätigt; siehst du auf der Plugins-Seite eine Option für eigene MCP-Server, kannst du es versuchen · nur Web

  1. In ChatGPT im Web die Seite zum Hinzufügen von MCP öffnen

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Name und Adresse eintragen

    Namen eingeben, Adresse unter Connection einfügen, Risikohinweis abhaken und Create as a plugin klicken

    Name · NameSec Beneficial Ownership
    Connection · Adressehttps://gateway.pipeworx.io/sec-beneficial-ownership/mcp
  3. Sec Beneficial Ownership im Chat auswählen

    Neuen Chat öffnen und vor dem Tippen Sec Beneficial Ownership aus deinen Plugins wählen

  4. Ausprobieren

    Nutze Sec Beneficial Ownership und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn ChatGPT sagt, dass es Sec Beneficial Ownership nutzt, oder ein Werkzeug von Sec Beneficial Ownership in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von OpenAI abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit Claude Code · etwa 2 Min.

Kein Schlüssel, nichts zu installieren

  1. Terminal öffnen

    Mac: Command+Leertaste drücken und Terminal tippen · Windows: PowerShell öffnen

  2. Diesen Befehl einfügen und Enter drücken

    claude mcp add --transport http --scope user sec-beneficial-ownership https://gateway.pipeworx.io/sec-beneficial-ownership/mcp
  3. /mcp in Claude Code eingeben

    Sec Beneficial Ownership sollte in der Liste als verbunden erscheinen

  4. Ausprobieren

    Nutze Sec Beneficial Ownership und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Claude Code sagt, dass es Sec Beneficial Ownership nutzt, oder ein Werkzeug von Sec Beneficial Ownership in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit Cursor · etwa 2 Min.

Kein Schlüssel, nichts zu installieren

  1. Mit diesem Button Cursor öffnen

    In Cursor öffnen

    Cursor fragt nach einer Bestätigung; klicke Install

  2. KI-Chat in Cursor im Agent-Modus öffnen

  3. Ausprobieren

    Nutze Sec Beneficial Ownership und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Cursor sagt, dass es Sec Beneficial Ownership nutzt, oder ein Werkzeug von Sec Beneficial Ownership in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von Cursor abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit VS Code · etwa 2 Min.

Kein Schlüssel, nichts zu installieren

  1. Mit diesem Button VS Code öffnen

    In VS Code öffnen

    VS Code fragt nach einer Bestätigung; klicke Install

  2. KI-Chat in VS Code im Agent-Modus öffnen

  3. Ausprobieren

    Nutze Sec Beneficial Ownership und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn VS Code sagt, dass es Sec Beneficial Ownership nutzt, oder ein Werkzeug von Sec Beneficial Ownership in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von VS Code abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Andere Apps mit MCP, etwa Windsurf, Zed oder Gemini CLI, fügen Server unterschiedlich hinzu. Sieh in der App-Liste nach

Alle Apps mit MCP ansehen →

Adresse für Apps, die über das Web verbinden

Adressehttps://gateway.pipeworx.io/sec-beneficial-ownership/mcp

JSON-Einstellungen stehen unten unter „Für Entwickler“

Hängst du fest? Frag Leute, die Sec Beneficial Ownership nutzen💬 Diskussion →
Für Entwickler: Terminal-Befehle und JSON-Einstellungen

Über das Web

Claude Code

claude mcp add --transport http --scope user sec-beneficial-ownership https://gateway.pipeworx.io/sec-beneficial-ownership/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "sec-beneficial-ownership": {
      "url": "https://gateway.pipeworx.io/sec-beneficial-ownership/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "sec-beneficial-ownership": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/sec-beneficial-ownership/mcp"
    }
  }
}

Auf deinem Computer installiert

Claude Code

claude mcp add --scope user sec-beneficial-ownership -- npx -y @pipeworx/mcp-sec-beneficial-ownership

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "sec-beneficial-ownership": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sec-beneficial-ownership"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "sec-beneficial-ownership": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sec-beneficial-ownership"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "sec-beneficial-ownership": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sec-beneficial-ownership"
      ]
    }
  }
}

Werte, die du selbst einträgst

  • PIPEWORX_API_KEY geheim env
    Optionaler Pipeworx-API-Schlüssel. Ohne ihn sind Aufrufe anonym und täglich begrenzt; ein kostenloser Schlüssel erhöht das Limit.
    Englisches Original anzeigenOptional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Beschreibungen automatisch übersetzt; Variablennamen bleiben wie im Original. Im Zweifel das Original ansehen.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Auf einen Blick

Downloads pro Wochei
258/Wo.
Verbindung
Computer oder Cloud
Transport
stdio, streamable-http
Neueste Versioni
0.2.1
Kategoriei
Sonstiges
In der Registry veröffentlichti
5. Nov. 2026
Code zuletzt geänderti
9. Nov. 2026
Zuletzt geprüft
16. Nov. 2026
Entwickler
pipeworx-io
Pakete
npm: @pipeworx/mcp-sec-beneficial-ownership
Registry-Status
Aktiv

Welche Apps ihn nutzen können

Basierend darauf, wie sich dieser Server verbindet, und auf der eigenen Doku jeder App, geprüft am 10. Nov. 2026.

Verbinden sich über das Internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

Laufen auf deinem Computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

Alle Apps, mit Vor- und Nachteilen →

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 16. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • ask_pipeworx

    PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring au

  • ask_pipeworx_beta

    Beta version of ask_pipeworx: identical universal router (same 7,498 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so

  • ask_pipeworx_grounded

    Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,498 across 1989 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbati

  • search_within

    Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into th

  • deep_research

    ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1989 STRUCTURED data sources (SEC filings,

  • discover_tools

    Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real est

  • resolve_entity

    "What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools re

  • compare_entities

    "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing

  • subscribe

    Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = o

  • unsubscribe

    Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

  • list_subscriptions

    List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.

  • recent_alerts

    Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp).

  • entity_profile

    "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over cha

  • recent_changes

    "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings s

  • validate_claim

    "Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is f

  • company_facts

    TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the pe

  • company_register_search

    Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CRO number, a CNPJ, a US state entity n

  • scan_dependency

    Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular

  • bet_research

    Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it sett

  • polymarket_arbitrage

    Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `ev

  • polymarket_edges

    Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segme

  • polymarket_kalshi_spread

    Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says s

  • polymarket_fill_risk

    Realizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the di

  • polymarket_edge_tracker

    Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: d

  • kalshi_weather_edge

    Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob

  • resolution_audit

    Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title" — e.g. P

  • resolution_diff

    Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equi

  • release_calendar_markets

    JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are c

  • prediction_calibration

    REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it

  • updown_venue_compare

    The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as

  • updown_divergence_rate

    How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair:

  • archive_evidence

    What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy

  • archive_compare

    What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and b

  • research_row

    Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code in

  • classify_row

    Cheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, e

  • pipeworx_trending

    What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice

  • suggest_questions

    What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed e

  • generate_llms_txt

    Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at si

  • ai_visibility_check

    Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns pe

  • scan_competitor_ai_presence

    Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our co

  • pipeworx_feedback

    Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipewor

  • remember

    Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-v

  • recall

    Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous

  • forget

    Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.

  • sec_13d_filings

    List Schedule 13D / 13G beneficial-ownership filings (and their amendments, 13D/A and 13G/A) for one issuer — AUTHORITATIVE source for "who owns 5%+ of $TICKER" and "has an activist filed a 13D on this company". Takes a ticker or company name (auto-resolved to CIK) or a CIK direc

  • sec_13d_filing

    Parse ONE Schedule 13D or 13G filing by issuer + accession_number (get the accession_number from sec_13d_filings). Returns every reporting owner (the "group members") with percent of class, sole/shared voting power, sole/shared dispositive power, and aggregate shares owned; for S

  • sec_13d_search

    MARKET-WIDE search of Schedule 13D / 13G beneficial-ownership filings by FILING DATE — no ticker needed. AUTHORITATIVE for "which activist investors filed new 13Ds this month and which companies did they target", "who disclosed a 5%+ stake in anything last week", "new 13G filings

  • sec_13d_amendment_diff

    Given one 13D/A or 13G/A amendment (issuer + accession_number), find the SAME reporting group's prior filing in the chain and diff what changed: percent of class, aggregate shares owned, sole/shared voting & dispositive power (per reporting owner, matched by CIK or name), and — f

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 20. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde mit dem GitHub-Konto pipeworx-io bestätigt, dem das Repo gehört

  • ✓ Bestanden

    Wird noch gepflegt

    Code zuletzt geändert: vor 11 Tagen

  • ✓ Bestanden

    Hat eine Lizenz

    Nutzt MIT

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 133 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 48 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Veröffentlichte Schwachstellen (OSV.dev)

Keine Einträge auf OSV.dev für @pipeworx/mcp-sec-beneficial-ownership@0.2.1

Prüft nur diese Paketversion, nicht alle Abhängigkeiten · geprüft 15. Nov. 2026

Was wir prüfen → · JSON

Entwickler: neue Prüfung anfordern oder falsche Angaben melden
Für Anbieter: Badge ins README

Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/pipeworx-io-sec-beneficial-ownership.svg)](https://mcp.popnx.com/en/servers/pipeworx-io-sec-beneficial-ownership)

Diskussion

Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.

Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.

Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.

Anmelden, um zu posten

Nutzerbewertungen

Noch keine Bewertungen

Anmelden, um eine Bewertung zu schreiben

Im Vergleich mit anderen in Sonstigesi

  • Mehr Sterne als 0 % der anderen 20868 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 76 % der anderen 20868 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 99 % der anderen 20868 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist Sec Beneficial Ownership sicher?

Er hat 5 von 5 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.

Läuft er auf meinem Computer oder in der Cloud?

Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt vor 11 Tagen geändert, und die neueste Version (0.2.1) kam vor 15 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL und funktioniert daher auch in Apps mit Remote-MCP, etwa ChatGPT im Web (volles MCP ab Business; Pro nur lesend).

Was kann ich stattdessen nutzen?

In derselben Kategorie: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Ähnliche Alternativen

Gleiche Kategorie, andere Entwickler, Befehle bereits geprüft. Offizielle zuerst, dann nach Sternen.

So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

von koala73Weit verbreitet★ 90.934Aktualisiert vor 4 Tagen

Läuft in der Cloud✓ vom Dienst · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

von openstatusHQWeit verbreitet★ 9276Aktualisiert vor 2 Monaten

Läuft in der Cloud✓ vom Dienst · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

von JanDeDobbeleerWeit verbreitet★ 23.772 Sterne des ganzen ReposAktualisiert vor 31 Tagen

Läuft in der Cloud✓ vom Dienst · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

von Klavis-AIWachsend★ 5824Aktualisiert vor 14 Monaten

Läuft in der CloudRepo archiviert✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

von jitsucomWeit verbreitet★ 5136Aktualisiert vor 4 Monaten

Läuft in der Cloud✓ vom Dienst · jitsu.com
Im Vergleich mit ähnlichen
Dieser
Sec Beneficial Ownership
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Läuft woIn der Cloud oder auf deinem RechnerLäuft in der Cloud, keine InstallationLäuft in der Cloud, keine InstallationLäuft in der Cloud, keine InstallationLäuft in der Cloud, keine InstallationLäuft in der Cloud, keine Installation
Braucht SchlüsselNeinNeinNeinNeinNeinNein
Mit + in Claude hinzufügenNeinNeinNeinNeinNeinNein
Basisprüfungen5/54/44/44/41/44/4
LizenzMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PreisKeine Kosten im RegisterKeine Kosten im RegisterKeine Kosten im RegisterKeine Kosten im RegisterKeine Kosten im RegisterKeine Kosten im Register

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

@pipeworx/sec-beneficial-ownership

SEC Schedule 13D / 13G beneficial-ownership filings — who holds 5%+ of a public company's stock, how (sole vs. shared voting/dispositive power), and — for 13D — why (Item 4 "Purpose of Transaction", the activist-investor signal). Parses the structured XML SEC has required since its 2024 rule, and falls back honestly (structured: false) on older plain-text filings instead of returning nothing.

Part of Pipeworx — an MCP gateway connecting AI agents to 1866+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

  • sec_13d_filings(ticker_or_cik, form_type?, limit?) — list an issuer's Schedule 13D/13G filings (and amendments), newest first. Each row flags whether it is structured XML or pre-2024 plain text.
  • sec_13d_filing(ticker_or_cik, accession_number) — parse one filing: every reporting owner with percent of class, sole/shared voting power, sole/shared dispositive power, aggregate shares owned; for 13D, also Item 4's purpose text. Falls back to bounded plain text for pre-rule filings.
  • sec_13d_search(form_family?, start_date?, end_date?, include_amendments?, limit?, enrich?) — market-wide, by filing date, no ticker needed: "which activists filed new 13Ds in October and which companies did they target". Per filing: the subject company (ticker, CIK), the filers, form, date; for the first enrich structured filings also percent of class, shares owned, event date and (13D) the Item 4 purpose text. Reports total_matches / scanned / truncated so a partial window is never read as a complete one. Source: SEC, Schedule 13D/G filings.
  • sec_13d_amendment_diff(ticker_or_cik, accession_number) — given one 13D/A or 13G/A, find the same reporting group's prior filing in the chain and diff ownership %, voting/dispositive power (per owner), and (13D) whether the Item 4 purpose text changed.

Auth

Keyless. SEC EDGAR is free, public, and requires no API key — only a descriptive User-Agent, which this pack sends on every request per SEC's developer guidelines.

Data sources

  • https://data.sec.gov/submissions/CIK##########.json — per-issuer filing index (form type, accession number, filing date, primary document name). Shared pattern with mcps/edgar.
  • https://www.sec.gov/Archives/edgar/data/{cik}/{accession}/primary_doc.xml — the filing's structured XML, for filings on or after SEC's 2024 structured-data rule (SCHEDULE 13D / SCHEDULE 13G form types).
  • https://www.sec.gov/Archives/edgar/data/{cik}/{accession}/{primary_document} — the filing's plain HTML/text document, for pre-rule filings (SC 13D / SC 13G form types).
  • https://www.sec.gov/files/company_tickers.json — ticker/company-name to CIK resolution, via the shared resolveSecEntity helper (also used by mcps/edgar) — one resolver for every SEC-keyed pack rather than a second implementation here.
Traps worth knowing
  • The submissions index's `primaryDocument` field for a structured filing is a VIEWER path, not the raw document. It reads like xslSCHEDULE_13D_X01/primary_doc.xml — fetching that exact URL returns rendered HTML (an XSLT transform applied server-side for browsers), not machine-readable XML, even though the filename ends in .xml. The actual structured XML always sits at primary_doc.xml directly in the accession's archive root, one directory up, regardless of which XSLT stylesheet variant (X01, X02, …) the viewer path names. This pack always fetches the root path for structured filings; mcps/sec-form-d relies on the same convention for Form D.
  • `SC 13D`/`SC 13G` (pre-rule, plain text) vs. `SCHEDULE 13D`/`SCHEDULE 13G` (post-rule, structured XML) are the SAME form, different eras. SEC's 2024 structured-data rule changed the submission type string, not just the document format. Filter logic in this pack normalizes both to one family (13D / 13G) so a caller filtering by form type gets every era.
  • `previousAccessionNumber` (when present) points to the ORIGINAL filing in the amendment chain, not the immediately preceding amendment. Confirmed live: three successive amendments by the same reporting group all carried the identical previousAccessionNumber (the 2024 original). It also is not universal — a later XSD revision (X0202, seen from at least one large institutional filer) omits it entirely. sec_13d_amendment_diff treats it as one signal of chain membership alongside reporting-owner-identity overlap, not as a direct pointer to "the prior filing."
  • A 13D/A or 13G/A only restates the Items that changed. An amendment's items1To7 (13D) or items (13G) block may simply omit item2, item4, etc. if that item's content is unchanged from the prior filing — this is not a parsing failure, it is how SEC's schema allows amendments to be filed. sec_13d_filing and sec_13d_amendment_diff return null for an absent item rather than inventing content.
  • Schedule 13G has no "purpose" field. 13D's Item 4 is "Purpose of Transaction" (free text); 13G's Item 4 is "Ownership" (amount/percent/voting power, already covered by reporting_owners). item4_purpose is only ever populated for 13D; for 13G it is null with a note explaining why.
  • SEC egress is shared fleet-wide across every SEC/EDGAR pack (one outbound IP). Every tool here reads a bounded, specific set of filings — never a bulk crawl of an issuer's history. sec_13d_amendment_diff's backward scan for the prior filing is capped (MAX_CHAIN_SCAN = 6 filing fetches).

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{

"mcpServers": { "sec-beneficial-ownership": { "url": "https://gateway.pipeworx.io/sec-beneficial-ownership/mcp" } } }

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/sec-beneficial-ownership/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{

"mcpServers": { "pipeworx": { "url": "https://gateway.pipeworx.io/mcp" } } }

Both URLs reach the same gateway and the same 1866+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/sec_13d_filings \

-H 'Content-Type: application/json' \ -d '{"ticker_or_cik":"IMXI","form_type":"all","limit":10}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/sec_13d_filings. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-sec-beneficial-ownership is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/sec-beneficial-ownership/mcp endpoint shown above. It needs network access; there is no offline mode.

{

"mcpServers": { "sec-beneficial-ownership": { "command": "npx", "args": ["-y", "@pipeworx/mcp-sec-beneficial-ownership"] } } }

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": " " } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Sec Beneficial Ownership data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT