GitHub Repo Change Intelligence
REMOTE · S-GITHUB.PIXHARVEST.COM · 2 COMPONENTS · SCANNED OCT 2
Track public GitHub repos: free snapshot, paid release, star & issue intel via x402 USDC.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 400, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 382 tokens (~76/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · s-github.pixharvest.com
claude mcp add --transport http contentforge-press-github-intel 'https://s-github.pixharvest.com/mcp'
{
"mcpServers": {
"contentforge-press-github-intel": {
"url": "https://s-github.pixharvest.com/mcp"
}
}
} {
"servers": {
"contentforge-press-github-intel": {
"type": "http",
"url": "https://s-github.pixharvest.com/mcp"
}
}
} [mcp_servers.contentforge-press-github-intel] url = "https://s-github.pixharvest.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"contentforge-press-github-intel": {
"type": "remote",
"url": "https://s-github.pixharvest.com/mcp",
"enabled": true
}
}
} openclaw mcp add contentforge-press-github-intel --url 'https://s-github.pixharvest.com/mcp' --transport streamable-http
mcp_servers:
contentforge-press-github-intel:
url: "https://s-github.pixharvest.com/mcp" {
"McpServers": {
"contentforge-press-github-intel": {
"Transport": "http",
"Url": "https://s-github.pixharvest.com/mcp"
}
}
} assistant mcp add contentforge-press-github-intel -t streamable-http -u 'https://s-github.pixharvest.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 2 Oct 2026 · Probed https://s-github.pixharvest.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pixharvest.com | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 82fc403ab81b2837134eb910c19b4401 |
| SANs: pixharvest.com, s-github.pixharvest.com, *.s-github.pixharvest.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of s-github.pixharvest.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pixharvest.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://s-github.pixharvest.com/mcp | Verified | 200 | |
| http (plaintext) | http://s-github.pixharvest.com/mcp | Inconclusive | 400 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
repo_batch_scan ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| targets | array | yes | – |
No output schema declared.
No examples provided.
repo_changes ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | – |
No output schema declared.
No examples provided.
repo_intel_report ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | – |
No output schema declared.
No examples provided.
repo_landscape ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| targets | array | yes | – |
No output schema declared.
No examples provided.
repo_snapshot ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | – |
No output schema declared.
No examples provided.
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.