GitHub Repository Metrics — Stars, Forks & Issue Counts

io.github.kriton-devPublished by GitHub account kriton-devv1.0.4Updated Nov 7, 2026

Read numeric metrics for known public GitHub repositories

The publisher's own server: Forks.World

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Remote Apify-hosted MCP server that lets an assistant read numeric metrics such as stars, forks and issue counts for known public GitHub repositories.

What you can do
  • Look up numeric metrics for a known public GitHub repository
  • Retrieve star, fork and issue counts as reported by the Actor
  • Return figures for repositories the user names explicitly
When to use it
Useful when you want quick, read-only popularity and activity numbers for specific public GitHub repositories without browsing GitHub yourself.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: either an Apify API token sent as an Authorization bearer header or OAuth sign-in to Apify. An Apify account is needed because runs are billed to it.
Before you install
Runs are billed to your Apify account at the pay-per-event prices on the Actor's store page, so usage costs money. The Authorization header carries an Apify API token secret that should be kept private. It only covers known public repositories and returns numeric metrics, not repository contents.

Installation

In SourceWeft

  1. Open GitHub Repository Metrics — Stars, Forks & Issue Counts in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.kriton-dev%2Fgithub-repository-metrics/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "github-repository-metrics-stars-forks-is": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=hermeskd/github-repository-metrics"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.4LatestNov 7, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Forks integrations