Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
RescueGroups.org MCP — adoptable animals and the rescues/shelters that list them, from the…
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
PIPEWORX_API_KEYAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://gateway.pipeworx.io/rescuegroups/mcpÖffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"rescuegroups": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-rescuegroups"
],
"env": {
"PIPEWORX_API_KEY": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add --transport http rescuegroups https://gateway.pipeworx.io/rescuegroups/mcpclaude mcp add rescuegroups --env PIPEWORX_API_KEY=your-value -- npx -y @pipeworx/mcp-rescuegroupsTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"rescuegroups": {
"url": "https://gateway.pipeworx.io/rescuegroups/mcp"
}
}
}In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"rescuegroups": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-rescuegroups"
],
"env": {
"PIPEWORX_API_KEY": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"rescuegroups": {
"type": "http",
"url": "https://gateway.pipeworx.io/rescuegroups/mcp"
}
}
}In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"rescuegroups": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-rescuegroups"
],
"env": {
"PIPEWORX_API_KEY": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://gateway.pipeworx.io/rescuegroups/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
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.
rescuegroups_adoptableSearch adoptable animals listed by rescues and shelters on RescueGroups.org: name, breed, age, sex, size, temperament flags (good with kids/dogs/cats), photos, and the listing organization. Filter by species, postal-code radius, breed, sex, age group and size. Requires your own R
rescuegroups_animalFull record for one adoptable animal by RescueGroups id — description, all photos, breeds, adoption fee, temperament and the listing rescue/shelter with its contact details. Requires your own RescueGroups API key. Example: rescuegroups_animal({ animal_id: "8013243", _apiKey: "you
rescuegroups_organizationsFind animal rescues and shelters with RescueGroups.org accounts: name, type (Rescue or Shelter), address, phone, email, website, adoption process, areas served and services. Filter by postal-code radius, state or name. Requires your own RescueGroups API key. Example: rescuegroups
rescuegroups_speciesThe species vocabulary RescueGroups uses — singular, plural and young-animal words for each species it lists. Use it to get the exact `species` value rescuegroups_adoptable expects. Requires your own RescueGroups API key. Example: rescuegroups_species({ _apiKey: "your-key" })
rescuegroups_breedsBreeds RescueGroups recognises for a species, for building an exact breed filter. Requires your own RescueGroups API key. Example: rescuegroups_breeds({ species: "dogs", limit: 50, _apiKey: "your-key" })
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto pipeworx-io bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Antwort in 308 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 49 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: PIPEWORX_API_KEY
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.2.1) kam vorgestern in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, jwatte.com free website tools
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Find free website audit tools, run links, blog articles and book details on jwatte.com.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Adoptable animals listed by rescues and shelters on RescueGroups.org, and the organizations themselves — name, breed, age, sex, size, temperament flags, photos, adoption fee, and the rescue's contact details, adoption process and areas served. Searchable by species, postal-code radius, breed and trait.
Part of Pipeworx — an MCP gateway connecting AI agents to 1866+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
rescuegroups_adoptable(species?, postalcode?, lat?, lon?, miles?, kilometers?, breed?, sex?, age_group?, size_group?, name?, good_with_kids?, good_with_dogs?, good_with_cats?, views?, org_id?, include_adopted?, sort?, limit?, page?, _apiKey) — the main search. Answers "adoptable beagles within 50 miles of 15206", "cats good with kids in Pittsburgh", "dogs needing a foster". Returns the animal's full attribute set with breeds, pictures, species and listing organization resolved inline.rescuegroups_animal(animal_id, _apiKey) — one animal in full, with every picture, colour, pattern, status and the listing org.rescuegroups_organizations(postalcode?, lat?, lon?, miles?, kilometers?, name?, state?, city?, type?, org_id?, sort?, limit?, page?, _apiKey) — rescues and shelters. Answers "shelters within 25 miles of me", "who is RescueGroups org 1234".rescuegroups_species(limit?, page?, _apiKey) — the species vocabulary, which is what rescuegroups_adoptable's species argument expects.rescuegroups_breeds(species?, limit?, page?, _apiKey) — breeds per species, for building an exact breed filter.BYO-key only. Pipeworx holds no RescueGroups key and this pack never reads a platform one — _apiKey is required in every tool's input schema, so the gateway's disclosure surface tells a caller before the call, not after a refusal.
Request a free public key at https://rescuegroups.org/services/request-an-api-key/. It is a short form (name, email, organisation, site URL, which species and whether you want a national search). It is open to individual developers — "not incorporated" is an accepted incorporation status, and the API docs state plainly that you do *not* need a RescueGroups account, only a public key. Staff review the form and email the key back, so it is not instant self-serve; the refusal message says so rather than promising a key in one click.
Note for anyone reading
docs/paid-upgrade-watchlist.md: its entry filing
RescueGroups under "signup not obtainable by a normal dev — requires being an
animal rescue with a vet, shelter, euthanasia policy" describes the *partner
onboarding* at
/partner-requirements-and-expectations/, which is how a
rescue gets its animals listed. The public API key form is a different,
open one. That entry has been corrected.
An invalid key is a silent zero, not an error. Probed live 2026-09-05:
GET /v5/public/animals/search/available/dogs/?limit=1 (no Authorization)
-> 401 application/vnd.api+json {"errors":[{"status":401,"source":{"header":"Authorization"}, "title":"Missing authorization header", "detail":"Missing authorization header - apikey authentication required"}]}
GET /v5/public/animals/search/available/dogs/?limit=1 (Authorization: ) -> 200 OK, Content-Length: 0, Content-Type: text/plain;charset=UTF-8
A *rejected* key returns HTTP 200 with a completely empty body, not a 401 — and it does so whether or not the required Content-Type header is present (checked both ways; the empty 200 is not an artefact of omitting it). Passed through naively that reads as "there are no adoptable dogs near you", which is both wrong and unfixable by the user because nothing points at their key. This pack therefore treats any empty non-JSON 200 as an auth failure and says so. See docs/silent-zero-policy.md.
Consequently the three states a caller can be in read differently, on purpose:
| State | What they see |
|---|---|
No _apiKey at all | "RescueGroups requires an API key, and Pipeworx does not supply one." + where to request one |
_apiKey rejected upstream | "the API key you passed as _apiKey was not accepted" + how RescueGroups signals it + key-scoping caveat |
| Upstream 401 with a key sent | "authorization failed (HTTP 401)" + the upstream's own detail |
The key never leaves the Authorization header. It is not put in a URL (a URL is logged by every hop whether or not the call succeeds), it is deleted from args before any handler runs so it cannot reach a usage record, and every string relayed from upstream is passed through a redactor first — so even if RescueGroups started quoting the key back in an error detail, the caller-facing message would not carry it. Verified by a test that plants a recognisable secret and asserts it appears in none of the URL, body, result or error paths.
Keys are scoped at issue time. The request form asks which species and whether you want just your own organization or a national search. A key issued narrowly returns fewer rows — or none — for a query outside its scope, which looks identical to a genuinely empty result. The rejected-key message names this possibility so a caller with a legitimately narrow key is not sent chasing a bad-key theory.
`Content-Type: application/vnd.api+json` is required on every request, including GETs, per the docs. Sent unconditionally here.
Views stack in the URL path, filters go in a POST body. available, species (dogs), and traits (haspic, urgent, isneedingfoster) are "views" and concatenate: /public/animals/search/available/dogs/haspic/. Anything else — breed, sex, size, postal-code radius — is a filters / filterRadius object POSTed to the same search URL. The pack picks GET or POST based on whether the caller supplied anything needing a body.
**Distance searches need a location *and* a radius.** Half of one is rejected locally rather than sent, because RescueGroups silently returns unfiltered results for a location with no radius, which looks like the radius was honoured.
Org search with no `type` needs two calls. rescue and shelter are the only org views, a filtered org search requires a view in the path, and the two cannot be stacked (they would AND to nothing). With no type the pack queries both and merges, and says so in a note — pages is not meaningful on that path, so pass type if you need to page.
Null attributes are omitted, not nulled (v5 change log, 2019-10-03), and the field set grows over time. The response mapper is deliberately generic — it flattens JSON:API attributes wholesale and resolves relationships against included one level deep — rather than listing fields, so new upstream fields appear instead of being silently dropped. raw always carries the untouched body.
Rate limits are unpublished. The docs say only that the API returns 429 for "an abnormal number of requests" and asks callers to cache reference data. Cache rescuegroups_species and rescuegroups_breeds; they change rarely.
There is a test environment at test1-api.rescuegroups.org with the same routes, but it also requires a key, and its data may be weeks stale and may not be used in production. Not wired up here.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": { "rescuegroups": { "url": "https://gateway.pipeworx.io/rescuegroups/mcp" } } }
tools/list at https://gateway.pipeworx.io/rescuegroups/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 1866+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/rescuegroups_adoptable. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
@pipeworx/mcp-rescuegroups 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/rescuegroups/mcp endpoint shown above. It needs network access; there is no offline mode.
{
"mcpServers": { "rescuegroups": { "command": "npx", "args": ["-y", "@pipeworx/mcp-rescuegroups"] } } }
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.
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 Rescuegroups data" })
The gateway picks the right tool and fills the arguments automatically.
MIT