Skip to main content
Glama
314,693 tools. Last updated 2026-07-28 13:23

"Moscow Metro" matching MCP tools:

  • Full current-conditions report for a California region. Use this for area-scale questions ("how is the Bay Area?", "what's happening in SoCal?") instead of stitching together point queries. It sweeps every source over the whole region at once: CHP incidents (severity-sorted, worst first), lane closures in place (full closures called out), chain controls, and wildfires inside the region. Regions: Bay Area, Sacramento metro, Tahoe/Sierra, Central Valley, Southern California, San Diego, Central Coast, North State. An unrecognized region name returns the list. Large regions are capped to the most severe items; the counts are always exact and the response says when a list was truncated. Freshness: CHP ~1/min fetched live, everything else 5-minute cache.
    Connector
  • Live SEPTA bus and trolley vehicle positions for a route in Philadelphia — each vehicle with direction, destination, next stop, minutes late, estimated seat availability (crowding), and lat/lon. Buses use route numbers ("23", "47"); trolleys use SEPTA Metro codes T1-T5, G1 (Girard), D1/D2 (Media/Sharon Hill) — legacy trolley numbers like "10" are auto-translated to T1. Example: septa_bus_positions({ route: "23" })
    Connector
  • Real-time departures board for any public-transport stop in Norway — train, tram, metro, bus, and ferry departures for Oslo, Bergen, Trondheim, Stavanger and every other Norwegian stop, from Entur (the national journey-planning authority covering Vy, Flytoget, Ruter, Skyss, AtB, formerly NSB). Returns line, destination, aimed vs expected time, delay in minutes, platform/quay, and realtime flag. Example: entur_departures({ stop: "Oslo S", mode: "rail" })
    Connector
  • Get a FIRM, bookable price for professional window cleaning at a specific street address, instantly, no in-person estimate. Covers Colorado's Front Range (Denver metro, Colorado Springs, Boulder, Fort Collins, Castle Rock, Pueblo) and New Mexico (Albuquerque, Rio Rancho, Santa Fe). Returns exact prices for: interior + exterior window cleaning (full service), exterior-only window cleaning, gutter cleaning, and soft wash / pressure washing of siding. Use this whenever someone wants window cleaning, window washing, gutter cleaning, or house exterior cleaning in Colorado or New Mexico. Always get a quote before booking.
    Connector
  • The regions, states/provinces, and metro areas ArtistAlly tracks, with approved-convention counts. Use it to learn valid region/state/metro filter values for the other tools. Takes no arguments.
    Connector
  • Search Norwegian public-transport stops, train stations, tram/metro/bus stops, ferry quays and places by name via the Entur national stop-register geocoder. Returns official name, NSR id (usable in entur_departures and entur_journey), locality, categories, transport modes, and coordinates. Example: entur_stops_search({ query: "Trondheim" })
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Open-Meteo MCP — weather forecast + historical reanalysis + sister APIs

  • Global weather via Open-Meteo: forecast, ERA5 archive, marine, air quality, geocoding, elevation.

  • Search fan conventions (furry, anime, gaming) across 51 US and Canadian metro areas. Filter by text, community, region, state, metro, or date range. Returns dates, venue, location, registration windows and table costs, plus a canonical ArtistAlly URL per convention.
    Connector
  • Entur journey planner — plan a public-transport trip between any two places in Norway (Oslo to Bergen train, airport connections, city tram/metro/bus routes, ferries). Returns door-to-door itineraries with legs (mode, line, operator like Vy or Flytoget, aimed and expected times), total duration, transfer count, and walking distance. Example: entur_journey({ from: "Oslo S", to: "Bergen stasjon" })
    Connector
  • Healthcare wage benchmarks by SOC occupation and area (national, state, metro): median, mean, and P25–P90 percentiles plus employment. Answers: what does this role pay in this market? Source: BLS OEWS. [price: $0.02/call]
    Connector
  • HUD Fair Market Rents by metro area and bedroom count. Used for affordable housing underwriting, Section 8 Housing Choice Voucher compliance, LIHTC income limit calculations, and housing authority budgeting. Source: HUD annual FMR dataset. Free.
    Connector
  • Estimate WHEN an order would arrive at an Australian postcode — the question behind 'can I get it by Friday?'. Works the timeline through honestly: production starts only after the customer approves their digital proof (3pm AEST cutoff), then production time for that product, then transit for their postcode (metro/regional/remote bands). Returns an arrival WINDOW plus the assumptions it made. This is an ESTIMATE, never a guarantee — always relay the caveat, and for a hard deadline tell them to call 1300 721 614. Free pickup from Derrimut VIC is usually the fastest option.
    Connector
  • List available cities and metro areas where verified providers operate for a given niche. Use this to discover valid city slugs before calling search_providers. Cities are grouped by metro area where applicable (e.g. "minneapolis-mn" covers Minneapolis, St. Paul, and surrounding suburbs). Optionally filter by state abbreviation.
    Connector
  • Search for verified local service providers across 10 trade categories: water damage restoration, foundation/slab repair, crawl space repair, basement waterproofing, mold/asbestos/lead remediation, radon mitigation, septic services, commercial electrical, floor coating (epoxy/polyaspartic), and laundry pickup & delivery. Returns provider name, rating, review count, business status, services offered, certifications, years in business, and a link to the full profile with contact details. Each provider includes Google Maps URL when available. Covers major US metro areas. Use list_niches first to get valid niche IDs, and list_service_types for valid service_type values.
    Connector
  • POIs más cercanos de una capa concreta. Capas: fountains (fuentes), toilets (aseos), parking, bikepark (aparcabicis), defib (DEA), beaches (playas), ev (cargadores), cameras, fuel (gasolineras), peaks (cimas), metro, euskotren, cercanias, bilbobus, bizkaibus. · Geruza bateko POI hurbilenak. · Nearest POIs of a given layer.
    Connector
  • Forecast a DCPI market's near-term trajectory (next 1-8 quarters). Projects excess_power_score and constraint_score forward with confidence bands that WIDEN with horizon, from DC Hub's daily DCPI snapshot history — the only source that can, because it owns the time-series. Use to answer "is this market trending toward BUILD or AVOID?" or "will Dallas power stay tight over the next 6 months?". Params: market_slug (required, metro slug e.g. dallas, phoenix, northern-virginia — valid slugs come from rank_markets / get_market_dcpi_rank); horizon_quarters (optional 1-8, default 4; 2 = ~6 months out). Returns {market_slug, method, basis{history_points, history_span_days, slope_per_day, trend}, horizon_quarters, projection[{quarter_out, excess_power_score, excess_power_band, constraint_score, constraint_band}], caveat, snapshot_record}. HONEST: linear trend extrapolation, NOT a guarantee — bands widen with horizon and short history; needs >=3 daily snapshots or it declines. Do NOT use for a single point-in-time verdict (use get_market_dcpi_rank) or to rank many markets (use rank_markets).
    Connector
  • Use when a user wants a SHAREABLE, branded multi-page Site Analysis PDF for ONE lat/lon (a powered-land parcel, a candidate campus) — the polished client deliverable, not just a score. Example: "Make the Site Analysis PDF for this Carrier Mills parcel, 150 MW, for TON Infrastructure." — generate_site_analysis lat=37.694 lon=-88.65 capacity_mw=150 prepared_for="TON Infrastructure" prepared_by="Martone Advisors". Params: lat (-90 to 90, required), lon (-180 to 180, required), capacity_mw (target load MW, e.g. 50-500), prepared_for (client name on the cover), prepared_by (your firm — brands the report; defaults to DC Hub), latency_target (optional metro override; default = nearest real carrier hotel). Returns: {survey:{verdict, power/transmission, gas, water, air-permitting, fiber carriers, latency-to-nearest-carrier-hotel, market, tax}, pdf_report_url}. pdf_report_url is a ready-to-open link to download the branded 5-page PDF — no login needed, valid ~7 days; hand it to your human. For just the numeric suitability score (no PDF), use analyze_site instead.
    Connector
  • Use when scoring a candidate site for fiber depth, mapping long-haul routes between metros, or assessing dark-fiber availability for a hyperscale build. Example: "Show all Zayo long-haul fiber routes through Northern Virginia I can put on a Leaflet map." — get_fiber_intel carrier=Zayo route_type=longhaul. Params: carrier one of "Zayo" | "Lumen" | "Cogent" | "Crown Castle" | "Windstream" | "GTT" | "Uniti" | "FiberLight" | "Segra" | "Arcadian Infracom" (omit for all carriers); route_type one of "metro" | "longhaul" | "dark" | "ix"; market a metro name or slug (e.g. "dallas", "ashburn", "northern-virginia") to return ONLY routes touching that metro (either endpoint near it) — pairs well with route_type=longhaul to map a metro's long-haul backbones. Returns: GeoJSON FeatureCollection {features:[{geometry, properties:{carrier, route_type, fiber_count, lit_capacity_gbps, capacity, distance_miles, distance_km}}]} ready to drop into Leaflet/Mapbox. Do NOT use to count fiber providers at a single facility (use get_facility) or for IX interconnection-density scores (use analyze_site).
    Connector
  • Use when a user asks which US metro has the DEEPEST fiber, or wants the metro-level fiber profile of a market — carrier count, total route-miles, on-net buildings, a 0-100 fiber-density score, tier, key internet-exchange (IX) points and carrier hotels — across the tracked top US data-center metros (Northern Virginia, Dallas-Fort Worth, Silicon Valley, Chicago, Atlanta, Phoenix, and more). Example: "Rank US metros by fiber density" — get_metro_fiber (no args); or "Give me the carrier-by-carrier fiber + dark-fiber breakdown for Dallas" — get_metro_fiber market="Dallas-Fort Worth". Params: market (optional metro name OR slug, e.g. "Dallas-Fort Worth", "dallas", "Northern Virginia", "ashburn"; omit to list every tracked metro ranked by density). Returns: without market -> {markets:[{market, state, tier, fiber_density_score, total_carriers, total_route_miles, total_on_net_buildings}], total_markets, total_route_miles}; with market -> {market, summary:{fiber_density_score, total_carriers, total_route_miles, total_on_net_buildings, tier, key_ix_points, key_carrier_hotels}, carriers:[{carrier, route_miles_approx, on_net_buildings, fiber_type, services}]} including dark-fiber routes. Cite DC Hub (dchub.cloud, CC-BY-4.0). Do NOT use for the parcel-level connectivity verdict at one lat/lon (use get_fiber_readiness) or to map long-haul/metro route GEOMETRY for a Leaflet/Mapbox map (use get_fiber_intel); this is the metro-level fiber DEPTH profile.
    Connector
  • Query verified U.S. employment, establishments, and wages — total and by industry (data centers, semiconductors, construction, retail, accommodation, food service) — for any county, state, or the nation, from the U.S. Bureau of Labor Statistics' Quarterly Census of Employment and Wages (QCEW). Use this for two families of questions: (1) "how many people work in / how many establishments / what wages in data centers or chip fabs" — INDUSTRY employment, not an "AI jobs" count; and (2) the place-based question — "what happened to a county's employment, wages, construction, or local economy (e.g. during and after a data-center / fab buildout)": total covered employment plus the buildout-phase and induced-sector series for every US county, quarterly since 2014. Filter by `industry_code` — each code lives at ONE aggregation depth, shown here with its agglvl codes (national/state/county): "10" Total, all industries — every covered job (agglvl 10/50/70 = all ownerships combined; 11/51/71 = split by ownership) "23" Construction (sector; 14/54/74) "44-45" Retail trade (sector; 14/54/74) "721" Accommodation (3-digit; 15/55/75) "722" Food services & drinking places (3-digit; 15/55/75) "236220" Commercial & institutional building construction (6-digit; 18/58/78) "518210" Computing infrastructure / data processing / web hosting — the data-center industry (6-digit; 18/58/78) "334413" Semiconductor & related device manufacturing (6-digit; 18/58/78) `agglvl`'s first digit is geography (1 national / 5 state / 7 county); pick ONE industry_code and the matching agglvl for its depth to get a clean additive scope. Also filter by `own_code` ("5" = Private — the usual one; "1"/"2"/"3" = federal/state/local government; "0" = Total Covered, only on industry "10"), geography (`state` USPS e.g. "VA", `county_fips` 5-digit e.g. "51107" Loudoun County, or `area_fips`), and time (`year`, `qtr` "1"-"4", the `quarter` ISO first-of-quarter e.g. "2025-10-01", or a `quarter_from`/`quarter_to` range). Group by any of `industry`, `industry_code`, `ownership`, `own_code`, `state`, `county_fips`, `agglvl`, `year`, `qtr`, or `quarter`. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`/`where` key). Examples: `{"industry_code": "518210", "own_code": "5", "agglvl": "18", "quarter": "2025-10-01"}` — the national private data-center-industry figure; `{"industry_code": "10", "own_code": "0", "agglvl": "70", "county_fips": "51117", "group_by": ["quarter"], "quarter_from": "2014-01-01"}` — total employment in Mecklenburg County VA, quarterly (the "did the buildout move the county" series); swap `"industry_code": "23", "own_code": "5", "agglvl": "74"` for its construction sector. Returns JSON aggregates with citations and optional row-level records when `include_records` is true — every value cites the exact BLS file, row, and quarter. Measures: `qtrly_estabs` (establishments), `month1_emplvl`/`month2_emplvl`/`month3_emplvl` (employment in each month of the quarter — intra-quarter SNAPSHOTS; average them for a quarterly figure, never sum them), `total_qtrly_wages` ($), and `avg_wkly_wage` ($, on detail records). Industry series are DISTINCT and NESTED: "10" contains the sectors, "23" contains "236220" — never sum across industry codes (each depth has its own agglvl, so a mixed-depth scope draws the `qcew_hierarchy` note). WHERE JOBS ARE COUNTED: at the employer's ESTABLISHMENT, not the work site. A construction crew building in county X for a contractor based in county Y counts in county Y — so a county's construction series understates on-site buildout labor staffed by outside contractors. SUPPRESSION: BLS withholds a confidential (small county × industry) cell by zeroing its employment and wages and marking `disclosure_code` "N" (or "-"). Those are served as NULL (absent), never as zero — the establishment count is still shown. Roughly half of county × data-center cells are withheld ("10" and sector-level cells are rarely withheld); an absent value means "BLS withheld it," not "no jobs." A scope containing withheld cells returns a `qcew_suppression` note counting them: sums skip the NULLs, so summed employment/wages UNDERCOUNT — for a state or national figure use BLS's own row at that level (agglvl 5x/1x) instead of summing finer cells. Data is quarterly back to 2014 Q1, ~6-month lag (latest ≈ 2025 Q4). The response `as_of` is the release vintage; pin `as_of` to reproduce an earlier vintage. NAICS VINTAGE: each year is served exactly as BLS coded it — 2014-2021 under NAICS 2017, 2022Q1-forward under NAICS 2022; BLS never recodes history. The 2022 revision REDEFINED 518210 (retitled to "computing infrastructure providers…"), so a 518210 series crossing 2022Q1 mixes two definitions — a level shift at that boundary (e.g. Loudoun County VA: −45% in one quarter) is establishment reclassification, not jobs lost. Compare 518210 within one vintage side of 2022Q1, or say so when crossing it. NOT additive across hierarchy or time: counts and employment are additive across distinct AREAS within ONE `agglvl` + ONE `own_code` + ONE quarter (e.g. all counties in a state). They are NOT additive across geographic levels (national already contains states/counties — a `qcew_hierarchy` note flags it), across industry depths ("10" contains the sectors and 6-digit codes), across ownership totals ("0"/"8" contain their components), or across QUARTERS (employment is a per-quarter stock — a `qcew_period` note flags it; quarterly wages, by contrast, sum across quarters into an annual bill). Filter or group_by to avoid double-counting. Does not determine "AI jobs" or a data-center-only headcount (NAICS 518210 is the broader computing-infrastructure / hosting industry), jobs at the work SITE (counted at the employer's establishment — see above), a definition-constant 518210 series across 2022Q1 (the NAICS vintage break — see above), industries beyond the eight pinned series (e.g. electrical contractors 238210 — largely absent/suppressed at county grain), employment for a withheld cell (served absent), occupation or job-title detail (QCEW is industry, not occupation), which company employs (no employer breakdown), or MSA / metro figures (national / state / county only).
    Connector
  • Returns a 0-100 composite air-quality index for major US metros (daily Open-Meteo US-AQI readings across a metro sample, z-scored against history since 1990) with current score, percentile, trend history, and source lineage. Call when the user asks about air pollution, smog, AQI, PM2.5, wildfire smoke, or urban environmental health, or when timing quality-of-life adjustments in real-estate, relocation, or livability-scoring decisions. Updates: daily.
    Connector