MCP server that helps developers find open-source issues worth contributing to — semantic issue search, repo health scoring, and downstream impact ranking.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"oss-contribution-advisor-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# OSS Contribution Advisor — MCP Server An MCP server that helps developers find open-source issues genuinely worth contributing to — not just issues tagged "good first issue," but ones that match their interests, come from a healthy/responsive repo, and have real downstream impact. ## Why this exists Existing "find your first OSS issue" tools filter by label only. This server answers three questions a label can't: 1. **Does this match what I actually want to work on?** — semantic search over open issues (local sentence-embeddings), not keyword/label matching. 2. **Is this repo actually a good place to spend my time?** — health score based on maintainer responsiveness and first-time-contributor merge rate. 3. **Does this repo matter?** — ranks by *real* downstream reach via [libraries.io](https://libraries.io)'s dependents graph (how many other packages depend on this one) — not just GitHub stars. ## Tools | Tool | Purpose | |---|---| | `match_issues_semantically` | Free-text interest → ranked list of matching open issues, using local sentence-embeddings. | | `score_repo_fit` | Given a repo, scores maintainer responsiveness, PR merge rate, doc completeness, and recent activity into a 0-100 fit score. | | `find_impact_multiplier_repos` | Ranks a given repo shortlist — or self-searches by language if none given — by real downstream dependents (libraries.io), falling back to a stars/forks proxy if unconfigured. | ## Caching design Two genuinely different cache policies, because the underlying data has two different change patterns — using one TTL for everything would either waste API calls (too short) or serve stale data (too long): | Cache | Key | Lifetime | Why | |---|---|---|---| | **Search results** (`match_issues_semantically`) | GitHub search query string | 20 min TTL | Open issues genuinely change often, but repeated calls in a short window shouldn't re-hit the API. | | **Issue embeddings** (`match_issues_semantically`) | `(issue_id, update…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.