Smithery · Mcp
GitHub is a code hosting platform for version control and collaboration, offering Git-based repository management, issue tracking, and continuous integration features
POST https://github.run.tools
The MCP remote exists, but its handshake currently requires credentials the public probe does not have.
MCP remote requires authentication before initialize completes.
Preview-before-commit metadata describes what this route declares before an agent pays or starts work.
Evidence-quality metadata describes how verifiable and composable this route's post-run outputs are for downstream agents and orchestration.
Matched 2 corroborating registry views across 2 services under the same public identity host and service name.
Smithery · MCP
GithubAccess the GitHub API, enabling file operations, repository management, search functionality, and more.
POST https://github--smithery-ai.run.tools
Endpoint health is mixed: some probe evidence is strong, but active risks still need attention.
Service health is mixed: the endpoints are partially proven, but there are still active operational gaps.
Hourly score snapshots are appended whenever the derived health layer recomputes.
No observed or documented price signal is available yet.
No observed challenge price history has been recorded yet for this endpoint.
Build 2 provider telemetry for this specific route. This is the endpoint-level slice for conversion, revenue, latency, and recent paid/challenge activity.
No endpoint hourly telemetry has been rolled up yet.
No endpoint intent telemetry yet.
No recent endpoint events have been recorded yet.
1/1 monitored step(s) are live but currently require credentials, so public proof is incomplete.
The latest normalized challenge data is stored here, including the new Solana-aware fields.
No documented session lifecycle has been synced for this endpoint yet.
No challenge snapshots have been captured yet.
No extra notes recorded.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The workflow is documented, but no monitored runtime step has been verified yet.
The workflow is documented, but no monitored runtime step has been verified yet.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The workflow is documented, but no monitored runtime step has been verified yet.
No service-level monitoring incidents are currently open.
Availability · 1 occurrence(s)