"A server for accessing or retrieving data from GitHub" matching MCP tools:

• get_release_notesA

  Dev Facts CheckA

  Get release notes. Use this when the user asks what changed between two versions of a package, or what to watch for in an upgrade, such as "what changed in express between 4.18.2 and 5.1.0?" or "are there breaking changes from requests 2.28 to 2.32?". Pass the npm or PyPI package name (or a GitHub repo) and fromVersion, the version the user has; toVersion defaults to the latest release. Returns each release after fromVersion up to toVersion, newest first, with its date, link, a short excerpt of its notes and a breaking flag, plus a GitHub compare link. Notes come from GitHub releases and, when those do not reach back far enough, from the repository's changelog file; complete is false when neither covers the whole range. Not for vulnerabilities.

  ConnectorNo auth

• list_github_discussionsA

  canton-ccpediaA

  List GitHub Discussions from Canton Network and Digital Asset repositories cached by CCPEDIA, sorted by recency (newest first). Filter by repo or category, or call with no filter to see which repos are present. CANTON-ONLY and read from CCPEDIA's cache, NOT the live GitHub API or the user's own repos (use a GitHub MCP for those). This is GitHub Discussions: distinct from the Canton web forum (get_discussion) and the sync.global mailing lists (list_mailing_threads). Use get_github_discussion for full body + comments.

  ConnectorNo auth

• get_cipA

  blobpediaA

  Read the full text of one Celestia Improvement Proposal (CIP) by its id. Celestia governance docs only — not GitHub issues or arbitrary proposals (use a GitHub tool for those). Get the id from search or list_cips first.

  ConnectorNo auth

• get_github_discussionA

  blobpediaA

  Read one Celestia GitHub Discussion (celestiaorg/docs and other Celestia repos) cached on THIS server — full body plus comments — by an id you got from list_github_discussions on this server. Celestia cache only: if the id was not returned by this servers list_github_discussions, or the request is just a raw GitHub node id (e.g. D_kw...) with no Celestia context, this is NOT the tool — use a dedicated GitHub tool for arbitrary GitHub Discussions. This is GitHub Discussions, not the community forum (use get_discussion). Pair it with list_github_discussions, which supplies the valid ids.

  ConnectorNo auth

• wdf_data_templates_listA

  Web Data FormsA

  Lists all automation-enabled Data Templates (Forms) available for the current group. Use this tool first when you need to determine which Data Template (Form) should be used for a user's request, before retrieving its schema or working with submissions.

  ConnectorNo auth

• push-to-githubA

  WebTwizzA

  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

• get_github_discussionA

  canton-ccpediaA

  Get the full body and comments of a single GitHub Discussion from a Canton Network or Digital Asset repo, by its GitHub GraphQL node id (from list_github_discussions). CANTON-ONLY, read from CCPEDIA's cache. Not the live GitHub API. This is GitHub Discussions, distinct from the Canton web forum (get_discussion) and mailing lists (get_mailing_thread).

  ConnectorNo auth

• list_reposA

  blobpediaA

  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

• list_github_discussionsA

  blobpediaA

  List GitHub Discussions from Celestia repos (e.g. celestiaorg/docs) cached on this server, ranked by upvotes then recency. Celestia repos only, from the local cache — not arbitrary GitHub Discussions (use a dedicated GitHub tool for those). Use get_github_discussion for the full body plus comments of one thread; this is GitHub Discussions, not the community forum (use get_discussion).

  ConnectorNo auth

• resort_leaderboardA

  Agent ResortA

  Inspect resort standings to compare an agent's passport status and receive ranked real agents, with demo and test guests returned separately. Provide no input; use after retrieving a passport or whenever comparing resort status.

  ConnectorNo auth

• resort_leaderboardA

  Agent ResortA

  Inspect resort standings to compare an agent's passport status and receive ranked real agents, with demo and test guests returned separately. Provide no input; use after retrieving a passport or whenever comparing resort status.

  ConnectorNo auth

• browse_ticket_integration_importA

  Meta CouncilB

  Read one bounded page of importable items live from a saved GitHub, GitLab or Asana connection. GitHub: open issues, oldest first, 20 per page; page 1 to 50 (GitHub only). GitLab and Asana: the first 20 items only. Not a snapshot or complete inventory. Read-only provider requests; never writes to the provider or creates tickets. Requires integrations:read and tickets:read.

  ConnectorNo auth

• query_contextA

  aictrlA

  Read project context in exactly six domains: code, system (architecture, data model, APIs, roadmap), issues, backlog (epics and tasks), agent skills, and stack layers. Most actions read stored, indexed context such as the knowledge graph. Two reads reach GitHub live: issues/read returns the current GitHub issue and latest comments (issues/context, list and overlap use stored issue context), and code/read can fetch file content from repositories connected to the organization. Use backlog list/get actions to find existing epic and task IDs before calling update_backlog. Read-only: it does not create, change, or delete backlog, workflow, or GitHub data. Not for workflow runs or task executions: use list_workflow_runs to discover runs, get_workflow_run for a known run ID, and get_task_execution for an execution ID returned by start_task.

  ConnectorAPI key

• find_toolsA

  Phở Research ToolsA

  Find research software for a task from the bio.tools registry (ELIXIR), check each tool's licence, verify the paper behind it (DOI, retractions, corrections), label whether it is still maintained, and give the install line. Describe the task (e.g. "cluster single-cell RNA-seq data") and optionally the file format the data is in (e.g. H5AD, FASTQ, VCF); tools that list that format as an input are favoured. Each result has a match level, a plain-language licence verdict, the paper and whether it checks out, a maintenance label (active, idle, stale, archived) read from the linked GitHub repository, and an install line built from a PyPI, Bioconda, Bioconductor, CRAN or GitHub link the registry lists. Every identifier and command comes from the registry's own records; nothing is generated. The `why` field lists the facts behind the match: explain the fit in your own words from those facts, and say plainly when no tool matched. Pass `keywords` with English words when the task is long or not in English. Licence verdicts come from registry and repository metadata and are not legal advice.

  ConnectorNo auth

• repo_health_checkA

  Presend MCP ServerA

  Maintenance signals for a GitHub repository given as owner/name: stars, forks, open issues, license, archived and fork flags, creation date and age, days since last push, topics. Use it to judge whether a dependency looks maintained or abandoned. For an npm or PyPI package whose repository you do not know, supply_chain_check resolves it from registry metadata and includes these signals. GitHub only; missing or private repositories return found: false.

  ConnectorNo auth

• p2pquake.seismic.quake_historyA

  apibaseB

  Search historical JMA earthquake records via the P2PQuake history endpoint. Supports pagination, intensity and magnitude filters, and prefecture filtering for deeper analysis. Returns epicenter name, coordinates, depth, Richter magnitude, max JMA intensity label, domestic tsunami advisory, report type, and observation point count. Use this for trend analysis, seismic risk assessment, or retrieving older events not in the recent feed. Filter examples: min_scale=60 for Shindo 6+ events, min_magnitude=7.0 for major quakes, prefecture=13 for Tokyo area events. Data source: P2PQuake — community-operated JMA relay, open data, no auth required.

  ConnectorNo auth

• repo_health_checkA

  Presend dependency checksA

  Maintenance signals for a GitHub repository given as owner/name: stars, forks, open issues, license, archived and fork flags, creation date and age, days since last push, topics. Use it to judge whether a dependency looks maintained or abandoned. For an npm or PyPI package whose repository you do not know, supply_chain_check resolves it from registry metadata and includes these signals. GitHub only; missing or private repositories return found: false.

  ConnectorNo auth

• google_jobs_jobA

  Crawlora MCPB

  Fetch one Google Careers job posting by the numeric ID returned by google_jobs_search. Use google_jobs_search to discover openings before retrieving a specific posting.

  ConnectorNo auth

• google_jobs_jobA

  Crawlora MCPA

  Fetch one Google Careers job posting by the numeric ID returned by google_jobs_search. Use google_jobs_search to discover openings before retrieving a specific posting.

  ConnectorNo auth

• relay_cassie_seedA

  Cassie HourA

  Prepare a signed, one-hop Cassie Seed relay envelope after explicit recipient consent and proof are supplied. Returns a prepared envelope only; Cassie does not send, post or contact the recipient, and no durable relay record is created. Deliver only to the named consenting recipient. This is distinct from joining or retrieving a seed.

  ConnectorNo auth

• nonprofit_get_filingsA

  nonprofit-explorer-mcp-serverA

  All Form 990 filings for a tax-exempt org by EIN: year-by-year revenue, expenses, assets, liabilities, net assets, revenue breakdown, executive compensation, and source PDF links. Use for trend analysis, due diligence, and accessing primary 990 documents. The filing year (tax_prd_yr) is the fiscal year of the return — data lags 1–2 years; always cite the year. An organization that resolves but has filed no 990 returns an empty filings array with a notice, not an error. Also returns filings_pdf_only — older filings with a PDF but no extracted financial data. Data from ProPublica Nonprofit Explorer, sourced from IRS Form 990 filings.

  ConnectorNo auth