Skip to content
Agentmart
Submit a tool

git-into-gsoc

Evidence-based GSoC preparation: organizations, repositories, free beginner issues, proposals.

Connector by anandkaranubc · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 1
Write a review

Install

Works with Claude Code, Codex, VS Code, Claude Desktop, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/anandkaranubc-git-into-gsoc

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Evidence-based GSoC preparation: organizations, repositories, free beginner issues, proposals.

Use cases: version-control, code-review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
14 read · 2 write · 0 delete · 9 not yet classified
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Python package

Tools by what they do 25

Read from the source code; the running server may list different tools.

Read 14 · Look things up without changing anything.

  • gsoc_check_message
  • gsoc_discover_repos
  • gsoc_evaluate_repo
  • gsoc_find_issues
  • gsoc_issue_status
  • gsoc_journey_guide
  • gsoc_org_ideas
  • gsoc_past_projects
  • gsoc_pr_check
  • gsoc_program_info
  • gsoc_proposal_check
  • gsoc_rate_limit
Show 2 more tools
  • gsoc_recommend_path
  • gsoc_search_orgs

Write 2 · Create, change, send or run things.

  • gsoc_draft
  • gsoc_log

Not yet classified 9 · We could not tell from the name and description.

  • gsoc_contribution_evidence
  • gsoc_diagnose
  • gsoc_issue_pointers
  • gsoc_next
  • gsoc_org_details
  • gsoc_org_mentors
  • gsoc_orient_repo
  • gsoc_progress
  • gsoc_proposal_checklist

Network hosts it talks to 1

  • github.com · found in install command

Tools (25)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • gsoc_check_messageCheck a message before sending

    Check a message the contributor wrote, before they post it, against the rules for its kind. kind: intro, question, claim, pr, review-reply, status, or final (the same kinds as gsoc_draft). Reports leftover placeholders, phrases that read as machine-written, and kind-specific problems: a greeting with nothing else, no question, asking to ask, not saying what was tried, a bare "can I work on this", no plan, no linked issue or testing note in a PR description, missing weekly-update questions, missing final-report parts. Each finding cites its source. Never rewrite the message for them; point to …

  • gsoc_contribution_evidenceContribution evidence

    Collect a contributor's real history in an org's repos as proposal evidence. Returns merged/open/closed PRs, issues opened, threads joined, reviews given, paste-ready markdown evidence lines, a standing (none/starting/developing/strong), and honest gaps. org: GSoC org name or GitHub org; or scope with repo="owner/repo". One of them is required.

  • gsoc_diagnoseDiagnose a failed setup or test run

    Name the likely cause of failed setup or test output, with what to try next. text: the failing terminal output (the last 50 to 200 lines are enough). repo: optional owner/repo, to add the runtime versions, services, systems and test command its CI uses. Recognises missing modules, wrong runtime versions, missing compilers or headers, services not running, missing environment variables, missing commands, permissions, network failures, ports in use, lock-file mismatches, memory, and test failures. Each cause quotes the line it matched. Walk the contributor through the steps; do not run commands…

  • gsoc_discover_reposRank an organization's repositories

    Rank a mentoring org's GitHub repositories for a first contribution. org: GSoC org name ("GNU Radio") or GitHub login. Repos named on the org's ideas page, with open good-first-issues, recent pushes, and the preferred `language` rank highest.

  • gsoc_draftMessage draft

    Skeleton for a message the contributor must write themselves: kind is intro, question, claim, pr, review-reply, status, or final. Returns a template with <placeholders>, the fields that must hold the contributor's own observations, and the rules maintainers and the official guide state, each with its source URL. With org, repo, or issue it fills in real context: channels, the project's claim convention (/assign, .take, "do not assign"), sign-off and AI-disclosure requirements, and the issue's availability. Never fill the placeholders with invented observations; ask the contributor for them.

  • gsoc_evaluate_repoRepository health for newcomers

    Will a newcomer's PR land here? Health grade (A-F) with signals and warnings: activity, CONTRIBUTING/CoC/templates, CI, open beginner issues, bot-free merge rate, outside-contributor merge rate, review speed; plus toolchain/dev-container setup hints. `points` gives what each signal earned out of its most, and `capped_by` the rule that held the score down, so you can say where a grade came from. `notes` earn nothing. full_name: owner/repo or a GitHub URL (e.g. sympy/sympy)

  • gsoc_find_issuesBeginner issues that are free

    Find beginner issues that are genuinely free to pick up. org: a GSoC organization's name (its GitHub owners plus organizations whose repositories its ideas page names) or a GitHub login. scope="gsoc" (default) searches only repos owned by GSoC mentoring orgs that use `language`; scope="all" searches all of GitHub. Excludes assigned, PR-linked, and archived-repo issues, then checks the top candidates' timelines for claims ("can I work on this?"), contested threads, and maintainer engagement. Each result has availability + reason + signals.

  • gsoc_issue_pointersIssue code pointers

    Where to start reading the code for one issue, as evidence only (never a fix): files the issue text names (blob links, stack frames, paths, identifiers) resolved against the real tree with a confidence label; GitHub code search hits for unresolved identifiers (needs a token; otherwise ready-made search links); closed issues with the same beginner label and the pull requests that closed them with the files they touched; and the repository's fix norm (median files per fix, how often tests and docs are touched). Use after gsoc_issue_status says the issue is available and before the contributor co…

  • gsoc_issue_statusIs this issue free?

    Check if one issue is free: linked PRs, assignees, claims (with dates), maintainer approval, and caveats. ref: "owner/repo#123", an issue URL, or "owner/repo" + number. A GitLab issue link (gitlab.com, gitlab.gnome.org, ...) gets state, assignees, labels, and merge requests from GitLab's public API; its comments cannot be read, and it says so.

  • gsoc_journey_guideJourney phase guide

    Return journey phase guidance for GSoC contributors. Phases: learn, discover, evaluate, find_issues, contribute, community, proposal, track. Omit phase to get the full overview.

  • gsoc_logWeekly note

    Write the contributor's weekly note (goal, what happened, links, learned, stuck, next step), or list recent notes when every field is empty. Notes stay local; they feed the `gsoc_next` reminder and give the contributor material for proposals and mentor updates. links: comma-separated URLs. Ask the user for their own words; never invent progress.

  • gsoc_nextWhat to do next

    What should the contributor do right now? One call that combines the program phase and upcoming deadlines, their saved progress, a live re-check of every tracked issue (reporting status changes such as available -> claimed), beginner issues created in tracked repos and shortlisted orgs since the last check, the contributor's open pull requests sorted into "needs_you" (conflict, failing check, requested changes, unanswered comment, draft) and "waiting" (when a saved profile has a GitHub username), and an ordered list of concrete next actions, each with the exact command. Use this first when a u…

  • gsoc_org_detailsOrganization profile

    Full profile for one org: ideas page, contributor guide, channels, GitHub orgs, projects per year, and recent accepted project titles. Accepts the full name or a whole word of it ("mailman"); a word that fits several orgs returns their names to choose from, and an unknown name returns close matches in did_you_mean. `statement_on_file` is what the monthly check found the org said about the coming year (also in issue bodies, which the live `gsoc_posts` search misses); give its date.

  • gsoc_org_ideasOrg ideas page

    Read a GSoC org's ideas page into structured project ideas: title, description, size (small/medium/large and hours), difficulty, mentors, skills, expected outcome, links, and a confidence flag; plus any AI-use policy sentences found on the page. Ideas are ranked by `skills` (comma-separated; defaults to the saved profile), `size`, and `difficulty`. `layout` tells you how the page was read: headings, index (umbrella org; sub-pages followed when `follow`), issues (ideas are GitHub issues), unstructured, unreachable, or missing. Empty fields were not on the page. Never paste idea text into a prop…

  • gsoc_org_mentorsOrg mentors from the archive

    Who has mentored a GSoC organization's completed projects in recent archived years, from the official archive: each mentor with years, project count and recent project titles; how many mentors return; the GitHub repositories past projects touched; and the technology tags on past projects. Use it to find who to talk to in the public channel and which repository past work lives in. Names show past mentors, not next year's.

Show 10 more tools
  • gsoc_orient_repoRepository orientation

    Orientation sheet for a repository the contributor has chosen, built from about 16 cached GitHub calls and containing facts and paths only: top-level code map with file counts and purpose guesses, entry points, the test command CI really runs, README / CONTRIBUTING / architecture docs, active committers in the last 90 days and CODEOWNERS, rules before a PR (DCO sign-off, CLA, commit style, pre-commit, PR checklist, AI disclosure) each with evidence, verbatim policy sentences (assignment, AI, PR limits), chat channels, one recently merged small outsider PR as a worked example, and an ordered re…

  • gsoc_past_projectsPast accepted projects

    Search accepted GSoC projects from past years by keyword and/or org. Use to calibrate proposal scope and discover which orgs fund a kind of work. Never suggest copying a past proposal.

  • gsoc_pr_checkCheck a pull request

    Check one pull request against the repository's own rules before review. ref: owner/repo#123 or a pull request URL. Returns pass/warn/fail findings with the evidence for each: merge conflict, failing checks, linked issue (a fail when a workflow closes pull requests without one), description length, the template checklist, AI disclosure when the template asks, commit sign-off when the repository requires DCO, commit style, tests changed alongside code, a changelog entry when one is expected, size, and draft state; plus the branch-rule gates still ahead. Coach the author to fix their own branch…

  • gsoc_program_infoGSoC program status and timeline

    Get GSoC program status, timeline, official links, and anti-spam rules. year: program year; 0 means the configured target year (currently 2027). Dates for a year Google has not published yet are estimates. Always verify on summerofcode.withgoogle.com.

  • gsoc_progressLocal journey progress

    Track local GSoC journey progress. action: summary | complete_phase | shortlist_org | track_repo | track_issue | note phase: required for complete_phase value: org name / owner/repo / issue url / note text depending on action

  • gsoc_proposal_checkCheck a draft proposal

    Check a draft proposal for what organizations reject on. Never rewrites it. Reports pass/warn/fail findings with reasons: required sections (synopsis, deliverables, timeline, about), recommended ones (benefits, contributions, availability, AI statement), links to the author's PRs (verified on GitHub when verify_links is true, flagging PRs authored by someone else when github_username is given), week-by-week timeline detail and buffer, concrete code references, generic AI-sounding phrasing, leftover template placeholders, and length. Pass the org's ideas page as ideas_text to flag passages cop…

  • gsoc_proposal_checklistProposal checklist

    Proposal quality checklist grounded in official GSoC guidance.

  • gsoc_rate_limitGitHub API budget

    Show GitHub API rate limit status. Set GITHUB_TOKEN for higher limits.

  • gsoc_recommend_pathPersonalized starting path

    Personalized starting path: matching orgs with evidence, ideas that fit, starter issues, and a learning path. experience: new, some, or experienced (default: the saved profile, else read from the person's merged pull requests when a GitHub username is known). hours_per_week: hours a week they can give (default: the saved profile). Returns `program` (whether the organizations are confirmed for the target year or only took part last year), `recommended_orgs` (each with fit, evidence naming its source, caveats, skills_to_learn, and `participation` when the org posted that it will or will not tak…

  • gsoc_search_orgsRank mentoring organizations

    Rank GSoC mentoring organizations by fit with a contributor's skills and interests. technologies/topics: comma-separated, in the person's own words ("python,rust", "healthcare", "web dev"); synonyms and common misspellings are understood and `read_as` says when a word was corrected. With no filters at all, the saved profile is used and `matched_on.from_profile` is true; saved experience and hours always apply. year: target program year (default: configured target, 2027). If that year's orgs are not announced yet, the latest official list is used and `catalog.note` says so: say clearly that th…

Signals

Stars
1
Forks
4
Open issues
1
Weekly downloads
2,153
Last commit
Oct 24, 2026 (5 days ago)
Last release
Oct 24, 2026 (5 days ago)
Last package publish
Oct 24, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.anandkaranubc/git-into-gsoc
Version
0.24.7
Auth
No auth
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 25, 2026

More from anandkaranubc

Cite this page

git-into-gsoc MCP server. Agent Mart. https://agentmart.dev/connectors/anandkaranubc-git-into-gsoc (last updated 2026-10-25)