프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

Finra

제작자: pipeworx-io버전 0.2.1i★ –i컴퓨터 또는 클라우드
레지스트리 이름io.github.pipeworx-io/finra

설치

개요

제작자가 쓴 설명(영어 원문)

FINRA short-sale data — Reg SHO daily short-sale VOLUME plus consolidated bi-monthly SHORT INTEREST.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 컴퓨터 또는 클라우드
  • 전송 방식: stdio, Streamable HTTP
  • 카테고리: 기타
  • 입력해야 할 값: PIPEWORX_API_KEY

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.

필요한 것

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:

  1. Settings → Connectors 열기
  2. Add custom connector 누르기
  3. 아래 주소를 붙여 넣고 Add 누르기
  4. 로그인하라고 하면 제작자의 서비스에 로그인하기
SettingsConnectors1+ Add2https://…3
https://gateway.pipeworx.io/finra/mcp

또는 내 컴퓨터에서 실행하기

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

{
  "mcpServers": {
    "finra": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-finra"
      ],
      "env": {
        "PIPEWORX_API_KEY": "your-value"
      }
    }
  }
}

터미널에서 이 명령어를 실행하세요

claude mcp add --transport http finra https://gateway.pipeworx.io/finra/mcp

또는 내 컴퓨터에서 실행하기

claude mcp add finra --env PIPEWORX_API_KEY=your-value -- npx -y @pipeworx/mcp-finra

실행하기 전에 빈 값을 채워 주세요.

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

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

또는 내 컴퓨터에서 실행하기

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "finra": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-finra"
      ],
      "env": {
        "PIPEWORX_API_KEY": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "finra": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/finra/mcp"
    }
  }
}

또는 내 컴퓨터에서 실행하기

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "finra": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-finra"
      ],
      "env": {
        "PIPEWORX_API_KEY": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:

  1. 웹에서 ChatGPT 열기 → Settings → Connectors (Apps)
  2. Create 또는 Add 누르기(일부 요금제는 먼저 Advanced에서 Developer mode를 켜야 해요)
  3. 아래 주소를 붙여 넣고 이름을 정한 뒤 저장하기
  4. 로그인하라고 하면 제작자의 서비스에 로그인하기
SettingsConnectors1+ Create2https://…3
https://gateway.pipeworx.io/finra/mcp

메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

  • PIPEWORX_API_KEY 비밀 env
    Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

  • 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,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_grounded

    Hallucination-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_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 1863 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 CNPJ, or an LEI. Use this when you want

  • 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.

  • short_volume_daily

    FINRA Reg SHO daily short-sale volume for one symbol on one trading day, summed across every consolidated-NMS reporting facility (Nasdaq TRF Carteret, NYSE TRF, Nasdaq TRF Chicago) so the total matches FINRA's consolidated CNMS figure. Returns short_volume, short_exempt_volume, t

  • short_volume_history

    FINRA Reg SHO daily short-sale volume time series for one symbol — up to 30 trading days ending at `end_date` (default: most recent published day). Each day carries short_volume, short_exempt_volume, total_volume and short_ratio summed across every consolidated-NMS reporting faci

  • short_volume_top

    Ranks symbols on a given trading day by short_ratio (short_volume / total_volume) using FINRA Reg SHO daily data summed across every consolidated-NMS reporting facility. Scans the whole published day (~12,000 symbols) and returns the highest-ratio names. Useful for spotting heavi

  • short_interest

    FINRA consolidated SHORT INTEREST for one symbol — the bi-monthly settlement-date data: total open short position, days-to-cover, average daily volume, and change vs the prior settlement. This is the "% short / days-to-cover" metric investors cite — DISTINCT from short_volume_dai

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 pipeworx-io 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • ✓ 통과

    엔드포인트 응답

    928ms 만에 응답(HTTP 200)

  • – 해당 없음

    OAuth로 로그인

    로그인 필요 없음

  • ✓ 통과

    도구 설명에 숨겨진 지시 없음

    도구 설명 48개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

기타 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 18428개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 18428개 중 86%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 18428개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Finra, 안전한가요?

해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: PIPEWORX_API_KEY

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.2.1)은 6일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Winecellarbuilders

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트
설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 2113일 전 업데이트
설치

Winecellarbuilders

제작자: itsryanarmani

Find the team for your wine room.

클라우드에서 실행오늘 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

@pipeworx/finra

FINRA short-sale data for US equities — daily short-sale volume from the Reg SHO daily dataset, and bi-monthly consolidated short interest. Both come from the FINRA Query API's otcMarket dataset group.

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

The two are different measurements and are constantly confused. Short *volume* is how many shares traded short on a given day. Short *interest* is how many shares are currently sold short and not yet covered, reported twice a month by settlement date — that is the "% short / days-to-cover" figure investors quote.

Tools

ToolWhat it returns
short_volume_dailyOne symbol's short-sale volume for one trading day, summed across every consolidated-NMS reporting facility: short_volume, short_exempt_volume, total_volume, short_ratio, and the per-facility split.
short_volume_historyUp to 30 trading days of the same series for one symbol, ending at end_date. One upstream request, not one per day.
short_volume_topSymbols on one trading day ranked by short_ratio, with a min_total_volume filter to exclude thinly-traded micros. Scans the full published day (~12,300 symbols).
short_interestOne symbol's consolidated short interest by settlement date: open short position, change vs the prior settlement, days-to-cover, average daily volume, plus recent history.

Publishing lag on the Reg SHO data is typically T+1 or better — 2026-08-25's rows were queryable on 2026-08-25. Omit date/end_date and the pack probes back up to 7 days for the most recent day with published rows. Short interest settles bi-monthly, so the newest record is routinely a week or two old — that is the source's cadence, not staleness on our side.

Reporting facilities, and why the sum matters

regShoDaily returns one row per reporting facility per symbol per day. A symbol's real short volume is the sum of them:

FacilityMarket codeVenueIn consolidated NMS?
NQTRFQNasdaq TRF Carteretyes
NYTRFNNYSE TRFyes
NCTRFBNasdaq TRF Chicagoyes
ORFOOTC Reporting Facilityno — OTC / non-NMS securities

combined sums every non-ORF facility, which reproduces FINRA's own consolidated CNMS figure exactly. Verified 2026-08-25 against CNMSshvol20260821: GME on 2026-08-21 sums to short 1,335,397.220545 / exempt 1,355 / total 2,315,275.403735, byte-identical to that file's line (whose own market column reads B,Q,N), and market-wide the same day, 12,269 symbols summing to short 3,244,559,759 / total 6,564,367,888.

Until fleet #532 this pack read only the Nasdaq and NYSE TRFs and asserted current data lived "exclusively" there. It does not: omitting Nasdaq TRF Chicago undercounted short volume by 0.77% and total volume by 0.88% market-wide, every day, with a clean 200 and nothing in the response saying so — and far more on any symbol that trades disproportionately on that facility.

ORF is excluded on purpose, and is a different thing from a missing facility: it is a separate market, not a missing part of this one. A symbol with both gets its ORF volume listed under otc_reporting_facility rather than folded into the NMS total; a symbol with *only* ORF volume is returned with scope: "otc_reporting_facility" and a note, rather than a zero.

Symbol case is significant

A lowercase letter is FINRA's preferred-share marker. On 2026-08-21 BCpC (Bancorp preferred series C, 2,267 shares) and BCPC (Balchem common, 52,413) are two different securities in the same day's data, as are TpC and TPC.

The Query API's equal filter is case-insensitive, so asking for BCPC returns both. This pack therefore never upper-cases a symbol: it resolves to exactly one security, and if your input matches several it returns reason: "ambiguous_symbol" with the candidates rather than adding a preferred series into a common stock's total. When a near-miss symbol exists, it is named in also_reported so you can see it was left out.

Auth

Keyless. The upstream answers without a credential, and no _apiKey is accepted.

Keyless is not the same as unencumbered — see Licence below.

Licence and attribution

All four tools read the otcMarket dataset group at api.finra.org, covered by FINRA's Specific Terms for Equity Data, section 2.3. Two conditions bind us and are not optional:

  • Attribution. FINRA must be clearly identified as the owner and source of the data and of anything derived from it. Every response from this pack therefore carries a leading attribution string, attached centrally in callTool so a new tool or a new early-return cannot ship unattributed by omission. It leads the object so a model synthesizing an answer reads it first, and it survives into ask_pipeworx answers because the answer path passes a pack's structuredContent through verbatim.
  • No incremental fee. We may not charge for the data. The whole pack is therefore zero-rated at the gateway (zeroRated: true on its MCP_PACKS entry): zero credits on every tier including paid, no monthly-volume slot consumed, not counted as a billable lookup inside an answer, and quoted as zero in the pre-call cost disclosure. Responses carry _meta.cost.zero_rated: true. A metered version of any of these tools would be a licence breach, not a pricing choice — do not remove the flag.

End users may not redistribute the data further and are limited to non-commercial personal or professional use; that condition is stated in the attribution string and in section 6 of the published terms at https://pipeworx.io/terms.

Do not reintroduce a `cdn.finra.org` fetch, for a fallback or for freshness. The Reg SHO daily *files* published there are a different distribution, outside the Specific Terms; the general FINRA.org Terms of Use that govern them instead are stricter — non-commercial use only, no redistribution without prior written consent, no bulk copying of the website, no creating a database from it, and an explicit bar on use "in conjunction with any machine learning, neural network, deep learning, predictive analytics or other artificial intelligence computer or software program", which is what every caller of this gateway is. Both routes carried 2026-08-21 on 2026-08-25, so there is no freshness trade to make.

Background: fleet #531 and #532, and the licence analysis in docs/finance-data-ingest-plan.md.

Data sources

  • Reg SHO daily short-sale volume — POST https://api.finra.org/data/group/otcMarket/name/regShoDaily
  • Consolidated short interest — POST https://api.finra.org/data/group/otcMarket/name/consolidatedShortInterest
  • Field names and types — GET https://api.finra.org/metadata/group/otcMarket/name/regShoDaily
  • Catalog: https://www.finra.org/finra-data/browse-catalog/short-sale-volume-daily

Upstream quirks worth knowing if you touch this pack: send Accept: application/json or FINRA returns CSV; limit is capped server-side at 5,000 and the true match count is in the record-total response header; a query matching nothing answers 204 with an empty body, not [], so a naive res.json() throws a parse error that reads like a pack bug when it means "no data for that day"; and sorting is rejected unless the partition key (tradeReportDate) is pinned with an equal filter, so there is no "latest date" query — the pack probes backwards instead.

Quick Start

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

{

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/finra/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 1864+ 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/short_volume_daily \

-H 'Content-Type: application/json' \ -d '{"symbol":"AAPL"}'

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

Run it from npm

@pipeworx/mcp-finra 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/finra/mcp endpoint shown above. It needs network access; there is no offline mode.

{

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

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 Finra data" })

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

More

License

MIT

PopNx에게 묻기