Local MCP server/Version Control

GitHub Repo Change Intelligence MCP server

Local MCP server

GitHub Repo Change Intelligence tracks releases, stars, issues, and pushes for any public GitHub repository, aimed at dependency and open-source monitoring. Anonymous calls cover a free snapshot. Paid tool calls require x402 USDC settlement or a monthly access key passed as ?key=. The README documents the local npm package github-repo-change-intelligence and a hosted endpoint at s-github.pixharvest.com/mcp; that host did not resolve when checked on 2026-11-16, so use the local package until the hosted service is confirmed.

Anonymous free tools; paid tools via x402 USDC or a ?key= access key Source checked Nov 12, 2026 Local install path Reviewed 2026-11-16
About

Where it fits

Maintainers and security teams monitoring public GitHub dependencies for release and activity changes.

  • Check recent releases for a dependency repository.
  • Monitor stars, issues, and pushes over time.
  • Start with the free snapshot before configuring paid access.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

The README documents this npm package. Anonymous calls cover the free snapshot; paid tool calls need an x402 USDC settlement or a monthly access key in the URL as ?key=. The README's hosted host, s-github.pixharvest.com, did not resolve when checked on 2026-11-16.

npx -y github-repo-change-intelligence

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

GitHub Repo Change Intelligence repositoryhttps://github.com/contentforge-press/github-repo-change-intelligence