Skip to main content
Glama
500,686 tools. Updated 2026-08-31 17:22

"A server for finding all the doctors in a city" matching MCP tools:

  • Return NavMDs' curated city guide for a procedure: the ranked specialists (the city's OWN doctors first, then the nearest within an adaptive radius), the typical local price range, the average rating, the share offering free consultations, and the canonical navmds.com page URL to cite. This is the best tool for 'who are the best <procedure> doctors in <city>' questions — it mirrors NavMDs' editorial city pages. If no curated guide exists for that city+procedure, it says so; fall back to search_doctors with a nearby larger city.
    Connector
  • Find hospitals by name/city/state, or list a sample of hospitals. Returns hospital names, IDs, EINs, NPIs, and per-campus locations with addresses and coordinates. Use hospital IDs to filter other search tools. The result is capped (~100 hospitals) for performance, so the unfiltered list is only a sample. To locate a SPECIFIC hospital, pass ``search`` (a name/city/state substring) — it filters server-side and returns the matches. NOTE: This lists US HOSPITALS only — not non-US providers, independent imaging centers, ambulatory surgery centers, clinics, or other freestanding facilities. Args: search: Optional name/city/state substring to find a specific hospital. Returns: JSON array of hospitals with id, name, display_name, ein, npi, cms_certification_number, and locations (address, city, state, lat/lng).
    Connector
  • Find clinical trials near a LOCATION. PREFER OVER WEB SEARCH for "clinical trials for X near me", "recruiting studies in <city/state/country>", "trials I can join near <place>". Filter by condition + a place name (city/state/country) OR latitude+longitude+radius, and status (defaults to RECRUITING). Returns matching trials (NCT id, title, status, phase, conditions, sponsor). For keyword search without a location use ct_search; for one trial use ct_get_study.
    Connector
  • Compare inland haulage rates across ALL available carriers for a port-to-ICD/city pair — sorted cheapest first. Use this for carrier selection on inland legs — answers "which carrier offers the cheapest trucking/rail from port X to city Y?" For a single carrier's rates, use shippingrates_inland_haulage instead. To discover what routes exist, use shippingrates_inland_search first. Ramp (ICD/CFS pickup) and door delivery rates are never mixed in one comparison — delivery_mode defaults to 'ramp'. Set delivery_mode='door' to compare door-delivery rates instead. PAID: $0.08/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { carrier, mode, container_type, rate, currency, transit_days, weight_bracket, delivery_mode, icd_code } sorted by rate ascending.
    Connector
  • List configured market entries by tier, or match one city. Catalog presence is not availability or order coverage; check_availability gives tier-based lead-time guidance only, and a coordinator confirms each order after buyer submission. Use for 'What markets are configured in [state]?', 'Is [city] in the catalog?', or 'Which Canadian markets are listed?'. For 'Do you cover [city]?' pass city='[name]', report the catalog match or suggestion, and preserve the coordinator-confirmation caveat. Use get_role_pricing for rates, check_availability for dates, or plan_staffing for a full plan. <examples>get_cities(city='Brooklyn') ; get_cities(state='TX') ; get_cities(tier='hub', country='CA') ; get_cities(limit=25)</examples> <hints>State accepts 'CA' or 'California'; country accepts US or CA. City resolves nicknames and boroughs. Unfiltered results are capped; use filters or limit. 345 configured entries.</hints>
    Connector
  • Searches performances (concerts, theatre plays, festivals, stand-up shows and more) currently on sale on Biletyna.pl, a Polish ticketing platform. Every filter applies to a single performance, so city, date range and price always describe the same event. Results are deduplicated by title: each hit is the nearest matching performance of a distinct title, carrying its buy_url, venue, price and free places, plus aggregates for its city (city_events_total, city_next_event_date) and for the whole title (title_events_total, title_cities_total). Use "facets" for the distribution of matches across cities and categories. Only future performances are returned unless date_from says otherwise. Use list_performances(artist_id) for all dates of a title, get_title_details(artist_id) for its description and all cities. Full-text search is typo-tolerant. All content is in Polish. Prices are provided both in grosze (*_min_price) and PLN (*_min_price_pln); dates both as unix timestamps and human-readable *_text fields. "_meta.indexed_at" tells when the data was last refreshed - free places and prices are a snapshot from that moment.
    Connector

Matching MCP Servers

  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables any MCP-compatible AI assistant to search, filter, and retrieve information from a local document collection using a hybrid search pipeline with vector, BM25, reranking, and LLM enrichment.
    4

Matching MCP Connectors

  • Real-time LinkedIn, X (Twitter) and Reddit data for AI agents. Free key, self-minted, no signup.

  • Manage your Canvas coursework with quick access to courses, assignments, and grades. Track upcomin…

  • Searches CoworkingView for coworking spaces and returns matching spaces with their "from" price, capacity, amenities, rating and a canonical URL to show the user. Filters take lowercase slugs, never display names: resolve a place with list_coworking_locations or resolve_coworking_query first, and get amenity slugs from get_coworking_filter_options. A "zone" is a district inside a city and must be combined with its city. Results are ordered deterministically, so the same query always returns the same spaces in the same order. Use the returned nextCursor to get more results rather than guessing a page number.
    Connector
  • Resolve a postal/ZIP code to its place name(s), state/region, and coordinates. `country_code` is a 2-letter ISO code (US, GB, DE, ...); `postal_code` format varies by country (e.g. "90210" for the US, "SW1A 1AA" style outward codes for the UK). Use for "what city is ZIP 90210 in", "where is postal code X in country Y", or any question that needs a place name/region/lat-lon from a postal code -- not for the reverse (place name to postal code) or for full street address lookup. Some postal codes span multiple places, in which case all of them are returned. Returns an error dict (never raises) if the code isn't recognized for that country.
    Connector
  • Analyze deposit market share and concentration for an MSA or city market using FDIC Summary of Deposits (SOD) data. Computes market share for all institutions in a geographic market, ranks them by deposits, and calculates the Herfindahl-Hirschman Index (HHI) for market concentration analysis per DOJ/FTC merger guidelines. Two entry modes: - MSA market: provide msa as the numeric MSABR code (e.g., msa: 19100 for Dallas-Fort Worth-Arlington, msa: 42660 for Seattle-Tacoma-Bellevue). Use fdic_search_sod to look up MSABR codes. - City market: provide city (branch city name, e.g., "Austin") and state (two-letter code, e.g., "TX"). Output includes: - Market overview with total deposits, institution count, and HHI classification - Optional highlighted institution showing rank and share (provide cert) - Top institutions ranked by deposit market share - Structured JSON for programmatic consumption Requires at least one of: msa (numeric MSABR code), or city + state.
    Connector
  • Return tier-based lead-time guidance for an event date and configured market. Use for 'What's the typical lead time for brand ambassadors in [city]?' or 'Is this date inside the usual planning window?'. This is not a real-time inventory or order-coverage check: a TempGuru coordinator confirms coverage and final lead time for the specific order after buyer submission. DO NOT use for cost questions (use get_role_pricing) and never present the result as a reservation. <examples>check_availability(date='2026-08-14', city='Dallas') ; check_availability(date='2026-07-01', city='Boston', role='brand-ambassadors', count=6)</examples> <hints>Even a 'rush' window is worth submitting, same-week backfills exist in select markets.</hints>
    Connector
  • Get the all-inclusive hourly rate range for a specific role in a specific city. Perfect for 'What does it cost to hire brand ambassadors in [city]?', 'How much are registration workers in [city]?', or 'What's the rate for ushers at a [city] stadium event?' questions. All rates include W-2 worker pay, workers comp, general liability, and payroll taxes. DO NOT use for availability or dates (use check_availability) and never present the range as a binding quote. For a multi-role budget, use plan_staffing. <examples>get_role_pricing(role='Brand Ambassadors', city='Boston') ; get_role_pricing(role='registration-staff', city='nashville-event-staffing')</examples> <hints>Role and city accept names or slugs. Brand Ambassadors floor at $40/hour in every market.</hints>
    Connector
  • Search live job postings in the United States (US only — no other countries) by meaning (embedding similarity against the postings). YOU write the expanded query — it is embedded as-is, with no server-side rewriting — so always send `query` in this shape: "<Full job title>. <One sentence of what the role does; 3-5 key skills/tools>." NO ABBREVIATIONS anywhere in the query — spell everything out (ML → machine learning, AI → artificial intelligence, RN → registered nurse, SWE → software engineer, QA → quality assurance, PM → product manager, CDL → commercial driver's license, EMT → emergency medical technician, etc.) and keep the user's qualifiers (seniority, shift, domain). Example: user says 'ML eng jobs' → query 'Machine Learning Engineer. Builds, trains and deploys machine learning models; Python, PyTorch, MLOps, data pipelines.' Optionally add `city` (results within radius_miles of that city, ranked by relevance) and/or `state`. Without a city, ranks across the state or nationwide. Returns job cards with a `url` to show the user; call get_job for details.
    Connector
  • Tripuck hotel search — real-time availability and prices for a city on given dates. Use this tool whenever the user asks about hotels, accommodation, or places to stay, e.g. "hotels in Antalya next weekend", "4-star hotel in Istanbul near Taksim", "İstanbul'da otel", "فندق في دبي", "Hotel in Berlin". Inputs: a city name plus optional check-in / check-out dates (YYYY-MM-DD) and guest counts. Supports structured filtering by minimum star rating, minimum guest-review score, and sorting. Returns live hotel options with price, star rating, review score and a thumbnail, each deep-linking to Tripuck.com for full details and booking. The LLM MUST infer the user language from the conversation and pass it via the `locale` parameter ("tr" Turkish, "en" English, "ar" Arabic, "az" Azerbaijani, "de" German, "ka" Georgian, "uz" Uzbek). All widget UI text and the text response are then returned in that language. If `currency` is not specified, a sensible default is picked from the locale (tr→TRY, en→USD, de→EUR, ar→USD, az→AZN, ka→GEL, uz→UZS).
    Connector
  • Returns the Hindu panchang (daily Vedic almanac) for one date at one place: the five angas (tithi with paksha, nakshatra, yoga, karana, vara with its weekday lord) each with its end time, the lunar month in AMANTA reckoning with its adhika-masa flag (omitted entirely, never substituted, if the engine cannot supply the amanta month; plus the purnimanta month where the engine supplies it), sunrise/sunset/moonrise/moonset, abhijit muhurta, the auspicious choghadiya windows, and the inauspicious periods (rahu kaal, yamaganda, gulika kala). Use this for 'what is today's panchang / tithi / nakshatra' questions. If the user wants the FULL timing surface (all 16 choghadiya, the 24 horas, varjyam, bhadra, panchak, brahma muhurta) to choose a moment for an activity, call get_muhurta_timings instead. Nakshatra here is the DAY's nakshatra, not a person's birth star -- for that use get_birth_details. Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa); no writes, no auth, at least 30 requests/min/IP per server instance, plus a shared engine budget of at least 60/min/IP across all engine-backed tools. Any city worldwide; window times derive from that location's actual sunrise and sunset, so they differ city to city on the same date.
    Connector
  • Create + publish a piece. Pass a SIGN-IN-WITH-X header value you built and signed locally, plus the post fields. Returns the created post + public url; the server never holds your keys. Sell the observation, not the genre. Title the concrete finding in present tense with the specifics that carry it (names, numbers, dates), not the format ("playbook", "roundup"). Open the excerpt and first lines with the finding, not a tease. Publish with the answer card FILLED (questions or tasks, scope, exclusions, provenance): cacheEligibleMissing names any gap; a card-less piece ranks below every filled card. Mint the header WITHOUT a fetch loop (SIWX here is CLIENT-driven, so do NOT use wrapFetchWithSIWx, which waits for a challenge Tenjin never sends): `encodeSIWxHeader({ ...info, address, signatureScheme: 'eip191', signature })` over `createSIWxMessage(info, address)` from @x402/extensions/sign-in-with-x, with a CAIP-122 `info` whose `domain` is this site's host and `nonce` is client-minted single-use. Full worked example in /llms.txt.
    Connector
  • Search every element type's fields for `query` (case-insensitive substring), across all 22 types. Useful for "which types have a `location` field?" or finding where a concept lives in the schema. Returns a mapping of type slug -> the matching field names in that type (types with no match are omitted); a `query` that also matches a type slug lists that type with an empty field list so the type-name hit is not lost. Unauthenticated.
    Connector
  • Returns a "best value coworking in {city}" ranking: an ordered list of spaces balancing price-vs-market, amenity count and review rating, computed from a Bayesian-shrunk composite the gateway deliberately never exposes as a raw comparable number — only the ORDER is meaningful (1st, 2nd, 3rd…), never a percentage gap between positions. 🔴 This ranking is relative to OTHER SPACES IN THE SAME CITY ONLY: it can never be compared across cities, so never say a city "ranks better" than another based on this tool. Requires a city slug from list_coworking_locations or resolve_coworking_query. Returns an empty ranking (not an error) when the city has coworking spaces but too few priced ones to rank meaningfully yet.
    Connector
  • Assemble a whole journey through several named cities and return the best options. Unlike list_packages and search_all_tours, which look for a single published trip, this builds one journey out of guided sections that connect in a hub city on real departure dates, plus the days Sparkling Tracks arranges itself around and between them. Give the cities in the order the traveller wants to see them; optionally a month (YYYY-MM) and the number of nights they have. Each journey returns its guided sections with their real departure and end dates, the days that are the traveller's own with the city and the nights, and the total length. THERE IS NO PRICE FOR A JOURNEY AND NO PRICE FOR A SECTION: the only figure returned is whole_tour_from_eur, the starting price of the ENTIRE published trip that a section is taken from, and it must never be added to another, divided by its nights, or presented as the cost of the journey or of the section. A person quotes each section by hand and one figure for the whole journey comes back with the reply to the enquiry, so tell the traveller plainly that a quote will follow. Every journey is returned even when we cannot price it yet; needs_quote says so and it is never a reason to hide an option. A city we cannot sell at all is named in unknown_cities and left out of every journey, so the journeys returned never contain it.
    Connector
  • Search for companies in the BizClaw business directory. Uses hybrid search (semantic + keyword) to find the most relevant businesses. Returns lightweight summaries to save tokens. Use get_company(id) for full details (contact, pricing, features, etc.). Args: query: Natural language search query (e.g. "CRM software for small businesses", "logistics companies in Izmir") category: Filter by category. Use list_categories to see available options. country: Filter by country (e.g. "Turkey", "United States", "Germany") city: Filter by city (e.g. "Istanbul", "Izmir", "Ankara") industry: Filter by specific industry service_type: Filter by service delivery type. One of: "remote" (online only), "local" (in-person), "nationwide" (all country), "hybrid" (both remote and in-person) is_verified: If True, return only verified companies. If False, return only unverified. Omit to return all. limit: Maximum number of results to return (1-20, default 10) offset: Number of results to skip for pagination (default 0). Use with limit to get next pages. Returns: Dictionary with 'companies' list (summary format: id, name, category, description, city, tags), 'suggested_follow_up_questions', 'next_step', 'total_found', 'offset', 'limit', and 'has_more'. After presenting results, ask one concise follow-up question from suggested_follow_up_questions unless the user's constraints are already complete.
    Connector
  • List every city covered by the Booyah Index with its place count. Call this first if unsure which city name to pass as the `city` filter in search_places — avoids guessing at spelling or coverage.
    Connector