GitHub Dev Tools

io.github.firstnameapk-designPublished by GitHub account firstnameapk-designv1.0.1Updated Oct 30, 2026

GitHub security scanning, code audit, and workflow automation for repositories.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint offering GitHub security scanning, code audit and workflow automation for repositories.

What you can do
  • Scan GitHub repositories for security issues.
  • Audit code and review repository contents.
  • Automate GitHub workflows.
  • No tool list is published, so the exact operations are not documented.
When to use it
Worth considering when you want an assistant to check repositories for security problems, review code, or drive GitHub workflow automation without building that integration yourself.
Requirements
A remote streamable HTTP endpoint; nothing to install locally. No authentication, environment variables or headers are declared, and no account or API key setup is documented.
Before you install
The endpoint is a temporary-looking Cloudflare tunnel host, which is unusual for a production service and may change or disappear. No authentication is declared, so it is unclear how repository access is authorized or whose credentials are used. It may read private repository code and perform workflow actions; verify the operator before connecting.

Installation

In SourceWeft

  1. Open GitHub Dev Tools in the dashboard and add it to a workspace.
  2. 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.firstnameapk-design%2Fgithub-dev-tools/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.

{
  "mcpServers": {
    "github-dev-tools": {
      "type": "http",
      "url": "https://maiden-bonus-specifics-precipitation.trycloudflare.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestOct 30, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.