"Top 20 most starred MCP servers on GitHub" matching MCP tools:

• findagent_connect_githubA

  FindAgentA

  Start connecting GitHub for the CALLER'S OWN FindAgent account so findagent_import_repo / findagent_list_repos can pull their repos. Returns whether GitHub is already connected plus a browser connect URL — the caller opens it, authorizes GitHub, and the token is stored server-side (this tool grants nothing itself; the actual connect happens in the browser). Call this first if import_repo or list_repos reports github not connected. The connection is scoped to THIS FindAgent account, so authorize on the same browser account. To switch GitHub accounts, use findagent_disconnect_github first.

  ConnectorOAuth

• muninn_mirror_designateA

  Muninn by BizatA

  Designate (or un-designate) a bundle for mirroring to a provider. Adds/removes the 'gdrive-mirror' tag on the bundle root's backing memory for Drive ('github-mirror' for GitHub). After designating, writes to that bundle automatically enqueue a mirror push. Use muninn_mirror_push to force one now. Turning mirroring on is Paid plan; turning it off (enabled=false) is always free. GitHub is not available yet: enabling it is refused, un-designating still works.

  ConnectorAPI key

• muninn_mirror_designateA

  Muninn (munn.is)A

  Designate (or un-designate) a bundle for mirroring to a provider. Adds/removes the 'gdrive-mirror' tag on the bundle root's backing memory for Drive ('github-mirror' for GitHub). After designating, writes to that bundle automatically enqueue a mirror push. Use muninn_mirror_push to force one now. Turning mirroring on is Paid plan; turning it off (enabled=false) is always free. GitHub is not available yet: enabling it is refused, un-designating still works.

  ConnectorAPI key

• add_to_collectionA

  Lion ReaderA

  Add articles to a collection (find its ID with list_subscriptions, or make one with create_collection). Any article the user can see works, feed entry or saved article; it stays in its own feed too, sharing read and starred state. A collection holds at most 10000 articles. Returns the IDs newly added; IDs already present or not visible are skipped. Fails with a not-found error if the collection isn't the user's. To order the collection, use set_collection_positions.

  ConnectorOAuth

• list_past_bookingsA

  Rudko — vertebrologist (Chernivtsi, Ukraine)A

  The user's past appointments (booking_id, date, time, status), most recent first. limit (default 20) and offset for pagination. Cancelled ones are ALSO shown — by the status field. Requires authorization.

  ConnectorNo auth

• top_attackers_toolA

  HoneyLabsA

  Ranked leaderboard over a time window: the top source addresses, networks, countries, destination ports, user agents, JA4 fingerprints, URL paths, reverse DNS domains or CVEs by event count. Use for "who is attacking the most", "top countries hitting port 22", "most targeted ports this week", "top networks by volume", and with by='cve' for "which CVEs are being scanned for right now". Do not use it for one known address (use ioc_lookup_tool), one known network (use asn_enrich_tool), one known CVE (use cve_lookup_tool), or a trend over time (use attack_timeline_tool). by: ip, asn, country, port, user_agent, ja4, url_path, domain or cve (default ip). limit is 1 to 100, default 20. Optional filters country (ISO code), dest_port and asn ('AS12345'); add one when the window is long, because an unfiltered ranking over many days can hit the query memory limit. by='cve' takes no filters and returns value (the CVE id), title, severity, actively_exploited (on the CISA KEV catalogue), kev_date_added and counts. since and until are ISO-8601 UTC, within the plan's query window.

  ConnectorNo auth

• user_activityA

  convalyticsA

  Composite snapshot of a specific user's activity on a project. Returns an identity block (visitorId, userEmail, userName, firstSeen, lastSeen), total pageviews, total custom events, session count, top pages this user visited, their most-fired event names, and their 20 most recent events with props. Use this for 'how is dancleary54@gmail.com using my app?' style questions — one call, full picture. For ad-hoc drill-down (just a count, just recent events) pass `user` to the individual tools instead. Default window is the last 7 days.

  ConnectorNo auth

• search_gmail_messagesA

  YouSpotB

  Search the user's connected Gmail mailboxes and return matching messages, newest first: from, to, subject, date, and a short snippet of the body. `query` uses Gmail search syntax: 'in:sent to:jane@acme.com' for messages the user sent to someone, 'from:jane@acme.com' for messages they received, plus operators like subject:, newer_than:7d, and has:attachment. So 'show me the last 5 messages I sent to jane@acme.com' is query 'in:sent to:jane@acme.com' with max_results 5. Each result carries a `starred` flag; a message the user starred matters to them, so weight it accordingly; 'is:starred' finds starred mail directly. For 'how many' questions, use total_matches_estimate in the result (it is Gmail's estimate of ALL matches, beyond the messages returned). If it reports no Gmail account connected, give the user the link it returns. Rare header-only connections cannot run query search; the tool says so. Answer correspondence questions from the brain for those.

  ConnectorNo auth

• get_digestsA

  remoetA

  HISTORICAL ONLY: the user's archived job digests, the email summaries Remoet used to send about new jobs from their starred companies. No new digest has been generated since 2026-07-06, when the feed roundup replaced that pipeline, so this returns nothing at all for an account created since then. What carries new roles now is get_feed (the composed dashboard stream, and what the roundup emails are built from); for searching, use get_starred_jobs or search_jobs. Reach for this tool only when the user asks about their old email summaries by name. Without an id: the 20 most recent as lightweight summaries (id, title, frequency, jobCount, createdAt). With an id: that digest's full markdown body (each job's title, application URL, salary, remote policy, experience level, tech stack).

  ConnectorNo auth

• get_digestsA

  remoet-mcpA

  HISTORICAL ONLY: the user's archived job digests, the email summaries Remoet used to send about new jobs from their starred companies. No new digest has been generated since 2026-07-06, when the feed roundup replaced that pipeline, so this returns nothing at all for an account created since then. What carries new roles now is get_feed (the composed dashboard stream, and what the roundup emails are built from); for searching, use get_starred_jobs or search_jobs. Reach for this tool only when the user asks about their old email summaries by name. Without an id: the 20 most recent as lightweight summaries (id, title, frequency, jobCount, createdAt). With an id: that digest's full markdown body (each job's title, application URL, salary, remote policy, experience level, tech stack).

  ConnectorOAuth

• trending_reposA

  whichlibA

  Discover projects: the most-starred GitHub repositories created in the last day, week or month, or with period "rising" repositories of any age that gained the most stars this week (like GitHub Trending; risingRank keeps that order). Optionally one language; each scored and returned sorted by score (starsRank keeps the stars order). Each result has a 0-100 score (momentum 40% (stars gained per week; without history, lifetime stars per week scaled by the npm/PyPI download trend), maintenance 25%, adoption incl. npm/PyPI weekly downloads 25%, license 10%), a tier (Strong >=75, Solid >=50, Watch >=25, Avoid <25; New for repos under 30 days old, too new to judge), a one-line verdict and the full breakdown. Not the right tool for picking a dependency, since new repositories have little maintenance history; use recommend_repos for that. One GitHub search (rising: one download of the daily list from raw.githubusercontent.com instead), plus one npm/PyPI lookup per repository when withDownloads is true. Hosted: 50 free tool calls per day per user; send header X-GitHub-Token with your own GitHub token for unlimited use, or run the npm package locally (npx -y whichlib).

  ConnectorNo auth

• dash_address_receivedA

  Bitquery: Crypto & Blockchain DataA

  INCOMING Dash (dash, DASH, mainnet) outputs for an address — every coin received (tx, amount, output type: payment (change is not detected on Dash), time), most recent first. Indexed by address (fast). Use to see what a DASH address received and in which transactions. NOT what this address spent → use dash_sent_from_address. NOT sums over its whole history → use dash_address_flow_summary or dash_address_profile. An address can receive several coins (outputs) in one transaction, each its own row. Returns up to limit rows (default 20, at most 1000), newest first; page back with the last row's Cursor - a page shorter than limit is the last one. Set sort='amount' for the largest receipts instead: a top-N page with no Cursor. NOTE: shows receiving events, not the sender addresses (a UTXO output has no single sender) — pass a Tx to dash_tx_flow to see the addresses that funded it, or call dash_address_flow_summary for the top senders. A small share of outputs is missing from this list (a few whole blocks a month, under 0.1 % on busy addresses, a few % in some months of 2023), so it can hold a few rows fewer than dash_address_profile counts; dash_tx_flow on the transaction is complete. Each row: Time, Tx, Type, Amount_DASH, Cursor.

  ConnectorOAuth

• doge_address_receivedA

  Bitquery: Crypto & Blockchain DataA

  INCOMING Dogecoin (doge, DOGE, mainnet) outputs for an address — every coin received (tx, amount, output type: payment/change, time), most recent first. Indexed by address (fast). Use to see what a DOGE address received and in which transactions. NOT what this address spent → use doge_sent_from_address. NOT sums over its whole history → use doge_address_flow_summary or doge_address_profile. An address can receive several coins (outputs) in one transaction, each its own row. Returns up to limit rows (default 20, at most 1000), newest first; page back with the last row's Cursor - a page shorter than limit is the last one. Set sort='amount' for the largest receipts instead: a top-N page with no Cursor. NOTE: shows receiving events, not the sender addresses (a UTXO output has no single sender) — pass a Tx to doge_tx_flow to see the addresses that funded it, or call doge_address_flow_summary for the top senders. A small share of outputs is missing from this list (a few whole blocks a month, under 0.1 % on busy addresses, a few % in some months of 2023), so it can hold a few rows fewer than doge_address_profile counts; doge_tx_flow on the transaction is complete. Each row: Time, Tx, Type, Amount_DOGE, Cursor.

  ConnectorOAuth

• ltc_address_receivedA

  Bitquery: Crypto & Blockchain DataA

  INCOMING Litecoin (ltc, LTC, mainnet) outputs for an address — every coin received (tx, amount, output type: payment/change, time), most recent first. Indexed by address (fast). Use to see what a LTC address received and in which transactions. NOT what this address spent → use ltc_sent_from_address. NOT sums over its whole history → use ltc_address_flow_summary or ltc_address_profile. An address can receive several coins (outputs) in one transaction, each its own row. Returns up to limit rows (default 20, at most 1000), newest first; page back with the last row's Cursor - a page shorter than limit is the last one. Set sort='amount' for the largest receipts instead: a top-N page with no Cursor. NOTE: shows receiving events, not the sender addresses (a UTXO output has no single sender) — pass a Tx to ltc_tx_flow to see the addresses that funded it, or call ltc_address_flow_summary for the top senders. A small share of outputs is missing from this list (a few whole blocks a month, under 0.1 % on busy addresses, a few % in some months of 2023), so it can hold a few rows fewer than ltc_address_profile counts; ltc_tx_flow on the transaction is complete. Each row: Time, Tx, Type, Amount_LTC, Cursor.

  ConnectorOAuth

• arena_list_matchesA

  Dead Brands Bot ArenaA

  List matches. WHEN: find live/recent/mine match ids (then arena_get_state / arena_get_replay). Differs from arena_leaderboard (scores) and arena_presence_list (who is online). List matches. Public: live = up to 20 active matches updated in the last 10 minutes, recent = the 20 most recently finished. Each row: id, handle, kind (house|team|outsider), game, difficulty, tick, score, status, tournament_id, created_at, updated_at (ms), duration_ms (updated_at-created_at), finished_at (ms, finished rows only). With your key and mine:true you also get mine = your last 20 matches, and live/recent are filtered to you. Use the id with arena_get_state (your own matches) or watch it on the TV pages. Example: {}

  ConnectorNo auth

• top_animeA

  KitsuA

  Kitsu anime and manga database — the highest-ranked anime on Kitsu, ordered by popularityRank (default) or ratingRank, up to 20 entries. Each entry returns the Kitsu anime id, titles, both rank positions, average rating, episode count and synopsis. Answers which anime are most popular or highest rated according to Kitsu.

  ConnectorNo auth

• analyze_github_userA

  AyHireA

  For someone in a role, use score_role_person instead (it also judges them against the role's criteria). Score a GitHub user's public work on 4 general dimensions (technical_depth, shipping_velocity, communication, gem_score; 0-10 each, total out of 40) with findings (what their work shows) and red flags, each with the GitHub links it rests on (claims without a source are dropped), and top skills. The analysis reads their own repos and their work on other people's projects (`outside_work`: commits and PRs by repo, last year). The scores are general: none is judged against a role, and where someone lives is never used. Returns a saved result if the user was analyzed in the last 30 days (free, cached=true); otherwise scrapes, scores and saves (takes 15-25s). Also returns `activity`: their GitHub contribution calendar for the last year, summarized (total, active weeks, streaks, busiest month, last active; null when GitHub has none). Set refresh=true only when the user asks for a fresh analysis.

  ConnectorAPI key

• get_person_evidenceA

  AyHireA

  Everything a recruiter would click through on GitHub to judge someone, in one call, each item with its link: profile and profile README, their repos (code, prose such as playbooks and lists, or forks) with descriptions, how they worked on their top repos (commits, active days, how many made with an AI coding agent), their work on other people's projects from the contribution graph (last year), pull requests they opened to other repos (grouped, merged counts, titles), orgs, activity month by month, and, with role_id, the repos the role's search found them through and their history there. Read live from GitHub, free, about 5 s. Use it to check a claim or judge fit yourself; `unknown` lists what GitHub could not show this time (unknown is not a weakness). Compact by default (own repos only, forks counted; shorter lists); detail: 'full' for everything. Whole READMEs: read_readme. All PRs or commits: list_pull_requests, list_commits.

  ConnectorAPI key

• youtube_videoCommentsA

  TrueScrapeB

  Video comments. Top-level comments on a video, about 20 per page. Pass `pagination.cursor` back as `cursor` for the next page. Each item that has replies also appears in `replyCursors`; feed that cursor to `/v1/youtube/video/comment-replies`. Use `order=newest` when polling for new comments, since `top` is re-ranked by YouTube and will churn. Costs 1 credit.

  ConnectorNo auth

• batch_modify_labelsA

  gmailA

  Add and/or remove the same labels on many email messages at once in a single Gmail API call (wraps users.messages.batchModify). Use this for bulk operations such as marking multiple specific emails as read (remove ['UNREAD']), archiving (remove ['INBOX']), or starring (add ['STARRED']). Use list_labels to find label IDs (Gmail requires IDs, not names). Common system label IDs: INBOX, STARRED, IMPORTANT, UNREAD, SPAM, TRASH. Provide 1-1000 email IDs and at least one of `add` or `remove`. The same label changes are applied to every listed message. Gmail returns no per-message status, so a successful call means Gmail accepted the request; an invalid email ID or label ID typically causes Gmail to reject it.

  ConnectorOAuth

• get_leaderboardsA

  Agent Zero — ERC-8004 Trust FilterA

  Top ERC-8004 agents by live capability, plus the most recently indexed. Three ranked lists — top by live MCP tool count, top by OpenAPI method count, and most-recently indexed — each with agent_id, chain, public name, a shareable detail URL, and the relevant count. Names and counts only: no owner wallets, handles, or endpoint URLs. Use this to find the most capable / most active agents to integrate or watch. Paid counterpart: `GET /v1/intel/trending` (x402, USDC on base-mainnet) returns trending intel — top earners, fastest-rising agents, and integration candidates ranked with the signals behind the ranking. Every response from this free tool carries an `unlock` block with the exact paid endpoint, price, and payment discovery.

  ConnectorNo auth