Resolve a Foursquare venue ID to its corresponding Untappd venue, enabling access to Untappd venue data from Foursquare identifiers.
MIT
524,762 tools. Updated 2026-09-06 18:04
"Foursquare" matching MCP tools:
- Get detailed information about a Foursquare place by providing its unique FSQ ID, including name, address, and other attributes.AGPL 3.0
- Retrieve tips and reviews for any Foursquare venue using its unique identifier.AGPL 3.0
- Autocomplete place searches using Foursquare. Input a query to get matching place suggestions.AGPL 3.0
- Retrieve photos for a Foursquare place using its unique ID.AGPL 3.0
- Find venues on Foursquare by submitting a query, coordinates or location name, and optional result limit.AGPL 3.0
Matching MCP Servers
- AlicenseNot gradedqualityCmaintenanceFoursquare Places MCP server enabling AI agents to search and retrieve venue data via the 2025 Places API through the Pipeworx gateway.6MIT
- FlicenseNot gradedqualityDmaintenanceEnables place search and discovery via the Foursquare Places API v3, allowing AI assistants to find venues, search near locations, look up place details, and get location context.-
- Assess commercial area saturation by counting businesses per category within a radius, showing density, ratings, and top places for market analysis.Apache 2.0
- Retrieve the complete list of all Foursquare Swarm check-ins by automatically paginating through the full history. This method makes one API call per 250 check-ins, so use with caution for large datasets.MIT
- Check if a place exists by cross-referencing OSM, Foursquare, and OpenTripMap. Get verification status, confidence score, and canonical name to avoid hallucinated results.MIT
- Resolve a Foursquare venue ID into an Untappd venue to fetch its info and activity. Converts Foursquare identifiers from check-ins into Untappd venue IDs for further queries.MIT
- Retrieve your most visited venues with visit counts from Foursquare Swarm check-in history. Filter by category, city, state, or country.MIT
- Find restaurants, bars, pubs, or cafes near any location. Filter by cuisine, radius, or category and get links to Google Maps, Zomato, TripAdvisor, Yelp, OpenTable, Resy, Untappd, and Foursquare.MIT
- Retrieve statistical summary of your check-in history, including total count and date range. Useful for analyzing your Foursquare Swarm activity.MIT
- Fetch full details of a Foursquare Swarm check-in by providing its check-in ID.MIT
- Retrieve your Foursquare Swarm check-in history with venue details, timestamps, and photos. Paginate and sort results to find past check-ins.MIT
- Send a venue location with name, address, and coordinates to a Telegram chat. Supports Foursquare and Google Places IDs, reply markup, and message protection.MIT
- Get recent Foursquare Swarm check-ins with configurable lookback period and result limit.MIT
- Send a venue's location, title, and address to a Telegram chat, with optional Foursquare or Google Place details.MIT
- 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; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).ConnectorNo auth
- "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 since `since`), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). `since` accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.ConnectorNo auth
- Find 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. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). `topic` (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FILL CHECK: when the partition signal fires, arbitrage.fill_check prices it against live CLOB depth (theoretical_edge_pp_at_book vs realizable_edge_pp at 1000 shares/leg, thin_legs[]) — realizable_edge_pp ≤ 0 means the overround exists only at last-trade, not in the book; do not trade it. For custom sizing use polymarket_fill_risk.ConnectorNo auth