Skip to content
Back to search

mcp-qcew

BLS QCEW pack: county / state / national employment, establishments and wages by industry.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pipeworx-io--mcp-qcew/badge.svg)](/listings/pipeworx-io--mcp-qcew)

HTML

<a href="/listings/pipeworx-io--mcp-qcew"><img src="/api/listings/pipeworx-io--mcp-qcew/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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

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

What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/qcew/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 2034+ data sources. The only difference is which pack's tools are listed **directly**; `ask_pipeworx` reaches all of them from either one.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 128 lines
  1. # @pipeworx/qcew
  2. County, state and national employment, establishments and wages by industry from the U.S. Bureau of Labor Statistics Quarterly Census of Employment and Wages (QCEW).
  3. Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2034+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
  4. ## Tools
  5. - `qcew_area(area_fips, year, quarter, industry?, own?, limit?)` — industries in one area and quarter with title, establishments, three months of employment, total wages, average weekly wage and the over-the-year change. `industry` takes a NAICS code or a title phrase; `own` selects private, federal, state, local or total.
  6. ## Auth
  7. Keyless.
  8. ## Data sources
  9. - U.S. Bureau of Labor Statistics, Quarterly Census of Employment and Wages (county, state and national quarterly data, with industry and area titles).
  10. Quarterly data lags about 5 to 6 months. Small counties suppress industries with few employers; those rows come back flagged `suppressed` with null values rather than being dropped.
  11. ## Quick Start
  12. Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
  13. ```json
  14. {
  15. "mcpServers": {
  16. "qcew": {
  17. "url": "https://gateway.pipeworx.io/qcew/mcp"
  18. }
  19. }
  20. }
  21. ```
  22. ### What this endpoint actually serves
  23. `tools/list` at `https://gateway.pipeworx.io/qcew/mcp` returns the tools in the table
  24. above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
  25. `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
  26. gateway-wide set. So the tool count you see is larger than this table: a
  27. single-pack endpoint currently lists roughly 30 shared tools alongside the
  28. pack's own. The connection's `initialize` response states its exact scope, and
  29. is the authoritative answer for a given day.
  30. This is deliberate, not multiplexing by accident. The meta-tools are what let a
  31. scoped connection answer a question this pack does not cover — via
  32. `ask_pipeworx`, which routes across the whole catalog — without you adding a
  33. second MCP server. There is currently no way to mount a pack endpoint without
  34. them; if the extra schemas cost you more context than the routing is worth,
  35. connect to the full gateway once rather than to several pack endpoints.
  36. Or connect to the full Pipeworx gateway to get every pack's tools listed
  37. directly, instead of just this one's:
  38. ```json
  39. {
  40. "mcpServers": {
  41. "pipeworx": {
  42. "url": "https://gateway.pipeworx.io/mcp"
  43. }
  44. }
  45. }
  46. ```
  47. Both URLs reach the same gateway and the same 2034+ data sources. The
  48. only difference is which pack's tools are listed **directly**; `ask_pipeworx`
  49. reaches all of them from either one.
  50. ## No MCP client? Call it over HTTP
  51. ```bash
  52. curl -X POST https://gateway.pipeworx.io/v1/tools/qcew_area \
  53. -H 'Content-Type: application/json' \
  54. -d '{"area_fips":"06081","year":2026,"quarter":1}'
  55. ```
  56. No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/qcew_area`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
  57. ## Run it from npm
  58. `@pipeworx/mcp-qcew` is a local stdio bridge to the Pipeworx gateway: your MCP client
  59. starts it with `npx`, and it forwards every call to the same
  60. `https://gateway.pipeworx.io/qcew/mcp` endpoint shown above. It needs network access;
  61. there is no offline mode.
  62. ```json
  63. {
  64. "mcpServers": {
  65. "qcew": {
  66. "command": "npx",
  67. "args": ["-y", "@pipeworx/mcp-qcew"]
  68. }
  69. }
  70. }
  71. ```
  72. Without a key it calls anonymously, capped at 50 calls a day. A free account
  73. raises that to 200 a day: get a key at https://pipeworx.io/signup and add
  74. `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
  75. The key is sent as a Bearer token, the same way a hosted connection sends it,
  76. so calls are metered and billed exactly as they are there.
  77. It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
  78. also list `ask_pipeworx` and the other gateway-wide tools.
  79. Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
  80. default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
  81. your Node version's documentation.
  82. ## Using with ask_pipeworx
  83. Instead of calling tools directly, you can ask questions in plain English —
  84. this works on the pack endpoint above as well as on the full gateway:
  85. ```
  86. ask_pipeworx({ question: "your question about Qcew data" })
  87. ```
  88. The gateway picks the right tool and fills the arguments automatically.
  89. ## More
  90. - [Docs and guides](https://pipeworx.io/docs)
  91. - [pipeworx.io](https://pipeworx.io)
  92. ## License
  93. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.