timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Federal Judicial Center (FJC), Integrated Database — federal case outcomes (fleet #3271).…
이런 작업을 AI에게 가르치는 Skill, 이것과 함께 쓸 수 있습니다
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
목록은 사용 점수(100점 만점)로 정렬되며 구성은 다음과 같습니다
| 인기 | 0/80 | GitHub 별 또는 주간 다운로드: 큰 쪽 60, 작은 쪽 20 |
|---|---|---|
| 최신성 | 12/12 | 30일 안에 릴리스나 코드 변경이 있으면 만점 |
| 응답 중 | 8/8 | 마지막 점검 때 클라우드 엔드포인트가 응답 |
| 사용 점수 | 20/100 |
품질: 기본 점검 5/5개 통과(표시만, 정렬에는 안 씀) · 상승세: 데이터 없음 (급상승 탭에서만 사용)
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
한 문장으로 AI에게 설치 맡기기
Fjc Case Outcomes 설치해 줘. https://mcp.popnx.com/i/pipeworx-io-fjc-case-outcomes.md 를 따라 하고, 명령을 먼저 보여 주고 내가 승인하면 실행해.내 컴퓨터에서 작업하는 AI(Claude Code, Cursor 등)에 붙여 넣으세요. 단계를 읽고 명령을 보여 준 뒤 승인을 기다립니다. 키도 가입도 필요 없습니다. · AI가 읽을 전체 내용 보기
검사 5/5 통과 · 내가 묻는 내용은 제작자 서버(gateway.pipeworx.io)를 거쳐요 · ✓ 명령 확인 2026년 11월 14일
먼저: 어떤 AI를 쓰시나요?
쓰는 앱을 고르면 아래에 단계가 나옵니다.
Claude에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음 · claude.ai나 데스크톱 앱에서 한 번 설정하면 채팅에서 쓸 수 있어요 · 무료 계정은 1개까지 · Team/Enterprise는 소유자(Owner)가 추가
CustomizeConnectors
여기서 복사해 Claude의 같은 이름 칸에 붙여 넣고 Continue를 누르세요
Fjc Case Outcomeshttps://gateway.pipeworx.io/fjc-case-outcomes/mcpClaude가 찾은 로그인 설정 화면에서 Continue를 누르고 · Authentication은 제작자 안내대로(Sign in now, Sign in when needed, No sign in) 고른 뒤 Add를 누르세요
+ConnectorsFjc Case Outcomes
Fjc Case Outcomes을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude가 Fjc Case Outcomes을 쓰고 있다고 하거나 답에 Fjc Case Outcomes 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
ChatGPT 연결은 요금제에 따라 달라요
전체 MCP: 웹 ChatGPT Business, Enterprise, Edu · Pro: 읽기/가져오기 권한으로 연결, 데이터를 바꾸는 도구는 안 될 수 있어요 · Plus: 공식 문서 미확인, 플러그인 화면에 사용자 지정 MCP 추가 항목이 보이면 시도해 볼 수 있어요 · 웹만
Plugins+Add custom MCP server
이름을 넣고 Connection에 주소를 붙여 넣은 뒤 경고에 체크하고 Create as a plugin을 누르세요
Fjc Case Outcomeshttps://gateway.pipeworx.io/fjc-case-outcomes/mcp새 채팅을 열고 입력 전에 플러그인 목록에서 Fjc Case Outcomes을 고르세요
Fjc Case Outcomes을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ ChatGPT가 Fjc Case Outcomes을 쓰고 있다고 하거나 답에 Fjc Case Outcomes 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 OpenAI 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Claude Code에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
Mac: Command+스페이스를 누르고 Terminal 입력 · Windows: PowerShell 열기
claude mcp add --transport http --scope user fjc-case-outcomes https://gateway.pipeworx.io/fjc-case-outcomes/mcpFjc Case Outcomes이 목록에 있고 연결됨으로 보이면 돼요
Fjc Case Outcomes을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude Code가 Fjc Case Outcomes을 쓰고 있다고 하거나 답에 Fjc Case Outcomes 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Cursor에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
Fjc Case Outcomes을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Cursor가 Fjc Case Outcomes을 쓰고 있다고 하거나 답에 Fjc Case Outcomes 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Cursor 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
VS Code에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
Fjc Case Outcomes을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ VS Code가 Fjc Case Outcomes을 쓰고 있다고 하거나 답에 Fjc Case Outcomes 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 VS Code 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Windsurf, Zed, Gemini CLI 같은 다른 MCP 앱은 추가 방법이 저마다 달라요. 앱 목록에서 확인하세요
웹으로 연결하는 앱용 주소
https://gateway.pipeworx.io/fjc-case-outcomes/mcpJSON 설정은 아래 “개발자용”에 있어요
Claude Code
claude mcp add --transport http --scope user fjc-case-outcomes https://gateway.pipeworx.io/fjc-case-outcomes/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"fjc-case-outcomes": {
"url": "https://gateway.pipeworx.io/fjc-case-outcomes/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"fjc-case-outcomes": {
"type": "http",
"url": "https://gateway.pipeworx.io/fjc-case-outcomes/mcp"
}
}
}Claude Code
claude mcp add --scope user fjc-case-outcomes -- npx -y @pipeworx/mcp-fjc-case-outcomesClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"fjc-case-outcomes": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-fjc-case-outcomes"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"fjc-case-outcomes": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-fjc-case-outcomes"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"fjc-case-outcomes": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-fjc-case-outcomes"
]
}
}
}PIPEWORX_API_KEY 비밀 env설명은 자동 번역이며 변수 이름은 원문 그대로입니다. 확실하지 않으면 원문을 확인하세요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
npm: @pipeworx/mcp-fjc-case-outcomes이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.
인터넷으로 연결하는 앱
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
내 컴퓨터에서 실행하는 앱
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
도구 이름과 설명은 서버가 2026년 11월 17일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.
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,215 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,215 across 1874 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 1874 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.
fjc_case_outcome_lookupLook up a SPECIFIC federal case or criminal defendant by docket number in the Federal Judicial Center's Integrated Database (FJC IDB) — civil case, criminal defendant, or appellate case. Needs a docket number plus a district (civil/criminal, FJC's own numeric district code) or ci
fjc_case_outcomes_summaryAggregate federal caseload statistics from the Federal Judicial Center's Integrated Database (FJC IDB) — case counts by nature of suit (civil/appellate), offense code (criminal), disposition, fiscal year and district/circuit. Returns the TOTAL count first, then a breakdown groupe
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 19일 점검
레지스트리 이름이 GitHub 계정 pipeworx-io 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
코드 마지막 변경: 10일 전
MIT 사용
187ms 만에 응답(HTTP 200)
로그인 필요 없음
도구 설명 46개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요
OSV.dev에 @pipeworx/mcp-fjc-case-outcomes@0.2.1 항목이 없습니다
이 버전의 패키지 자체만 확인하며 모든 의존성은 아닙니다 · 확인 2026년 11월 15일
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/servers/pipeworx-io-fjc-case-outcomes)질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
아직 리뷰가 없어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 5개 중 5개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 10일 전 변경됐고, 최신 버전(0.2.1)은 17일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되므로 원격 MCP를 받는 앱에서도 쓸 수 있어요. 예: 웹 ChatGPT(Business 이상은 전체 MCP, Pro는 읽기 전용).
같은 카테고리에는: QueryWeaver, Supabase, Neon, DBCode, Keboola MCP
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
An MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding.
Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.
Query and explore 100+ databases through your DBCode connections.
Connect your AI assistants to Keboola and expose your data, transformations, SQL queries, ...
| 이 항목 Fjc Case Outcomes | QueryWeaver | Supabase | Neon | DBCode | Keboola MCP | |
|---|---|---|---|---|---|---|
| 실행 위치 | 클라우드 또는 컴퓨터 설치 모두 가능 | 컴퓨터에 설치 필요 | 클라우드 또는 컴퓨터 설치 모두 가능 | 클라우드에서 동작, 설치 불필요 | 컴퓨터에 설치 필요 | 클라우드 또는 컴퓨터 설치 모두 가능 |
| 키 필요 | 아니요 | 아니요 | 예 | 아니요 | 아니요 | 아니요 |
| Claude에서 +로 추가 | 아니요 | 아니요 | 예 | 예 | 아니요 | 아니요 |
| 기본 점검 | 5/5 | 3/3 | 5/5 | 5/5 | 2/3 | 5/5 |
| 라이선스 | MIT | AGPL-3.0 | Apache-2.0 | MIT | NOASSERTION | MIT |
| 가격 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 |
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Federal caseload and case-outcome statistics — fleet #3271. Complements the court-listener pack: court-listener finds and reads individual dockets and opinions; this pack answers aggregate statistical questions court-listener has no data for ("how many civil rights cases were filed in SDNY in FY2023, and how did they terminate") plus a direct docket+district outcome lookup.
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.
Migration 264 is applied and fjc-idb-refresh.yml has run for real (run 39288114956): FY2023-24 is loaded — civil 690,312 rows, criminal 435,234 rows, appellate 80,722 rows, plus their summary tables. FY2020-22 is loading separately. The pack was promoted out of _incubator in this session, but `tool-examples.json`, the live smoke payloads, and the post-deploy re-probe are not yet done — they need a real call through the pack against the live backing tables, which needs the backing database's URL and service-role credential as environment variables (see the ingest script's own header for the exact names), and this session had neither (confirmed absent from .env, every .dev.vars, and the process environment). Running node scripts/add-pack.mjs fjc-case-outcomes stopped cleanly at step 3/11 ("backing-store credentials not injected"). Whoever has the credential: node scripts/add-pack.mjs fjc-case-outcomes --from 3 resumes exactly there and writes tool-examples.json from the real calls.
The FJC publishes one SAS7BDAT file per fiscal year per case type, no query API, no multi-year bulk export. Per-year file naming was confirmed live for FY2021-FY2023 (cv23.sas7bdat, cr23_0.sas7bdat, ap23.sas7bdat — see scripts/ingest-fjc-idb.mjs's header for the filename-probing logic, since the suffix is inconsistent and undocumented).
v1 scope: civil + criminal only, FY2020-FY2024 (5 fiscal years). Appellate is included opportunistically where cheap (see sizing below) but is not the committed scope; bankruptcy is out entirely (see below).
Real measured sizing, not an estimate. FY2023 civil (293,677 rows) and criminal (218,853 rows) were parsed from the live SAS7BDAT files and actually loaded into a local Postgres 17 — raw tables, summary tables, indexes, ANALYZE — then measured with pg_total_relation_size:
| Table | Table size | Indexes | Total |
|---|---|---|---|
fjc_idb_civil | 44 MB | 21 MB | 65 MB |
fjc_idb_criminal | 27 MB | 14 MB | 41 MB |
fjc_idb_civil_summary | 1.4 MB | 1.6 MB | 2.9 MB |
fjc_idb_criminal_summary | 0.7 MB | 0.9 MB | 1.6 MB |
| One fiscal year, total | 110 MB |
Extrapolated linearly to v1 (5 fiscal years, civil+criminal): ~550 MB — comfortably under the ~1.5 GB ceiling that would force reconsidering the store. Caveat: this extrapolates from ONE year (FY2023); case volume does vary year to year, so actual 5-year size could differ by some margin, but not by the multiples that would change the conclusion. EXPLAIN ANALYZE on both the lookup query (district+docket, indexed) and a filtered summary-table read confirmed index-scan-only, sub-millisecond, zero sequential scans — see the migration's header for the exact plans.
Bankruptcy IDB data is NOT in scope for this build. The FJC has published bankruptcy case data since 2008, but no bk##/bq##/bankr## filename (plain or _0-suffixed) returned HTTP 200 during this session's probing — it likely uses a different naming scheme or portal entirely. Needs separate research before it can be sized; not attempted further here to keep this build's scope honest rather than guess at a URL.
Supabase (structured relational data, aggregation-heavy queries), not R2/FTS5 — this is tabular caseload statistics with GROUP BY-shaped questions (counts by district/year/nature-of-suit/disposition), not text search. Confirmed viable by the real-load sizing above, not assumed.
Three raw tables (fjc_idb_civil, fjc_idb_criminal, fjc_idb_appellate) carry only the fields the tools here actually use — no raw jsonb catch-all column (an earlier draft had one; dropped on review, since every byte paid for in a real Postgres table even when unused is exactly the cost this revision is supposed to be honest about).
Aggregates are PRECOMPUTED SUMMARY TABLES, not views. A plain GROUP BY view over the raw tables looked cheap in the first draft of this migration, but PostgREST runs under an ~8s statement_timeout, and the uspto-maintenance-fees pack (27.5M rows) timed out on every call under exactly that shape until count=exact and full scans were removed. fjc_idb_*_summary is built ONCE PER FISCAL-YEAR LOAD by scripts/ingest-fjc-idb.mjs (it has no direct SQL connection — only the same PostgREST credential every other pack's ingest uses — so the GROUP BY runs in Node over the already-parsed rows, not in SQL) and reinserted on every full-fiscal-year refresh. The aggregate tool reads ONLY these summary tables, never the raw per-case tables. See the migration's own header comment for the full design rationale.
Full fiscal-year replace, not a row upsert — for both the raw table and its summary table. The IDB's own quarterly update model only revises records within a fiscal year still open for reporting (FJC Research Guide); once a year closes, its file stops changing. A scheduled refresh therefore only needs to re-pull the current (and, defensively, prior) fiscal year's files, delete every previously-loaded row for that (table, fiscal_year) — raw AND summary — and reinsert — scripts/ingest-fjc-idb.mjs --case-type all --years , . A full v1 backfill across FY2020-FY2024 is a separate, one-time run of the same script with a wider --years list. ANALYZE is not run from the script (no direct SQL access); Postgres autovacuum picks it up after a full-year replace touches the whole year's rows — the one-time initial backfill should have a human run a manual ANALYZE via psql as its last step rather than wait on it.
fjc-idb-refresh.yml is live at .github/workflows/fjc-idb-refresh.yml (applied by the config-applier, since .github/workflows/** is push-blocked) and has already run once successfully for the data load (run 39288114956); its smoke step is what will pass once tool-examples.json exists (see "Status" above).
node scripts/add-pack.mjs fjc-case-outcomes --from 3 — this smoke-tests both tools for real against the loaded data, writes tool-examples.json FROM those calls, and carries through the rest of the add-pack checklist (npm-release-status confirmation, deliverable entry).fleet_close on #3271 with the smoke_payloads / live_probes / etc. artifacts the task's acceptance checklist requires.fjc_case_outcome_lookup(case_type, district_or_circuit, docket, fiscal_year?, defendant_number?) — one case's/defendant's outcome by docket number + district (or circuit for appellate).fjc_case_outcomes_summary(case_type, fiscal_year?, district_or_circuit?, nature_of_suit_code?, offense_code?, disposition_code?, group_by?, limit?) — aggregate counts, total first, broken down by whichever dimensions are requested (nature of suit / offense code / disposition / year / district or circuit).Per-year filename suffix is inconsistent and undocumented. cv23.sas7bdat (civil) needs no suffix; cr23_0.sas7bdat (criminal) does; ap23.sas7bdat (appellate) needs none. The ingest script probes both forms per year/case-type rather than hardcoding one pattern.
`pandas.read_sas` returns `NaT` for missing dates, which is NOT caught by a plain `isinstance(v, float) and math.isnan(v)` check and fails json.dumps with TypeError: Object of type NaTType is not JSON serializable — hit live on the civil file's TRANSDAT column (all-NaT for the vast majority of cases, which were never transferred to another district). Fixed by checking pd.isna(v) first, which covers None, float NaN, and NaT in one call.
Criminal defendant names are already redacted by the FJC itself (verified empirically: the NAME column is 100% null across all 218,853 FY2023 criminal rows), per 1995/2003 Judicial Conference policy — there is nothing to carry, so the criminal table has no name field at all. Civil party names (PLT/DEF) ARE populated and published; stored as-is.
Fiscal-year boundaries changed in 1992. Statistical years SY70-SY91 run July-June; FY1993 onward runs the federal government's October-September fiscal year; the 1992 file covers a 15-month transition span. A caller asking for "year 1991" and "year 1993" is asking about non-comparable 12-month windows unless this is accounted for — not yet surfaced in the tool responses; a documented gap for the promotion step to address.
Codes are raw FJC codes (nature of suit, disposition, offense, district, circuit), not yet labelled with human-readable names. See the migration header for why a crosswalk was not guessed at, and the planned follow-up (a small reference table sourced from the FJC's own published codebooks, e.g. https://www.fjc.gov/sites/default/files/idb/codebooks/).
`(fiscal_year, district, office, docket)` is NOT unique — found loading the real FY2023 civil file, not assumed. 293,677 rows resolve to only 290,139 distinct triples (~1.2% collide). The one pair inspected has the same disposition and nature-of-suit but a different filedate (2017 vs. 2023) — likely a reopened or renumbered proceeding; the IDB has no case-level version column to disambiguate. Criminal hit the same shape (collision even including defendant_number). The raw tables therefore have plain indexes, not unique constraints, on this tuple — the ingest script loads every row the FJC publishes rather than deduplicating, and fjc_case_outcome_lookup returns every matching row for a docket.
`fjc_case_outcomes_summary` requires `fiscal_year` and/or `district_or_circuit`. The summary tables are pre-aggregated but an unfiltered, multi-year query could still carry more distinct groups than PostgREST's row cap — a real FY2023-only measurement already has 26,067 distinct civil groups. The tool fetches the full matching set at the summary table's fine grain and re-aggregates client-side to whatever coarser group_by the caller asked for (PostgREST cannot re-GROUP BY a table via a plain select=); if the fetch hits the safety cap the response carries total_may_be_incomplete: true rather than a silently wrong total.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": { "fjc-case-outcomes": { "url": "https://gateway.pipeworx.io/fjc-case-outcomes/mcp" } } }
tools/list at https://gateway.pipeworx.io/fjc-case-outcomes/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