GitHub Repo Change Intelligence

io.github.contentforge-pressPublished by GitHub account contentforge-pressv1.0.1Updated Oct 27, 2026

Track public GitHub repos: free snapshot, paid release, star & issue intel via x402 USDC.

The publisher's own server: Tariff Data

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Tracks public GitHub repositories, offering a free snapshot plus paid release, star and issue intelligence paid in USDC via x402.

What you can do
  • Take a free snapshot of a public GitHub repository.
  • Get release intelligence for tracked repositories.
  • Get star and issue intelligence for tracked repositories.
  • Access paid intelligence tiers settled in USDC through x402.
When to use it
Useful when an assistant needs to monitor or summarize activity in public GitHub repositories, such as releases, star growth or issue trends, and when the user is willing to pay per request in USDC for the deeper tiers.
Requirements
A remote endpoint at the given host, or the npm package run locally with Node.js. No authentication, environment variables or headers are declared. Paid features require a USDC-capable x402 payment setup.
Before you install
The deeper release, star and issue intelligence is paid in USDC via x402, so requests can spend real money; confirm pricing and spending limits before enabling it. Only public repositories are described as covered. No credentials are declared, but payment authorization is effectively a financial credential.

Installation

In SourceWeft

  1. Open GitHub Repo Change Intelligence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.contentforge-press%2Fgithub-intel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "github-repo-change-intelligence": {
      "type": "http",
      "url": "https://s-github.pixharvest.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.1LatestOct 1, 2026
  2. v1.0.0Oct 1, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Pixharvest integrations