Skip to main content
Glama
744,934 tools. Updated 2026-11-05 01:14

"Finding people on GitHub" matching MCP tools:

  • Monthly Amazon search volume for up to 1,000 keywords you already have, in the order given. Use when: "how many people search Amazon for X", comparing Amazon demand with Google demand, sizing a product idea on Amazon. Not for: Google volume, use seo_get_keyword_metrics. Finding keywords, use amazon_search_keywords. Returns: List. rows[]: keyword, volume (monthly Amazon searches; null = no data). Cost: 5 + 5 per 100 keywords. 10 keywords = 6 credits. Cached 7 days. Example: {"keywords": ["standing desk", "desk converter"]}
    ConnectorAPI key
  • Use this when the user asks about GitHub for one of their WebTwizz sites: whether it is linked to a repository, if GitHub has changes the site does not, the last push, recent commits and open pull requests. When nothing is linked yet it says how to connect, and lists their repositories once GitHub is connected.
    ConnectorOAuth
  • Only when the customer explicitly asks to undo an add or stop leads. Target lead IDs, one batchId from add_leads, or target=companies with employer names: those go on the workspace do-not-contact list (shown in get_workspace), every Play stops finding people there, no lead at those employers is ever added again, and everyone already queued there is removed. Uncontacted leads leave the queue; contacted leads keep history and get no further automated steps. Sent invitations and messages cannot be reversed. Returns removal IDs for undo_remove_leads. Removed people stay out of Play review and ordinary imports until explicitly restored.
    Connector
    Destructive
    OAuth
  • Only when the customer explicitly asks to undo an add or stop leads. Target lead IDs, one batchId from add_leads, or target=companies with employer names: those go on the workspace do-not-contact list (shown in get_workspace), every Play stops finding people there, no lead at those employers is ever added again, and everyone already queued there is removed. Uncontacted leads leave the queue; contacted leads keep history and get no further automated steps. Sent invitations and messages cannot be reversed. Returns removal IDs for undo_remove_leads. Removed people stay out of Play review and ordinary imports until explicitly restored.
    Connector
    Destructive
    OAuth
  • Start a paid job billed to the user's Desearch balance: find people on X, YouTube, LinkedIn, or TikTok who match a plain-language description. Returns a task_id at once, with the task's status and reserved_cost_usd. Cost: the call reserves count times the platform's per-person price at the time of the call (reserved_cost_usd; prices at https://desearch.ai/pricing). When the search ends you pay only for the people it delivered (final_cost_usd; a per-search minimum applies when it finds anyone; a search that finds no one is free) and the rest of the reservation is returned. Data: each person comes back with a fit score, why they matched, their audience, and only the contacts and links they list publicly. Desearch reads public data only. X: public posts and public profile fields (bio, followers, website, location). YouTube: public channel pages (About section, subscribers, country, links) and the creator's own website for publicly listed contact details. LinkedIn: public posts and public profiles (headline, company, location, followers, about). TikTok: public videos and public profiles (bio, followers, likes, latest videos, a public email listed in the bio). People found stay readable for 30 days after the search ends. The search runs in the background, usually for 1 to 5 minutes: poll people-search-status with the task_id to read progress and the people found so far, and use people-search-pause, people-search-resume, or people-search-cancel to pause, resume, or cancel it. Do not start the same search twice; send idempotency_key so a retry returns the first task instead of charging again. Filters depend on the platform. x: min_followers, max_followers, verified_only, countries, keywords, exclude_keywords. youtube: min_subscribers, max_subscribers, countries, require_contact, keywords, exclude_keywords. linkedin: min_followers, max_followers, countries, keywords, exclude_keywords. tiktok: min_followers, max_followers, require_contact, keywords, exclude_keywords.
    ConnectorNo auth
  • Your People Search tasks, newest first, with status, counts, cost, why each ended search stopped (completion_reason, coverage_limited), and the metadata labels set on people-search. Free; it lists your own tasks, not the people they found (read those with people-search-status or people-profiles). Use it to find a task_id (filter by metadata to find the searches of one campaign), or to see which searches are still queued, running, or paused: a new search is refused while too many are active.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Run the role's own search and save everyone it finds to the role. A role with a search plan (search_plan in get_role: the role's mix, tools and 3-6 searches read from its brief) runs every search in it: repos about the work, repos using the tools, profiles that say the job, and the tools' own maintainers (kept apart as builders). Each search is answered from AyHire's own index of people first and searched live on GitHub only where the index is thin or older than a month. Each person comes with why_found, source (index or GitHub just now) and a relevance (area fit, the brief's similarity, quality, feedback). Older roles run one search: people behind the top repos matching its words and language. role. People the role has already seen are left out, so each round brings new people (include_seen to bring them back); page 2 and on read the next repos. Returns everyone found with name, company, location, GitHub 'hireable' flag, followers, the matching repos they build and how much. To choose people yourself instead, use the search tools with role_id (search_people, find_people_behind_repos, search_commits) and add_people_to_role. Nothing is scored yet: call score_role_person for the people worth a closer look. Free (GitHub only). Pass query/language to search differently this time. For rounds that learn from your feedback (decide with reasons) and keep the plan's required constraints, use next_round.
    ConnectorAPI key
  • Get remediation advice for a single finding as GitHub-flavored markdown. When AI Assist is enabled and within budget this is a suggestion written for this exact finding; otherwise it falls back to the static guidance-library text and says so in 'source'. Unlike the other reads this one can spend AI budget, which is why it is a separate tool. Use this for advice on one finding; for the whole library use list_security_guidance. Requires project context.
    ConnectorAPI key
  • Stop a finding (a warning on a run, by its key from get_run) from counting on this monitor: it stays on the run, marked ignored, but no longer alerts or fails later runs. Undo with unignore_finding. Only do this when the user says the finding is expected.
    Connector
    Destructive
    No auth
  • Stop a finding (a warning on a run, by its key from get_run) from counting on this monitor: it stays on the run, marked ignored, but no longer alerts or fails later runs. Undo with unignore_finding. Only do this when the user says the finding is expected.
    Connector
    Destructive
    No auth
  • Safety-check a skill before installing it. Pass a skill slug from search_skills, or any public GitHub URL (a repository, or a folder or SKILL.md inside one). Returns clear, review or flagged per skill folder, with the file, line and matched text for every finding. Skills not in the directory are fetched and scanned live.
    ConnectorNo auth
  • Resume a paused People Search task and return its updated status. Free. The search continues from where it stopped, keeping the people already found, with no new charge: the cost already spent is carried forward and the original reservation still covers it. Works only on a paused search, within 7 days of pausing; a search in any other state, including one the API cancelled after 7 days paused, returns 409. Poll people-search-status for the new people.
    ConnectorNo auth
  • Run the next round of a role's plan: it reads on from where the last round stopped, keeps every required constraint, applies what the feedback changed (round.changes: e.g. a search paused after people it found were the wrong stack) and saves only people the role has not seen. When nothing new comes back, round.exhausted is true and nobody already seen fills the list: suggest a wider search from broaden (suggestions only; approve one with set_search_plan). Pass the same request_id to retry: it returns the same round instead of searching again. Free (GitHub and AyHire's index); nothing is scored: call score_role_person for the people worth it. Needs a plan (create_role makes one).
    ConnectorAPI key
  • List the GitHub repositories that blobpedia has INDEXED for Celestia, with item counts. Read-only view of the Celestia index on this server — does NOT browse your GitHub account or arbitrary repos (use a dedicated GitHub tool for that). Zero arguments.
    ConnectorNo auth
  • Register an immutable LeanSolver finding against the currently tracked goal contract. subjectRefs must be goal-scoped refs of kind goal, criterion, or assumption. Returns the server-generated finding id to pass later as addressesFindingId; rejects stale contract tracking.
    ConnectorNo auth
  • LinkedIn posts matching a keyword, ranked by LinkedIn's own search. Use when: "what is being said about X on LinkedIn", finding the people posting about a category. Not for: one company's posts, use linkedin_get_company_posts. Finding people to contact, use leads_search_people. Returns: List, ranked. rows[]: posts with author and author_followers, created_at, text (cut at 2000 characters), likes, comments, shares, saves, views, media, duration_s, links, transcript and top_comments[]. top_comments are up to 10 commenters per post with their profile URLs, so one page names the people engaging with a topic; transcript is what a video post says. media is video only for a video stream; a photo, a document carousel or a GIF reads image. null or empty = the platform does not publish it. created_at is approximate: the platform shows an age such as "3 weeks ago", so it is exact only to that unit. Cost: 1 credit per page. Cached 6 hours. Example: {"query": "rfp automation", "since": "week"}
    ConnectorAPI key
  • Read-only list of open GitHub issues that carry a bounty label, read from public GitHub data every hour, with what matters before starting one: how many open pull requests, claiming people and assignees are already on it, whether it already carries a rewarded label, what reward a label or the title states, and how many issues of that repository carry a rewarded label, which is the only public sign that it pays. Sorted with the least crowded first. Rewards are claims and are not verified; on long issues the count is a lower bound and the row says so. Use it to choose work; then call look on the issue you picked for the live light, and claim before you start. Changes nothing.
    ConnectorNo auth
  • Use this when the user asks who to contact at a company, for the decision makers there, or for a role at a company ("who runs quality at X"). The people Whimbrel's full company research names at one company, by role: R&D and engineering, quality, regulatory, clinical, supply chain and sourcing, operations and manufacturing, executive, business. Each with title, source, date, a LinkedIn people search, and any published email or phone; work emails are looked up for the top names when none is on record. Also returns the company's published contact routes. With no record on file, this does not start one on its own: it lists the names government records give (SBIR award contacts, people on registry records, ClinicalTrials.gov contacts) and asks first. Pass start_new_record true only after the rep says yes. A record older than a week is shown as stored, with an offer to refresh. Each call is one lookup; a new company record uses one of the plan's records for the month and takes about 5 minutes.
    ConnectorOAuth
  • Use this when the user asks who to contact at a company, for the decision makers there, or for a role at a company ("who runs quality at X"). The people Whimbrel's full company research names at one company, by role: R&D and engineering, quality, regulatory, clinical, supply chain and sourcing, operations and manufacturing, executive, business. Each with title, source, date, a LinkedIn people search, and any published email or phone; work emails are looked up for the top names when none is on record. Also returns the company's published contact routes. With no record on file, this does not start one on its own: it lists the names government records give (SBIR award contacts, people on registry records, ClinicalTrials.gov contacts) and asks first. Pass start_new_record true only after the rep says yes. A record older than a week is shown as stored, with an offer to refresh. Each call is one lookup; a new company record uses one of the plan's records for the month and takes about 5 minutes.
    ConnectorAPI key
  • Use this when the user wants their WebTwizz site's code on GitHub. Commits and pushes the saved site to its repository; each call with new changes adds another commit. Other git work, like undoing a push, goes to edit-site. The first time, pass repo (an existing repository from get-github-status) or create_repo (a name for a new private repository).
    Connector
    Destructive
    OAuth