"author:iarsingh" matching MCP servers:

Exposes an HTTP interface that lets clients list the allowlisted MCP tools and invoke them by call, with only pre-approved tools permitted. Tool discovery and invocation are served alongside health checks, and any production apply request is refused.

Enables GitHub-shaped tool calls to list issues, retrieve pull requests, and summarize them, while refusing merge-via-apply operations and remaining a local proof rather than making production changes.

Enables clients to read files, list tests, and run tests through MCP tool calls, while refusing apply operations.

Enables users to inspect databases through read-only tools that explain queries, sample rows, and list indexes, while refusing apply or delete operations.

Enables users to list GKE clusters, describe virtual machines, and retrieve billing information through MCP read tools, without applying production changes.

Exposes a single HTTP endpoint that aggregates tool definitions from GitHub, Kubernetes, and database namespaces, letting clients list available tools and invoke them by name. It provides health-check, tool-discovery, and tool-call routes for local, read-only experimentation without calling hosted models or applying production changes.