Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GitHub Repo Change Intelligence

REMOTE · S-GITHUB.PIXHARVEST.COM · 2 COMPONENTS

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

−58 this week 0 Trust /100

Last scanned (35 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 9 Oct 2026.

Category Version Control

Trust breakdown (7 categories)

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (2)

  • HTTPS
  • Transport

Checks we could not complete (9)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • DNSSEC in Endpoint SecurityDNSSEC not yet verified: we couldn't validate it against a resolver.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 17 Oct 26 −12

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 16 Oct 26 −11

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 15 Oct 26 −12

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 14 Oct 26 −11

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 13 Oct 26 −12

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 10 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: 0.27 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HTTPS: unverified → pass ▲ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 9 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 17 Oct 2026 · Probed https://s-github.pixharvest.com/mcp

TLS unreached
DNSSEC inconclusive

Validation of s-github.pixharvest.com. — Inconclusive

Zone DS Keys Algorithms Outcome
s-github.pixharvest.com. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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 Unreachable
http (plaintext) http://s-github.pixharvest.com/mcp HTTPS enforced
MCP tools · 5 exposed · ~382 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
targetsarrayyes–

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.

NameTypeReqDescription
targetstringyes–

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.

NameTypeReqDescription
targetstringyes–

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.

NameTypeReqDescription
targetsarrayyes–

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.

NameTypeReqDescription
targetstringyes–

No output schema declared.

No examples provided.

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.

remote · s-github.pixharvest.com

# add to Claude Code
claude mcp add --transport http contentforge-press-github-intel 'https://s-github.pixharvest.com/mcp'
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 0 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?

Its publisher declares no required credentials for GitHub Repo Change Intelligence. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the GitHub Repo Change Intelligence MCP server still maintained?

GitHub Repo Change Intelligence has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 9 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the GitHub Repo Change Intelligence MCP server?

VerifyMCP ran 2 checks on GitHub Repo Change Intelligence, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about GitHub Repo Change Intelligence: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.