Skip to main content
ToolDix logoToolDixFind, compare, and use tools
Sign In

Curated, evidence-linked composition

GitHub maintainer

Combine capability discovery with GitHub repository workflows.

CodexClaudeCursorOpenClaw

Intended use case

Issue triage, pull-request review, and repository maintenance.

Data flow

This is the intended logical flow. Actual data access depends on each component configuration and permission boundary.

  1. 1Repository request → MCP client
  2. 2Bearer token from local environment → GitHub endpoint
  3. 3GitHub response → agent context
  4. 4Approved mutation → GitHub API

Linked capability trust cards

Open every component before copying configuration. A stack is only as safe as its broadest permission and weakest trust boundary.

MCP server

ToolDix Read-only MCP

ToolDix / com.tooldix · 2026-07-15

Search and compare ToolDix capability metadata through a read-only MCP endpoint.

Publisher/source identity checked No listed warning
Checks
Recorded checks passed
Evidence
1 source
CodexClaudeCursorOpenClaw
Review trust card

MCP server

GitHub MCP Server

GitHub / io.github.github · remote-2026-07-15

Connect an agent to GitHub repositories, issues, pull requests, and code workflows.

Metadata reviewed Elevated access
Checks
Metadata only
Evidence
1 source
CodexClaudeCursorOpenClaw
Review trust card

Alternatives

  • MCP server

    Context7 MCP

    Retrieve current library documentation and code examples from Context7.