feat(mcp): register loopover_get_contributor_profile as a local stdio MCP tool (#7760)

[andriypolanski]

Summary

• loopover_get_contributor_profile was a remote MCP tool (src/mcp/server.ts) with a contributor-profile CLI mirror (CLI mirror for loopover_get_contributor_profile #6737), but had no local stdio MCP tool registration — so a self-host operator using the local stdio server (not the CLI or remote MCP) could not call it.
• This registers the missing stdio tool, following the exact shape of its login-based sibling loopover_monitor_open_prs, and reuses the same REST endpoint the CLI already calls (no duplicated HTTP logic).

Closes #7760

Change

• Local stdio MCP tool (packages/loopover-mcp/bin/loopover-mcp.ts): registered loopover_get_contributor_profile (loginShape) next to its sibling, with a matching STDIO_TOOL_DESCRIPTORS entry (discovery category). The tool summary is the remote tool's own fixed sentence (server.ts uses the identical string), so the two surfaces never drift; the full API payload rides along as structuredContent.
• Shared call: extracted getContributorProfile(login) as the single source of truth for GET /v1/contributors/:login/profile, and pointed both the new stdio tool and the existing contributorProfileCli at it — the CLI no longer inlines the endpoint path.
• Export: contributorProfileCli is now exported (like maintainCli) so an in-process test can drive it directly; the subprocess CLI harness is not v8-instrumentable, so this is what makes the shared call graded by Codecov.

Tests

• New test/unit/mcp-cli-contributor-profile-inprocess.test.ts: in-process coverage (dynamic import + InMemoryTransport, mirroring mcp-cli-plan-issues.test.ts) — the stdio tool registers and proxies GET .../profile, url-encodes the login, and the exported contributorProfileCli prints the header + API summary (plain) and re-serializes the payload (--json).
• test/unit/mcp-tool-rename-aliases.test.ts: bumped the live stdio-tool count pin 89 → 90 (comment + three assertions).
• The existing subprocess test/unit/mcp-cli-contributor-profile.test.ts is unchanged.

Validation

• git diff --check clean; npm run build:mcp + package build:tsc typecheck clean.
• Targeted vitest suites pass (mcp-cli-contributor-profile-inprocess, mcp-cli-contributor-profile, mcp-tool-rename-aliases, mcp-cli-tools).
• Codecov patch = 100%. packages/loopover-mcp/bin/**/*.ts is in Codecov's scope (not ignored), and its coverage comes only from in-process importers. Verified from coverage-final.json that every changed line is executed (stdio handler, the shared getContributorProfile call from both the tool and the CLI) and that there are zero branches on any changed line — the summary is a fixed string, not a branchy payload.summary ?? … helper, precisely to avoid an uncovered fallback arm.
• No artifact regeneration needed (no REST/OpenAPI/schema/binding/migration changes).

UI Evidence

N/A — local stdio MCP tool + a one-line CLI refactor only; no apps/loopover-ui/** or other visible surface changed.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-21 23:08:17 UTC}

3 files · 1 AI reviewer · no blockers · readiness 82/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This PR registers the missing local stdio MCP tool `loopover_get_contributor_profile`, mirroring the existing `loopover_monitor_open_prs` pattern exactly, and extracts the shared `getContributorProfile(login)` helper so the CLI and new stdio tool hit the same endpoint. The tool count pin bump (90→91) and matching count assertions in mcp-tool-rename-aliases.test.ts are consistent with the diff. The new in-process test exercises the real registered tool via InMemoryTransport and asserts URL-encoding and payload shape, which is solid coverage of the actual code path rather than a fabricated scenario.

Nits — 6 non-blocking

• packages/loopover-mcp/bin/loopover-mcp.ts:2337,4207,6121 use `any` typed handler params (`{login}: any`, options: any, login: any) — consistent with the rest of this file's existing style, but worth tightening if this file is ever migrated off loose typing.
• test/unit/mcp-cli-contributor-profile-inprocess.test.ts:37 sets `process.env.LOOPOVER_API_TOKEN = "in-process-token"`, a placeholder test credential flagged by the secret scanner — confirm it's a dummy value (it clearly is, matching the sibling harness pattern) and not a real leaked token.
• The new stdio tool's description and summary duplicate the remote tool's fixed sentence by convention (per the PR description) rather than importing a shared constant — matches the existing pattern for `loopover_monitor_open_prs` so it's fine, but a future edit to one string won't auto-propagate to the other.
• Consider extracting the repeated remote/stdio tool summary sentence (e.g. `LoopOver contributor profile for ${login}.`) into a shared constant if more tool pairs are added, to prevent silent drift between server.ts and loopover-mcp.ts.
• packages/loopover-mcp/bin/loopover-mcp.ts is now ~6127 lines — no action needed for this PR, but the file is a longstanding candidate for the seam-splitting refactor mentioned in its own top-of-file comment.
• Possible secret-shaped assignment in the diff (generic_secret_assignment) — Verify the value is not a real credential.

Decision drivers

• ✅ Code review — No blockers (1 reviewer)
• ✅ Gate result — Passing (No configured blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ Linked	#7760
Related work	⚠️ 1 scoped overlap	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 184 registered-repo PR(s), 118 merged, 22 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	andriypolanski; Gittensor profile; 184 PR(s), 22 issue(s).
Improvement	✅ Minor	risk: clean · value: minor

Linked issue satisfaction

Addressed
The PR registers loopover_get_contributor_profile as a stdio tool via registerStdioTool mirroring the sibling pattern, adds a STDIO_TOOL_DESCRIPTORS entry with stdioToolDescription lookup, and extracts a shared getContributorProfile helper used by both the new tool and the existing CLI command, avoiding duplicated HTTP logic.

Review context

• Author: andriypolanski
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, JavaScript, Rust, Cuda, Kotlin, MDX, Scala
• Official Gittensor activity: 184 PR(s), 22 issue(s).
• Related work: Titles/paths share 7 meaningful terms. (PR #7957)

Contributor next steps

• Start here: Review top overlaps.
• Then work through the remaining 2 steps in the Signals table above.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 11.75%. Comparing base (fa3581d) to head (e6eb68d).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #7958       +/-   ##
===========================================
- Coverage   89.00%   11.75%   -77.25%     
===========================================
  Files          90        1       -89     
  Lines       21504     2194    -19310     
  Branches     3707      840     -2867     
===========================================
- Hits        19139      258    -18881     
+ Misses       2187     1914      -273     
+ Partials      178       22      -156     

Flag	Coverage Δ
control-plane	?
rees	?
shard-1	0.00% <0.00%> (?)
shard-2	11.75% <100.00%> (?)
shard-3	0.00% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
packages/loopover-mcp/bin/loopover-mcp.ts	11.75% <100.00%> (ø)

... and 90 files with indirect coverage changes