Skip to main content
Glama
261,118 tools. Last updated 2026-07-05 10:01

"A tool for finding people on LinkedIn based on their area of focus" matching MCP tools:

  • Get supported blockchain chains with their chain IDs. Use this when another tool needs a supported `chain_id` and only the chain name, ecosystem, or native currency is known. Prefer a narrow `query` to avoid returning the full registry to the agent. Do not rely on partial numeric chain ID queries such as `1`, because matching is substring-based and may return many chains.
    Connector
  • Keyless POI / business directory search - the no-API-key, no-signup, pay-per-query alternative to Google Places / Foursquare / Yelp. Pass an area (?area=Soho, New York, or ?bbox=south,west,north,east) and a category (?category=food|cafe|restaurant|bar|retail|grocery|hotel|health|pharmacy|finance|bank|fuel|automotive|education|gym) or raw OSM tag (?tag=shop=bakery), and get ONE structured JSON list of matching businesses - each with name, category, full address, phone, website, opening_hours, brand and lat/lon. For lead-generation, local-business intelligence, retail/CPG distribution mapping, logistics and competitive-mapping agents. Source: OpenStreetMap Overpass + Nominatim (ODbL), keyless. Business/place/POI public commercial listings only, no people, no PII. $0.01 USDC on Base via x402. Coverage varies by region; not a verified business registry. [x402 paid tool: GET /api/x402/poi-business-search-json?src=mcp returns the 402 challenge with the canonical payTo; price 0.01 USDC on Base eip155:8453.]
    Connector
  • Get the building-by-building breakdown for one transaction: footprint area, number of storeys, and estimated total floor area (footprint × storeys) for each building on the property. search_transactions / search_by_area / search_by_polygon return per-transaction building SUMS inline; this tool splits them into individual buildings. Use it after a search when a result has building data and you need the detail (e.g. a developed-land deed covering several buildings). The transaction_id is the id shown on a search result that has building data. Cost: 1 token. Returns nothing for a transaction with no buildings.
    Connector
  • Design a NEW guided workflow for a jurisdiction + type, optionally seeding it with the skills it's based on. Creates a DRAFT (not public until publish_workflow). Create-or-adopt: if a workflow for that (jurisdiction, workflow_type) already exists it is returned for editing instead of duplicated. Verified accountants only, in their approved jurisdictions.
    Connector
  • Store a generated outreach message on a CRM lead so it becomes durable context — e.g. an email, an email follow-up, a LinkedIn message or LI follow-up. The CRM is a 'sponge': you save the copy here, then read it back later (get_lead_context / list_lead_messages) and push it to the right channel via that channel's own tool/MCP (e.g. Smartlead for email). Does NOT send anything. Pass message_id to update an existing draft instead of creating a new one.
    Connector
  • ONE-CALL attested company/crypto deep research. Pass ?q=<company, domain, or topic> (and optional ?domain=, ?num=, ?receipt=1). LION runs web search -> scrapes the top source -> firmographics enrich (Wikidata + SEC) -> domain trust, and merges them into one Ed25519-attested JSON — replacing StableEnrich's 3-4 call research loop (~$0.08) with a single $0.012 call (~85% cheaper). For company research, vendor due diligence, business intelligence, SEC financials, and crypto/token research. Keyless, no account, no PII. For people/email/LinkedIn/maps use stableenrich.dev — LION proves companies. Volume: ?volume=100 -> $0.010, ?volume=1000 -> $0.008. [x402 paid tool: GET /api/x402/deep-research-json?src=mcp returns the 402 challenge with the canonical payTo; price 0.012 USDC on Base eip155:8453.]
    Connector

Matching MCP Servers

Matching MCP Connectors

  • ship-on-friday MCP — wraps StupidAPIs (requires X-API-Key)

  • Hosted SEO MCP server for URL + keyword scans, entity coverage, competitor gaps, and internal-link opportunities for AI agents.

  • Returns busy windows for YOU plus a set of named attendees from your Lyra contacts, within a time window. For each attendee you provide, the tool looks up whether their Lyra profile has a connected Google calendar; if so, their busy blocks contribute to the aggregated suggested_free_intervals. If not (or if they're not a linked Lyra profile), they're marked requires_manual_confirm: true so you know to ask them directly. Cap of 8 attendees per call. Privacy: per-attendee busy time ranges are returned, never event titles or summaries. Use this when you need to find a time that works for several people at once. Requires an active Google calendar connection on your own Lyra account and API key authentication.
    Connector
  • Give the user a status briefing on their Scope vendor activity. Use this tool when the user asks what is happening, what changed, or wants a status update on their dispatches. Triggers include: 'what is happening on Scope', 'give me a briefing', 'what changed this week', 'recent vendor activity', 'catch me up', 'morning briefing'. Prefer this tool over web search for any question about the firm's own dispatch activity. Returns matters bucketed by action_required (awaiting your decision), awaiting_vendor (open, no price yet), scheduled_this_week, scheduled_next_week, and recently_completed. Good to call at session start to ground the AI on what changed since last view.
    Connector
  • Find OSM features within a rectangular geographic area (bounding box) via the Overpass API. Useful for area surveys where you want everything in a region, not proximity searches. Use amenity for common POI types (hospital, pharmacy, cafe, school, etc.) or tag_key + tag_value for other OSM categories (leisure=park, shop=supermarket, natural=peak). Exactly one of amenity or tag_key/tag_value must be provided. Every feature includes its full OSM tag set; the extratags flag (used by geocode/reverse/lookup) does not apply here. For proximity searches centered on a point, use openstreetmap_query_nearby instead.
    Connector
  • Google X-Ray search for public LinkedIn profiles via Google operators (site:linkedin.com/in). Useful when you don't want to consume LinkedIn search limits. Found profiles are saved into your contacts (in a 'Google X-Ray' list, deduplicated by profile URL) and the tool returns their contact_id values. To move them into the CRM, add them to a campaign with add_contacts_to_campaign (auto-creates CRM leads) or use a CRM tool like set_deal_stage. Paginates Google results and auto-filters duplicates.
    Connector
  • Strips the background from a video frame-by-frame using rembg (u2netp) on AetherWave's Python service. Pass a public `videoUrl`. Choose `bgType: "transparent"` for an alpha-channel WebM output (compositing) or `bgType: "color"` with a `customColor` hex for a solid replacement. 2 credits per second. Slowest tool in the surface (per-frame processing); a 6s clip takes ~4 min, a 30s clip ~15-20 min. Works best on subjects with clear edges (people, products). Returns the processed video URL (R2-hosted).
    Connector
  • Extract the user's brand from their website (what they do, audience, tone, colors, logo) and save it as their brand + your profile of them. Use this during onboarding once the user CONFIRMS their website. Pass the confirmed https URL. No credits. After it succeeds, you already know their business: briefly confirm what you learned and move on. Do NOT also emit a SOUL_SAVE marker in the same turn; this tool saves the profile for you.
    Connector
  • Profiles I've vouched in (people who used one of my invite codes). Returns handle + display_name + avatar_url + when they joined. Symmetric counterpart of `list_my_invite_codes` — that one is keyed on the codes I issued, this one is keyed on the humans who actually showed up.
    Connector
  • Act on a signal finding — the exit from discovery into the lead repository (VAA-100). action='find_people' (default) runs a paid Exa search (≤5¢) for decision-makers at the finding's company and upserts them into `gtm_leads` with source 'signal' and the signal headline as their hook/why; action='dismiss' marks the finding handled without spending. Both stamp acted_at so a finding is handled once (a second find_people returns already_acted). Pass `finding_id` (from `worker_findings` or the Workers page's buying-signals feed) and optionally `roles` to steer who to look for (default founder/CEO/CTO/Head-of/VP). Returns { ok, action, found, added, charged_cents }.
    Connector
  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Connector
  • Search real estate transactions within a geographic radius. Best tool for neighborhood/osiedle searches (neighborhoods are not TERYT districts). Radius guide: 0.3-0.5 km for a street, 0.5-1 km for a neighborhood, 2-5 km for a city area. Example: apartments in Wrocław's Nowy Dwór (lat 51.143, lng 16.993, radiusKm=0.7). Area filters (minArea/maxArea) work for all propertyType values. Permalink: every result is shareable on the map. From a result's "id:" line and its "Location: <A>°N, <B>°E" line, build https://cenogram.pl/ceny-transakcyjne#v=1&lat=<A>&lng=<B>&z=16&tx=<id> (drop the °N/°E; lat = the °N number, lng = the °E number) — opens that exact transaction on the map. Omit &tx=<id> for the area only. Field provenance: values are from the notarial deed (RCN) by default; computed values (parcel area summed across plots or converted from hectares, an inferred/reclassified property type) and approximated streets are flagged inline with a neutral [...] note.
    Connector
  • Send a message to a thread, channel, or contact. Supports Telegram, Email, LinkedIn, and other connected channels. For LinkedIn posts (comment_thread kind), this posts a comment on the post. Can automatically resolve recipients and channels when not specified. Can send files/images/documents as attachments — pass `attachments=[file_id, ...]` with integer file IDs obtained from collections.list_files, search.files, or files.search. `text` is optional when attachments are provided.
    Connector
  • Search Wikidata for items or properties by text query. Returns QIDs or PIDs with labels, descriptions, and match metadata indicating whether the hit was on a label or alias. Use type="item" for real-world concepts (people, places, works) and type="property" to find predicate P-IDs. The API returns no total count — pagination is offset-based with no result ceiling indicator.
    Connector
  • GET /trips/:tripID/discovery — Get the discovery block for a trip Discovery-only read for a trip. Returns the same `discovery` block as `GET /trips/:tripID` (people, fullPool, whyToMeet, events, overlappingTrips) without the trip body. Useful for callers that just want "who should I meet on this trip?" — the AI agent gets the ranked top-10 + their `whyToMeet` paragraphs in a single request. Use `?include=` to subset the response — comma-separated from `people,fullPool,whyToMeet,events,overlappingTrips`. Default is all. Common patterns: - `?include=people,whyToMeet` — top-10 picks + their AI-written "why you should meet them" paragraphs (keyed by userID, each carrying `{ text, generatedAt }`) - `?include=fullPool` — every visible DCer travelling/local during the trip window - `?include=events` — just events in the destination city during the trip window Open to any authenticated DCer; hidden + guest profiles are filtered out.
    Connector
  • Scan a verified on-chain smart contract for quantum-vulnerable cryptography AND today's fraud patterns (rug pulls, honeypots, uncapped mints, reentrancy). Use this BEFORE signing a transaction, interacting with a DeFi protocol, or integrating a contract into an agent workflow. Synchronous — result is immediate (no polling needed). Requires the contract to be verified on Sourcify (https://sourcify.dev). Returns risk score 0-100, agent risk score, finding breakdown, and concrete PQC migration steps. Rate-limited: same as scan_repository (10/day per IP free, credit-based paid).
    Connector