# GitHub Repo Change Intelligence (remote · s-github.pixharvest.com)

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

- Trust score: 55/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `s-github.pixharvest.com`: 55/100 (this document), [markdown](https://verifymcp.io/servers/contentforge-press-github-intel/s-github.md), [page](https://verifymcp.io/servers/contentforge-press-github-intel/s-github)
- npm · `github-repo-change-intelligence`: 34/100, [markdown](https://verifymcp.io/servers/contentforge-press-github-intel/github-repo-change-intelligence.md), [page](https://verifymcp.io/servers/contentforge-press-github-intel/github-repo-change-intelligence)

## Channel facts

- Endpoint: `https://s-github.pixharvest.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-02.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 400, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 382 tokens (~76/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the GitHub Repo Change Intelligence MCP server?

GitHub Repo Change Intelligence is a hosted endpoint at https://s-github.pixharvest.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http contentforge-press-github-intel 'https://s-github.pixharvest.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "contentforge-press-github-intel": {
      "url": "https://s-github.pixharvest.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "contentforge-press-github-intel": {
      "type": "http",
      "url": "https://s-github.pixharvest.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.contentforge-press-github-intel]
url = "https://s-github.pixharvest.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "contentforge-press-github-intel": {
      "type": "remote",
      "url": "https://s-github.pixharvest.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add contentforge-press-github-intel --url 'https://s-github.pixharvest.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  contentforge-press-github-intel:
    url: "https://s-github.pixharvest.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "contentforge-press-github-intel": {
      "Transport": "http",
      "Url": "https://s-github.pixharvest.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add contentforge-press-github-intel -t streamable-http -u 'https://s-github.pixharvest.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "contentforge-press-github-intel": {
      "type": "http",
      "url": "https://s-github.pixharvest.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 55, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-01 (score 55)

First indexed and scored.

## MCP tools (5)

### `repo_snapshot` (~71 tokens)

FREE. Current state of a public GitHub repository: stars, forks, open issues, primary language, last push and latest releases. Use for "what is repo X", GitHub project research, open-source due diligence, library/framework health, checking if a project is maintained.

Input parameters:

- `target` (string, required)

### `repo_changes` (~71 tokens)

PAID ($0.05 USDC on Base via x402). Release change detection vs history: new releases, new prereleases, removed releases. Use for "did library X ship a new version", release monitoring, dependency update alerts, tracking when a project publishes/tagges.

Input parameters:

- `target` (string, required)

### `repo_intel_report` (~80 tokens)

PAID ($0.50 USDC on Base via x402). Highest-value repository-intelligence report: project health, popularity (stars/forks), maintenance signals, latest release and executive takeaways. Use for open-source risk assessment, choosing libraries/SDKs, vendor/technology due diligence, competitive developer research.

Input parameters:

- `target` (string, required)

### `repo_batch_scan` (~80 tokens)

PAID ($0.03 USDC per repo via x402, max 50). Track a whole dependency/portfolio set of GitHub repositories in one call: stars, issues, last push and latest release per repo. Use for dependency monitoring, open-source portfolio health, supply-chain maintenance tracking, scanning many projects.

Input parameters:

- `targets` (array, required)

### `repo_landscape` (~80 tokens)

PAID ($5 USDC on Base via x402, up to 10 repos). Strategic repository landscape: ranks related projects by stars and activity, flags abandoned/archived or low-maintenance outliers. Use for comparing libraries/frameworks, picking the best open-source option, technology benchmarking, developer-tool market mapping.

Input parameters:

- `targets` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/contentforge-press-github-intel/s-github#diagnostics

## Score history

- 2026-10-02: 55
- 2026-10-01: 55

## Common questions

### What is the GitHub Repo Change Intelligence MCP server?

GitHub Repo Change Intelligence is an MCP server listed in the public MCP registry as io.github.contentforge-press/github-intel. Track public GitHub repos: free snapshot, paid release, star & issue intel via x402 USDC. This page covers its hosted endpoint (https://s-github.pixharvest.com/mcp).

### Is the GitHub Repo Change Intelligence MCP server safe to use?

GitHub Repo Change Intelligence scores 55 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the GitHub Repo Change Intelligence MCP server expose?

GitHub Repo Change Intelligence exposes 5 tools: repo_snapshot, repo_changes, repo_intel_report, repo_batch_scan, repo_landscape. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.

### Does the GitHub Repo Change Intelligence MCP server require authentication?

No. We connected to GitHub Repo Change Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GitHub Repo Change Intelligence MCP server still maintained?

GitHub Repo Change Intelligence is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://s-github.pixharvest.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/contentforge-press-github-intel/s-github.xml
- Changelog JSON feed: https://verifymcp.io/servers/contentforge-press-github-intel/s-github.json
- HTML version of this page: https://verifymcp.io/servers/contentforge-press-github-intel/s-github