Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
คำอธิบายจากผู้ทำ (ภาษาอังกฤษตามต้นฉบับ)
PERM MCP — US green-card labor certification data from DOL PERM (Program Electronic Review…
สามเรื่องนี้ไม่รวมเป็นคะแนนเดียว เพราะความเห็น การวัด และความนิยม เป็นคนละเรื่องกัน
ตัวนี้ยังไม่ได้เรียบเรียงเป็นภาษาไทย ด้านล่างคือข้อเท็จจริงที่เราอ่านจาก registry
เลือกโปรแกรม AI ที่คุณใช้ แล้วคัดลอกค่าตั้งไปวาง
PIPEWORX_API_KEYค่าที่ติดป้ายความลับคือกุญแจของบัญชีคุณ อย่าส่งให้ใคร และอย่าวางในแชต
ต้องเตรียมก่อน
คุณใช้แอปไหน
เลือกแอปด้านบน เราจำไว้ให้ ครั้งหน้าปุ่มจะขึ้นว่า “ติดตั้งลง …”
ใช้ได้ทั้ง Claude บนเว็บ แอปคอมพิวเตอร์ และมือถือ:
https://gateway.pipeworx.io/perm/mcpเปิด Claude Desktop → Settings → Developer → Edit Config แล้ววางค่านี้ในไฟล์ claude_desktop_config.json
{
"mcpServers": {
"perm": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-perm"
],
"env": {
"PIPEWORX_API_KEY": "ใส่ค่าของคุณ"
}
}
}
}พิมพ์คำสั่งนี้ใน Terminal
claude mcp add --transport http perm https://gateway.pipeworx.io/perm/mcpclaude mcp add perm --env PIPEWORX_API_KEY='ใส่ค่าของคุณ' -- npx -y @pipeworx/mcp-permเติมค่าที่เว้นว่างไว้ก่อนรัน
วางในไฟล์ .cursor/mcp.json ของโปรเจกต์ หรือ ~/.cursor/mcp.json
{
"mcpServers": {
"perm": {
"url": "https://gateway.pipeworx.io/perm/mcp"
}
}
}วางในไฟล์ .cursor/mcp.json ของโปรเจกต์ หรือ ~/.cursor/mcp.json
{
"mcpServers": {
"perm": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-perm"
],
"env": {
"PIPEWORX_API_KEY": "ใส่ค่าของคุณ"
}
}
}
}เบราว์เซอร์จะถามก่อนเปิดแอป จากนั้นแอปแสดงค่าตั้งให้ตรวจแล้วกดยืนยัน ช่อง key เว้นว่างไว้ให้คุณใส่เอง
วางในไฟล์ .vscode/mcp.json ของโปรเจกต์
{
"servers": {
"perm": {
"type": "http",
"url": "https://gateway.pipeworx.io/perm/mcp"
}
}
}วางในไฟล์ .vscode/mcp.json ของโปรเจกต์
{
"servers": {
"perm": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-perm"
],
"env": {
"PIPEWORX_API_KEY": "ใส่ค่าของคุณ"
}
}
}
}เบราว์เซอร์จะถามก่อนเปิดแอป จากนั้นแอปแสดงค่าตั้งให้ตรวจแล้วกดยืนยัน ช่อง key เว้นว่างไว้ให้คุณใส่เอง
ChatGPT ต่อได้เฉพาะ server ที่อยู่บนอินเทอร์เน็ต:
https://gateway.pipeworx.io/perm/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.
perm_employer_certificationsCheck whether a US employer sponsors green cards (PERM labor certification) and profile their sponsorship, from DOL PERM (Form ETA-9089) disclosures. Answers 'does company X sponsor green cards' for recruiting and candidate advising. Returns the number of certified PERM filings,
perm_salaryLook up real green-card (PERM) offered wages for a job title from DOL PERM disclosures — a market wage benchmark backed by actual certified filings (not estimates). Answers 'what do green-card-sponsored software engineers earn at company X / in city Y'. Filter by job title, and o
perm_top_sponsorsFind which US employers sponsor the most green cards (PERM labor certifications) for a given job title (optionally in a specific city) — a candidate-sourcing / target-account signal for recruiting. Answers 'which companies sponsor the most data engineers for green cards' or 'top
เราตรวจจากข้อมูลที่ใครก็เปิดดูได้ ยังไม่ได้อ่านโค้ด ข้อที่ไม่เกี่ยวกับตัวนี้ไม่นับในตัวหาร · ตรวจเมื่อ 7 พ.ย. 2569
ชื่อใน registry ยืนยันด้วยบัญชี GitHub pipeworx-io ซึ่งเป็นเจ้าของ repo
ยังไม่ได้อ่านข้อมูล repo จาก GitHub
ยังไม่ได้อ่านข้อมูล repo จาก GitHub
ตอบกลับใน 155 ms (HTTP 200)
ไม่ต้องล็อกอิน
อ่านคำอธิบายเครื่องมือ 47 ตัวแล้ว ไม่พบคำสั่งแอบแฝงถึง AI
เทียบกับทุก server ที่ยังใช้งานในหมวดนี้ทั้งทะเบียน ดาวนับเฉพาะเมื่อผู้ลงทะเบียนเป็นเจ้าของ repo
จากการตรวจเบื้องต้นของเรา ผ่าน 3 จาก 3 ข้อที่ตรวจได้ เรายังไม่ได้อ่านโค้ด ก่อนใส่กุญแจหรือ token ให้ดูว่า server ขอสิทธิ์อะไร และเลือกกุญแจที่ทำได้เท่าที่จำเป็น
ต้องใส่ค่าเหล่านี้: PIPEWORX_API_KEY
ได้ทั้งสองแบบ จะลงในเครื่องหรือต่อผ่านคลาวด์ก็ได้
repo บน GitHub มีการแก้โค้ดล่าสุด – และส่งรุ่นล่าสุด (0.2.1) เข้า registry 3 วันที่ผ่านมา
โปรแกรมที่รองรับ MCP เช่น Claude Desktop, Claude Code, Cursor และ VS Code ตัวนี้ต่อผ่าน URL จึงใช้กับโปรแกรมที่รับ remote MCP ได้ เช่น ChatGPT ที่เปิดโหมดนักพัฒนา
ในหมวดเดียวกันมี Spec Driven Development, Remote Desktop Commander, Draugr
server หมวดเดียวกันจากผู้ทำคนอื่น เรียงตามดาว
อ่านการ์ด:★ ดาว GitHubiสามเสา: รีวิว · ผลตรวจ · การใช้งานiอัปเดต = วันที่ส่งรุ่นล่าสุดเข้า registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
ส่วนนี้คัดจาก repo ของผู้ทำตามต้นฉบับ PopNx MCP ไม่ได้ตรวจหรือรับรองเนื้อหา ตัด HTML รูปภาพ และสคริปต์ออกแล้ว ลิงก์จะพาออกนอกเว็บ
US green-card labor certification data from DOL PERM (Program Electronic Review Management, Form ETA-9089) disclosures — "does company X sponsor green cards", "what does role Y pay at company X under PERM", "who sponsors the most data engineers for green cards". The permanent-labor-certification sibling of @pipeworx/h1b (which covers the LCA / temporary-visa side).
Part of Pipeworx — an MCP gateway connecting AI agents to 1867+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
perm_employer_certifications(employer, year?) — filing count, offered-wage range, top titles/locations for an employer. Total count first, data_as_of on every response.perm_salary(job_title, employer?, city?, year?, limit?) — real disclosed offered-wage stats + a sample of records for a role.perm_top_sponsors(job_title, city?, year?, limit?) — employers ranked by filing count for a role, with median offered wage.Keyless. Local mirror only — no caller credential is needed or accepted.
Why a mirror: PERM, like LCA, is published only as bulk quarterly/annual .xlsx files — it is not on the apiprod.dol.gov v4 gateway that dol-whd/osha/ebsa already use (checked live 2026-10-17: not present in that gateway's 45-dataset catalog). A local Supabase mirror is this pack's only source.
Unlike `h1b`, there is no live fallback. LCA has h1bdata.info, a long-standing third-party aggregator of the same DOL data; no comparable third-party mirror of PERM disclosures was found. So when a query falls outside the mirror's currently loaded fiscal-year window, or the mirror cannot be read at all, every tool returns a coverage_status field and a null (not false) sponsorship/count — never a bare empty result that reads as "this employer doesn't sponsor" when the real reason is that the mirror has not loaded that year yet, or has not completed its first load. Three distinguishable states, same discipline as h1b's fleet #3198 fix:
Employer-name match grading. Both perm_search's SQL (employer_name ILIKE '%' || p_employer || '%') and the stats RPC's grouping are plain substring matches, so a query like "Amazon" can legitimately pull back more than one distinct legal name (verified live against the real FY2025 file: AMAZON.COM SERVICES LLC / Amazon.com Services LLC / Amazon.Com Services Llc / Amazon Data Services, Inc. all appear). matched_employers ranks exact-match first (after stripping case/punctuation and common entity suffixes), then name-contains variants, each tagged name_match — same employerNameKey/gradeEmployerMatch/ rankEmployerVariants logic h1b uses (fleet #3198).
DOL's own record layout (PERM_Record_Layout_FY2026_Q3.pdf, read in full 2026-10-17) carries named-individual contact fields that are never read into the mirror — scripts/perm-transform.py uses an ALLOWLIST of source columns (not a blocklist), so a column DOL adds later is excluded by default:
EMP_POC_{LAST,FIRST,MIDDLE}_NAME, EMP_POC_EMAIL, EMP_POC_PHONE and every EMP_POC_ADDR* field — the employer's named point of contact.ATTY_AG_{LAST,FIRST,MIDDLE}_NAME, ATTY_AG_EMAIL, ATTY_AG_PHONE, every ATTY_AG_ADDRESS*/STATE_BAR_NUMBER/GOOD_STANDING* field — the individual attorney or agent representing the employer (ATTY_AG_LAW_FIRM_NAME, a business name, is also dropped: unused by any tool here).DECL_PREP_{LAST,FIRST,MIDDLE}_NAME, DECL_PREP_EMAIL — whoever signed the employer declaration.FOREIGN_WORKER_*/COUNTRY_OF_CITIZENSHIP/CLASS_OF_ADMISSION field — PERM's layout carries no foreign-worker name field at all (confirmed by reading the full layout), but these still describe the sponsored worker's own nationality/education/experience, and no tool here needs them.Kept: EMP_BUSINESS_NAME/EMP_TRADE_NAME and employer city/state/country/ FEIN/NAICS (no street — same discipline as h1b_lca_disclosures), plus job/wage/worksite fields and case status/dates — this identifies the employer making a mandatory public disclosure, not a private individual.
h1b's LCA mirror, where a closed year's quarterly files are each discrete and all four are needed. PERM_Record_Layout_FY2025_Q4.pdf's own cover page states "Reporting Period: October 1, 2024 through September 30, 2025". So exactly ONE file per fiscal year gives full-year coverage. The still-open current fiscal year's latest quarterly file is likewise cumulative from Oct 1 (FY2026_Q3.pdf: "October 1, 2025 through June 30, 2026").DOL's PERM form (ETA-9089) changed 2023-06-01. Verified live 2026-10-17 against two real downloads: an FY2024 file carries the OLD 155-column shape (e.g. a single EMP_CONTACT_NAME field, no JOB_OPP_WAGE_FROM), while FY2025 and later use the NEW 137-column shape this pack's transform expects. scripts/perm-transform.py's REQUIRED_SOURCE check refuses an old-form file outright rather than silently mis-mapping it — old-form historical backfill (pre-FY2025) is future work, not attempted here. The mirror currently loads FY2025 onward.
supabase/migrations/259_perm_disclosures.sql — perm_disclosures table + perm_ingest_runs bookkeeping + four RPCs (perm_search, perm_stats, perm_top_sponsors, perm_coverage). RLS on; anon/authenticated have no grants; service_role only.scripts/perm-transform.py — streams one .xlsx file row-by-row via openpyxl(read_only=True) (never buffers a whole workbook), allowlist-selects the non-personal columns, and computes base_salary_annual from JOB_OPP_WAGE_FROM/JOB_OPP_WAGE_PER (Hour×2080, Week×52, Bi-Weekly×26, Month×12, Year×1), with the same filer-typo guard h1b's transform uses (an "Hour"-tagged four/five-figure amount is treated as already annual; any annualized result above $5,000,000 is nulled rather than served as data).scripts/perm-upsert.sh — per file: download (tries the current-year URL, falls back to the closed-year archive URL), transform, \copy into a staging table, then INSERT ... ON CONFLICT (case_number) DO UPDATE (CASE_NUMBER is DOL's own stable per-application id — no synthetic key needed)..github/workflows/perm-refresh.yml — workflow_dispatch only (deliberately no schedule: — Bruce's "supa stagger" rule queues big Supabase loads one at a time, overnight, on purpose; GitHub's schedule: trigger has also been unreliable fleet-wide since ~2026-09-09). Default files input: 2026:FY2026_Q3 (current open year) + 2025:FY2025_Q4 (full FY2025).| File | Bytes | Real data rows (transform only, no DB write) |
|---|---|---|
| FY2025_Q4 (full FY2025, Oct'24-Sep'25) | 87,007,731 | 147,056 kept, 1,603 dropped (no CASE_NUMBER) |
| FY2024_Q4 (old form, NOT loaded) | 76,167,854 | refused by transform — old-form shape |
| FY2026_Q3 (current, cumulative) | 156,267,808 | not downloaded during the proof run — estimate ~110k-130k by pro-rating FY2025's full-year count to 9 of 12 months |
case_status values observed live in the real FY2025 file: Certified, Certified - Expired (with spaces around the dash — not Certified-Expired as the record-layout prose might suggest), Denied, Withdrawn. "Certified" filters match the first two.perm_employer_certifications/perm_salary/perm_top_sponsors all return null (never false/0) for sponsorship/counts when the mirror could not answer — check coverage_status before treating an empty result as a real negative.Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": { "perm": { "url": "https://gateway.pipeworx.io/perm/mcp" } } }
tools/list at https://gateway.pipeworx.io/perm/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 1867+ 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/perm_employer_certifications \
-H 'Content-Type: application/json' \ -d '{"employer":"Microsoft","year":2025}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/perm_employer_certifications. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
@pipeworx/mcp-perm 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/perm/mcp endpoint shown above. It needs network access; there is no offline mode.
{
"mcpServers": { "perm": { "command": "npx", "args": ["-y", "@pipeworx/mcp-perm"] } } }
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 i
ตัดมาแค่ช่วงต้น อ่านต่อใน repo