@pipeworx/mcp-noirlab-datalab 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mojibake Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,155 @@
+# @pipeworx/noirlab-datalab
+
+NSF NOIRLab's Astro Data Lab — the DECam, Mayall and Blanco survey catalogues (Legacy
+Surveys/DECaLS, DES, DELVE, DECaPS, SMASH, NSC) alongside mirrored all-sky catalogues (Gaia DR3,
+AllWISE, CatWISE, 2MASS, SDSS, DESI), queryable as database tables. Around 130 schemas and tens of
+billions of rows.
+
+Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1679+ live data sources.
+
+## Tools
+
+- `datalab_tables(schema?, table?, limit?)` — list the survey data releases, one release's tables,
+  or one table's columns. Call it first: table names are survey-specific and a guessed name is a
+  query error, not an empty result.
+- `datalab_query(sql, limit?)` — run a read-only ADQL `SELECT`. A `TOP n` is injected when you omit
+  one, so a bare query cannot scan a billion-row table unbounded.
+- `datalab_cone_search(table, ra, dec, radius?, columns?, limit?)` — sources within a radius of a
+  sky position, nearest first, with exact angular separation in degrees.
+
+## Auth
+
+Keyless — **but only through the IVOA TAP endpoint.** See the first trap below.
+
+## Data sources
+
+- <https://datalab.noirlab.edu/tap/sync> — `REQUEST=doQuery&LANG=ADQL&FORMAT=csv&QUERY=…`.
+  Anonymous, and the only door this pack uses.
+
+## Traps
+
+- **`/query/query?sql=` is NOT anonymous, despite being the documented front door.** It is what the
+  `datalab` Python client uses and what the docs lead with, but without a login it answers
+  `401 The provided security token is invalid` — and the widely-quoted
+  `X-DL-AuthToken: anonymous.0.0.anon_access` answers **HTTP 200** with the body
+  `Error in query(). Try checking that you are logged in.` A 200 carrying a failure is the worst
+  shape a failure can take, and it is why this pack speaks TAP only. Measured 2026-09-17.
+- **TAP reports every error as HTTP 200.** Syntax errors, unknown tables, timeouts: all come back
+  200 with a VOTable whose single `INFO` element carries `QUERY_STATUS="ERROR"`. Read as data
+  that is an empty result set. Every response is checked for that element before it is parsed.
+- **ADQL geometry is not implemented, and neither is Q3C.**
+  `CONTAINS(POINT('ICRS',ra,dec), CIRCLE('ICRS',…))` parses and is handed to PostgreSQL verbatim,
+  which answers `function circle(numeric, numeric, numeric) does not exist`. The Q3C functions the
+  backend actually has (`q3c_radial_query`) are rejected by the ADQL parser one layer up. So both
+  obvious cone-search spellings fail. `datalab_cone_search` builds the search from trigonometry
+  both layers accept: an indexable RA/Dec box (RA widened by `1/cos(dec)`, wrapping at 0h) to
+  narrow the scan, then an exact great-circle distance to trim the box corners off and order by
+  true separation.
+- **Row limits are `SELECT TOP n`, not `LIMIT n`.** ADQL, not PostgreSQL.
+- **Zero rows is usually footprint, not absence.** The DECam surveys cover the southern sky and the
+  Galactic plane selectively, so a northern target legitimately returns nothing from `ls_dr10` or
+  `des_dr2`. The zero-result note says to re-check against `gaia_dr3.gaia_source`, which is all-sky.
+
+## Quick Start
+
+Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
+
+```json
+{
+  "mcpServers": {
+    "noirlab-datalab": {
+      "url": "https://gateway.pipeworx.io/noirlab-datalab/mcp"
+    }
+  }
+}
+```
+
+### What this endpoint actually serves
+
+`tools/list` at `https://gateway.pipeworx.io/noirlab-datalab/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:
+
+```json
+{
+  "mcpServers": {
+    "pipeworx": {
+      "url": "https://gateway.pipeworx.io/mcp"
+    }
+  }
+}
+```
+
+Both URLs reach the same gateway and the same 1679+ 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
+
+```bash
+curl -X POST https://gateway.pipeworx.io/v1/tools/datalab_query \
+  -H 'Content-Type: application/json' \
+  -d '{"sql":"SELECT ra, dec, phot_g_mean_mag FROM gaia_dr3.gaia_source WHERE phot_g_mean_mag < 6","limit":5}'
+```
+
+No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/datalab_query`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
+
+## Standalone (no gateway account)
+
+This package also runs as a local stdio MCP server — no Pipeworx account, no
+gateway round-trip:
+
+```json
+{
+  "mcpServers": {
+    "noirlab-datalab": {
+      "command": "npx",
+      "args": ["-y", "@pipeworx/mcp-noirlab-datalab"]
+    }
+  }
+}
+```
+
+Or run it directly to confirm it starts:
+
+```bash
+npx -y @pipeworx/mcp-noirlab-datalab
+```
+
+It speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`
+for **only** this pack's tools — none of the shared meta-tools the gateway
+connection above adds. Same source, same tools, no ask_pipeworx routing.
+
+## 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 Noirlab Datalab data" })
+```
+
+The gateway picks the right tool and fills the arguments automatically.
+
+## More
+
+- [Docs and guides](https://pipeworx.io/docs)
+- [pipeworx.io](https://pipeworx.io)
+
+## License
+
+MIT

package/bin/cli.js

@@ -0,0 +1,17 @@
+#!/usr/bin/env node
+//
+// Entry point for `npx @pipeworx/mcp-<slug>`.
+//
+// Packs ship as raw TypeScript (no build step — see publish-pack.sh for why:
+// tsx sidesteps every extensionless-import / bare-JSON-import edge case a
+// per-pack tsc build would have to solve one pack at a time). This file
+// registers tsx's ESM loader programmatically, then hands off to src/server.ts,
+// which wraps the pack's {tools, callTool} export in a stdio MCP server.
+//
+// Copied verbatim into every published pack repo by scripts/publish-pack.sh —
+// edit this file, not a per-pack copy.
+import { register } from 'tsx/esm/api';
+
+register();
+
+await import('../src/server.ts');

package/package.json

@@ -0,0 +1,32 @@
+{
+  "name": "@pipeworx/mcp-noirlab-datalab",
+  "version": "0.1.0",
+  "description": "NOIRLab Astro Data Lab — datalab.noirlab.edu.",
+  "type": "module",
+  "main": "src/index.ts",
+  "types": "src/index.ts",
+  "bin": {
+    "mcp-noirlab-datalab": "bin/cli.js"
+  },
+  "keywords": ["mcp", "mcp-server", "model-context-protocol", "pipeworx", "noirlab-datalab"],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/pipeworx-io/mcp-noirlab-datalab.git"
+  },
+  "scripts": {
+    "typecheck": "tsc --noEmit"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.30.0",
+    "tsx": "^4.19.0"
+  },
+  "devDependencies": {
+    "typescript": "^5.9.3",
+    "@cloudflare/workers-types": "^4.20260405.1"
+  },
+  "pipeworx": {
+    "sourceHash": "v1-bdbdbce036ad0781055f4a9be485b7edf245fef631a779068fa6ff4251b07cad",
+    "sourceCommit": "b0fb3c31386cf0256dcf1e2f1b3440435a87ec35"
+  }
+}

package/server.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
+  "name": "io.github.pipeworx-io/noirlab-datalab",
+  "title": "Noirlab Datalab",
+  "description": "NOIRLab Astro Data Lab — datalab.noirlab.edu.",
+  "version": "0.1.0",
+  "websiteUrl": "https://pipeworx.io/packs/noirlab-datalab",
+  "repository": {
+    "url": "https://github.com/pipeworx-io/mcp-noirlab-datalab",
+    "source": "github"
+  },
+  "remotes": [
+    {
+      "type": "streamable-http",
+      "url": "https://gateway.pipeworx.io/noirlab-datalab/mcp"
+    }
+  ]
+}