Penthera
Offline, rule-based security checks for your repo, dependencies, AI agent config and local app.
คำอธิบายจากผู้ทำ (ภาษาอังกฤษตามต้นฉบับ)
SEC Form N-PORT — fund and ETF holdings, asked security-first.
สามเรื่องนี้ไม่รวมเป็นคะแนนเดียว เพราะความเห็น การวัด และความนิยม เป็นคนละเรื่องกัน
ตัวนี้ยังไม่ได้เรียบเรียงเป็นภาษาไทย ด้านล่างคือข้อเท็จจริงที่เราอ่านจาก registry
เลือกโปรแกรม AI ที่คุณใช้ แล้วคัดลอกค่าตั้งไปวาง
PIPEWORX_API_KEYค่าที่ติดป้ายความลับคือกุญแจของบัญชีคุณ อย่าส่งให้ใคร และอย่าวางในแชต
ต้องเตรียมก่อน
คุณใช้แอปไหน
เลือกแอปด้านบน เราจำไว้ให้ ครั้งหน้าปุ่มจะขึ้นว่า “ติดตั้งลง …”
ใช้ได้ทั้ง Claude บนเว็บ แอปคอมพิวเตอร์ และมือถือ:
https://gateway.pipeworx.io/sec-nport/mcpเปิด Claude Desktop → Settings → Developer → Edit Config แล้ววางค่านี้ในไฟล์ claude_desktop_config.json
{
"mcpServers": {
"sec-nport": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-sec-nport"
],
"env": {
"PIPEWORX_API_KEY": "ใส่ค่าของคุณ"
}
}
}
}พิมพ์คำสั่งนี้ใน Terminal
claude mcp add --transport http sec-nport https://gateway.pipeworx.io/sec-nport/mcpclaude mcp add sec-nport --env PIPEWORX_API_KEY='ใส่ค่าของคุณ' -- npx -y @pipeworx/mcp-sec-nportเติมค่าที่เว้นว่างไว้ก่อนรัน
วางในไฟล์ .cursor/mcp.json ของโปรเจกต์ หรือ ~/.cursor/mcp.json
{
"mcpServers": {
"sec-nport": {
"url": "https://gateway.pipeworx.io/sec-nport/mcp"
}
}
}วางในไฟล์ .cursor/mcp.json ของโปรเจกต์ หรือ ~/.cursor/mcp.json
{
"mcpServers": {
"sec-nport": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-sec-nport"
],
"env": {
"PIPEWORX_API_KEY": "ใส่ค่าของคุณ"
}
}
}
}เบราว์เซอร์จะถามก่อนเปิดแอป จากนั้นแอปแสดงค่าตั้งให้ตรวจแล้วกดยืนยัน ช่อง key เว้นว่างไว้ให้คุณใส่เอง
วางในไฟล์ .vscode/mcp.json ของโปรเจกต์
{
"servers": {
"sec-nport": {
"type": "http",
"url": "https://gateway.pipeworx.io/sec-nport/mcp"
}
}
}วางในไฟล์ .vscode/mcp.json ของโปรเจกต์
{
"servers": {
"sec-nport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-sec-nport"
],
"env": {
"PIPEWORX_API_KEY": "ใส่ค่าของคุณ"
}
}
}
}เบราว์เซอร์จะถามก่อนเปิดแอป จากนั้นแอปแสดงค่าตั้งให้ตรวจแล้วกดยืนยัน ช่อง key เว้นว่างไว้ให้คุณใส่เอง
ChatGPT ต่อได้เฉพาะ server ที่อยู่บนอินเทอร์เน็ต:
https://gateway.pipeworx.io/sec-nport/mcpชื่อเมนูอาจต่างกันเล็กน้อยตามแพ็กเกจและรุ่นของแอป
ตัวเลือกเก็บในคุกกี้บนเครื่องนี้ ไม่ต้องมีบัญชี
ค่าตั้งนี้สร้างจากข้อมูลใน registry ของผู้ทำ ถ้าไม่ตรงกับ README ให้เชื่อ README
ชื่อและคำอธิบายเครื่องมือตามที่ server ตอบมาเมื่อ 6 พ.ย. 2569 ผู้ทำเป็นคนเขียน ไม่ใช่เรา แสดงเป็นข้อความล้วน
ask_pipeworxPREFER 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_betaBeta version of ask_pipeworx: identical universal router (same 7,176 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_groundedHallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,176 across 1863 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbati
search_withinSemantic 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_researchACCOUNT 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 1863 STRUCTURED data sources (SEC filings,
discover_toolsFind 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
subscribeCreate 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
unsubscribeCancel 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_subscriptionsList 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_alertsPull 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_factsTYPED, 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_searchSearch 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 CNPJ, or an LEI. Use this when you want
scan_dependencyComposite "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_researchResearch 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_arbitrageFind 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_edgesScan 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_spreadCross-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_riskRealizable-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_trackerEdge 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_edgePrices 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_auditExtract 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_diffField-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_marketsJOIN 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_calibrationREALIZED 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_compareThe 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_rateHow 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_evidenceWhat 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_compareWhat 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_rowClaygent-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_rowCheap 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_trendingWhat 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_questionsWhat 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_txtGenerate 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_checkProbe 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_presenceCompare 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_feedbackTell 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
rememberSave 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
recallRetrieve 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
forgetDelete 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.
nport_fund_ownersWhich mutual funds and ETFs hold a given stock or bond, ranked by position size, from SEC Form N-PORT portfolio filings — the reverse of a fund fact sheet, which makes you name the fund first. Give a ticker ("NVDA"), a company name ("NVIDIA"), or a CUSIP. Returns each fund, its s
nport_fund_portfolioThe portfolio a mutual fund or ETF reported to the SEC on Form N-PORT: its largest positions with issuer, value, share or principal count, and percent of net assets. Give the fund or ETF series name ("Vanguard Total Stock Market Index Fund", "SPDR S&P 500 ETF"). Answers "what doe
nport_holdings_coverageWhich SEC Form N-PORT releases are loaded, how many funds each carries, the newest reporting period, and what the data does and does not cover. Also reports N-CEN fund-profile coverage (nport_fund_profile). Use this to check how current fund holdings and profile answers are befor
nport_fund_profileA mutual fund or ETF's profile from SEC Form N-CEN, the annual fund census: ETF/index/money-market status (an explicit flag, which N-PORT holdings filings do not carry), AUM, expense ratio, advisory fee, NAV and market price per share, and its investment adviser(s). Also covers E
เราตรวจจากข้อมูลที่ใครก็เปิดดูได้ ยังไม่ได้อ่านโค้ด ข้อที่ไม่เกี่ยวกับตัวนี้ไม่นับในตัวหาร · ตรวจเมื่อ 9 พ.ย. 2569
ชื่อใน registry ยืนยันด้วยบัญชี GitHub pipeworx-io ซึ่งเป็นเจ้าของ repo
ยังไม่ได้อ่านข้อมูล repo จาก GitHub
ยังไม่ได้อ่านข้อมูล repo จาก GitHub
ตอบกลับใน 247 ms (HTTP 200)
ไม่ต้องล็อกอิน
อ่านคำอธิบายเครื่องมือ 48 ตัวแล้ว ไม่พบคำสั่งแอบแฝงถึง AI
เทียบกับทุก server ที่ยังใช้งานในหมวดนี้ทั้งทะเบียน ดาวนับเฉพาะเมื่อผู้ลงทะเบียนเป็นเจ้าของ repo
จากการตรวจเบื้องต้นของเรา ผ่าน 3 จาก 3 ข้อที่ตรวจได้ เรายังไม่ได้อ่านโค้ด ก่อนใส่กุญแจหรือ token ให้ดูว่า server ขอสิทธิ์อะไร และเลือกกุญแจที่ทำได้เท่าที่จำเป็น
ต้องใส่ค่าเหล่านี้: PIPEWORX_API_KEY
ได้ทั้งสองแบบ จะลงในเครื่องหรือต่อผ่านคลาวด์ก็ได้
repo บน GitHub มีการแก้โค้ดล่าสุด – และส่งรุ่นล่าสุด (0.2.1) เข้า registry 4 วันที่ผ่านมา
โปรแกรมที่รองรับ MCP เช่น Claude Desktop, Claude Code, Cursor และ VS Code ตัวนี้ต่อผ่าน URL จึงใช้กับโปรแกรมที่รับ remote MCP ได้ เช่น ChatGPT ที่เปิดโหมดนักพัฒนา
ในหมวดเดียวกันมี Penthera, Draugr, Harbor
server หมวดเดียวกันจากผู้ทำคนอื่น เรียงตามดาว
อ่านการ์ด:↓ ดาวน์โหลดต่อสัปดาห์i★ ดาว GitHubiสามเสา: รีวิว · ผลตรวจ · การใช้งานiอัปเดต = วันที่ส่งรุ่นล่าสุดเข้า registryi
Offline, rule-based security checks for your repo, dependencies, AI agent config and local app.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
Read-only access to Harbor: projects, artifacts, vulnerabilities, robots, replication, agent skills.
ส่วนนี้คัดจาก repo ของผู้ทำตามต้นฉบับ PopNx MCP ไม่ได้ตรวจหรือรับรองเนื้อหา ตัด HTML รูปภาพ และสคริปต์ออกแล้ว ลิงก์จะพาออกนอกเว็บ
Mutual fund and ETF portfolio holdings and fund profile, from SEC Form N-PORT and Form N-CEN. Keyless.
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.
nport_fund_owners(security, quarter?, limit?) — which funds and ETFs hold a stock or bond, ranked by position size. Takes a ticker, a company name, or a CUSIP.nport_fund_portfolio(fund, quarter?, limit?) — one fund's reported positions, largest first.nport_fund_profile(fund) — a fund's profile: ETF/index/money-market status, AUM, expense ratio, advisory fee, NAV/market price per share, and investment adviser(s). From SEC Form N-CEN, the annual fund census — see "Fund profile" below.nport_holdings_coverage() — which N-PORT and N-CEN releases are loaded, how current they are, and what the data does not cover."Which ETFs hold the largest positions in NVDA?" returned no_match before this shipped, and the router explained the gap in its own words: it would have to check each ETF individually. edgar_fund_holdings goes fund → holdings. Nothing went security → funds, because SEC publishes N-PORT filing-first and so does every API over it. That is a shape problem, not a rate-limit problem.
This is not 13F warmed over. 13F is institutional managers over $100M, long US equity only. N-PORT is registered funds — mutual funds and ETFs — and carries their bond positions too. "Which funds hold this corporate bond" has no 13F answer at all.
The quarterly archive is 441MB across 32 tables. Loaded: equity, preferred and debt positions — about 3.6M of the 5.35M holdings rows per quarter, across 14,416 funds. Not loaded: derivatives, loans, repos and structured products. A swap notional is not a holding of the underlying, and reporting it as one would be a wrong answer wearing a right one's clothes. Every response carries this in its scope field.
Two more caveats ride on every answer:
as_of_period. An answer that implies real-time is wrong.All of it is in Postgres. Measured on the live database, one release loaded:
| table | rows | on disk |
|---|---|---|
sec_nport_holdings | 3,614,371 | 1,123 MB |
sec_nport_funds | 14,416 | 8.9 MB |
That is a real amount of Postgres for one pack, so the choice is worth stating rather than leaving for someone to rediscover at 3am.
The query is the reason. The inversion this pack exists for — *which funds hold this security* — is a selective lookup on cusip and issuer_name returning tens of rows out of 3.6M. That is precisely what a B-tree index is for: it answers in milliseconds and touches almost none of the 1.1GB. R2 has no indexes. Serving the same question from object storage means either scanning the objects or building a side index to point into them, which is a worse database than the one already here.
R2 earns its place when the access pattern is *bulk*: whole-file reads, archival quarters nobody queries interactively, or payloads too large to index usefully. A reasonable split later is hot quarters in Postgres, cold quarters in R2 — but that only pays once several quarters are loaded, and today exactly one is. Splitting now would add a storage tier to save nothing.
Where the line is, so the next person does not have to guess. Each quarter costs roughly 1.1GB. Around four to six loaded quarters this becomes the largest single consumer in the database and the cold-quarter split should be built rather than discussed. sec_13f_holdings sits at 3.8M rows for comparison — this pack is the same order of magnitude, not a new class of problem.
nport_fund_profile answers a different question than the other three tools: not "what does this fund hold" but "what *is* this fund". It reads SEC Form N-CEN, the annual fund census, which carries fields N-PORT's holdings filing does not:
null, never 0.What it cannot answer: inception date. N-CEN's structured data set carries no such field — checked against SEC's own 53-table schema (ncen_readme.pdf) before this was built, not assumed. Every response says so explicitly rather than omitting the field.
Why this can be a year stale. N-CEN is filed annually, once per fund per fiscal year. SEC still releases the structured data quarterly because funds' fiscal year ends are spread across the calendar — one release quarter alone covers only the funds whose year ended in that window (measured against the live 2026q3 release: 2,330 of roughly 9-10k active funds). The ingest script loads a trailing four-quarter window for near-complete single-year coverage. report_ending_period on every response is the fund's own fiscal year end, not today.
ETFs organized as unit investment trusts (SPY, QQQ, DIA) ARE covered, through a separate N-CEN section. A UIT reports its fund-level data through N-CEN's Part F / UIT.tsv table (EXISTING_SERIES_CNT, TOTAL_ASSET_FOR_ALL_SERIES, keyed by accession only, no per-series row) rather than through Part C/D's FUND_REPORTED_INFO.tsv. nport_fund_profile tries Part C/D first and falls back to the UIT table when nothing matches there — verified live against SPDR S&P 500 ETF Trust (SPY, CIK 884394): its 2026 filing (accession 0001410368-26-023904) carries zero FUND_REPORTED_INFO rows but a UIT.tsv row reporting TOTAL_ASSET_FOR_ALL_SERIES of $712,072,540,255.17. A UIT profile returns fund_type: "unit investment trust", total assets, and administrators (a UIT has no investment adviser in the usual sense — it is passively administered) — but no expense ratio, advisory fee, or NAV/market price, because Part F does not report those items at all; uit_profile_note says so on every UIT response. Its N-PORT holdings are separately and fully covered by nport_fund_portfolio/nport_fund_owners (confirmed live: SPY is in sec_nport_funds under registrant "State Street(R) SPDR(R) S&P 500(R) ETF Trust").
Name matching is graded, never a silent best-guess. A query is matched against fund_name with ILIKE '%query%' over a wide candidate pool, then ranked client-side — exact (after normalizing punctuation and generic suffixes like "ETF"/"Trust"/"Fund") beats a prefix match, which beats a plain substring match. The response always carries name_match and, for anything short of exact, a name_match_note plus other_candidates (each with its own grade) — so a contains-match is never presented as *the* fund without saying so. Before this, ranking fell back to whichever ILIKE candidate had the most recent report_ending_period, which could and did pick an unrelated same-family fund over the one actually meant.
The holdings table keys on CUSIP, which is proprietary to CUSIP Global Services, so this pack does not build or cache a bulk CUSIP↔ticker table. A ticker-shaped input resolves live through OpenFIGI (Bloomberg FIGI, openly licensed) to a canonical company name, which is then matched against issuer_name in our own already-ingested rows — preferring the candidate that is not an ETF or option wrapper, because "NVDA" otherwise matches *Direxion Daily NVDA Bull 2X* right alongside NVIDIA and ranks them together. Same discipline as the 13F pack, deliberately.
SEC Form N-PORT structured data (holdings) and SEC Form N-CEN structured data (fund profile) — both published by the U.S. Securities and Exchange Commission.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": { "sec-nport": { "url": "https://gateway.pipeworx.io/sec-nport/mcp" } } }
tools/list at https://gateway.pipeworx.io/sec-nport/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.
curl -X POST https://gateway.pipeworx.io/v1/tools/nport_fund_owners \
-H 'Content-Type: application/json' \ -d '{"security":"NVDA","limit":10}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/nport_fund_owners. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
@pipeworx/mcp-sec-nport 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-nport/mcp endpoint shown above. It needs network access; there is no offline mode.
{
"mcpServers": { "sec-nport": { "command": "npx", "args": ["-y", "@pipeworx/mcp-sec-nport"] } } }
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.
Instead of calling tools directly, you can ask q
ตัดมาแค่ช่วงต้น อ่านต่อใน repo