Arcgis Tucson

Name: Arcgis Tucson
Author: pipeworx-io

MCP serverMCP

City of Tucson GIS — Tucson, Arizona open geospatial data (ArcGIS).

by pipeworx-iorepository ↗homepage ↗v0.1.0MIT

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"pipeworx-mcp-arcgis-tucson","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability3/3 checks ok

30 days agotoday

Tools observed via MCP handshake

ask_pipeworx — PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO paten
ask_pipeworx_beta — Beta version of ask_pipeworx: identical universal router (same 5,872 tools, same arguments, same response shape) with candidate routing improvements enabled liv
ask_pipeworx_grounded — Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 5,872 across 1532 sources, fills arguments,
search_within — Semantic 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;
deep_research — ACCOUNT 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 inste
discover_tools — Find 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, pro
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" / "
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 com
subscribe — Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cann
unsubscribe — Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events s
list_subscriptions — List 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 befo
recent_alerts — Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_u
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
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 A
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 cl
scan_dependency — Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (
bet_research — Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-bitcoin-hit-150k-by-june-30-2026"), a polymarket.c
polymarket_arbitrage — Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets b
polymarket_edges — Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover o
polymarket_kalshi_spread — Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their par
polymarket_fill_risk — Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGL
polymarket_edge_tracker — Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide e
pipeworx_trending — What 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 f
suggest_questions — What 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 onb
generate_llms_txt — Generate 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/
ai_visibility_check — Probe 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
scan_competitor_ai_presence — Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces
pipeworx_feedback — Tell 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 th
remember — Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved t
recall — Retrieve 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 tar
forget — Delete 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 re
search_datasets — Search City of Tucson GIS open geospatial datasets (zoning, parcels, public safety, transport & city services) by keyword. Returns each dataset's name, summary,
query_layer — Query an ArcGIS Feature Service / Map Service layer by its url (from search_datasets). SQL-like `where`, comma-separated `out_fields`, `order_by`, `limit`, `off
layer_info — Get an ArcGIS Feature/Map Service layer's schema by url: fields (name + type), geometry type, total record count, and capabilities.

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

npm registry@pipeworx/mcp-arcgis-tucson

first seen 2 d ago · fetched 54 min agoopen ↗

Official MCP Registryio.github.pipeworx-io/arcgis-tucson

first seen 23 h ago · fetched 23 h agoopen ↗

Field history (12 recent events)

23 h ago · declared · name → "Arcgis Tucson"
23 h ago · declared · publisherName → "pipeworx-io"
23 h ago · declared · homepageUrl → "https://pipeworx.io/packs/arcgis-tucson"
23 h ago · declared · repoUrl → "https://github.com/pipeworx-io/mcp-arcgis-tucson"
26 h ago · declared · repoUrl → null
2 d ago · declared · version → "0.1.0"
2 d ago · declared · license → "MIT"
2 d ago · declared · summary → "City of Tucson GIS — Tucson, Arizona open geospatial data (ArcGIS)."
2 d ago · observed · packageFacts → {"name":"@pipeworx/mcp-arcgis-tucson","registry":"npm","publishedAt":"2026-06-25T22:43:04.770Z","latestVersion":"0.1.0",
2 d ago · declared · protocols → ["mcp"]
2 d ago · declared · description → "City of Tucson GIS — Tucson, Arizona open geospatial data (ArcGIS)."
2 d ago · declared · publisherName → "mojibake-ai"

when	check	result	http	latency	detail
41 min ago	mcp initialize	ok	200	1512 ms	server pipeworx-gateway 0.1.0 · protocol 2025-06-18 · 34 tools
8 h ago	mcp initialize	ok	200	1607 ms	server pipeworx-gateway 0.1.0 · protocol 2025-06-18 · 34 tools
16 h ago	mcp initialize	ok	200	1333 ms	server pipeworx-gateway 0.1.0 · protocol 2025-06-18 · 34 tools
23 h ago	mcp initialize	ok	200	20 ms	server pipeworx-gateway 0.1.0 · protocol 2025-06-18 · 34 tools

Arcgis Tucson

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from