reapx GitHub repos - repository metadata and activity

dev.reapxPublished by reapx.devv1.0.0Updated Oct 24, 2026

Scrape GitHub repository metadata, stars, forks, topics, licences and activity. Pay per row.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that lets an assistant scrape GitHub repository metadata, stars, forks, topics, licences and activity, billed per row.

What you can do
Retrieve GitHub repository metadata such as stars, forks, topics and licences for repositories the assistant is asked about. Pull repository activity data alongside that metadata. Results are billed per row through the Apify platform. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Use it when you want an assistant to look up GitHub repository details and activity without building your own scraping setup, and per-row billing suits your usage.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com. Authentication is required via an OAuth flow and an Authorization header carrying your own Apify API token as a Bearer token; a free token is available from the Apify console. Network access to the endpoint is needed.
Before you install
The Authorization header carries your Apify API token, a secret that should not be shared. Usage is billed per row, so costs grow with the volume of data retrieved; a prepaid, spend-capped token option is mentioned. Requests go to a third-party hosted service.

Installation

In SourceWeft

  1. Open reapx GitHub repos - repository metadata and activity 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/dev.reapx%2Fgithub-repos/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": {
    "reapx-github-repos-repository-metadata-a": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=reapx/github-repo-scraper"
    }
  }
}

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.0LatestSep 16, 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.