devnull-mcp
Related Servers
Alternatives to devnull-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA single-user MCP server that exposes your GitHub activity to Claude via three read-only tools: recent commits, open pull requests, and repository summaries. Deployed as a Vercel function using Streamable HTTP.-
- AlicenseNot gradedqualityBmaintenanceLets MCP-compatible clients answer natural-language questions about your GitHub activity, such as counting today's commits across all your repositories via the GitHub REST API.281 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to read and write GitHub repositories, pull requests, issues, files, branches, commits, releases, and more using a personal access token without OAuth.281 npmMIT
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that exposes a personal git repository of markdown notes to Claude, enabling reading, writing, searching, and running scripts with automatic git commits and GitHub OAuth authentication.MIT
- FlicenseNot gradedqualityCmaintenanceEnables GitHub repository operations (list/read files, create branches, commit files, open/list PRs) via an authless remote MCP server that keeps your GitHub token encrypted on Cloudflare, with access limited to allowed repositories.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read and write GitHub text files with verifiable commit-SHA-based reads, chunked UTF-8 access, and atomic multi-file commits through a self-hosted Cloudflare Worker.MIT
TDQS
Scored across 5 tools
Each tool targets a distinct operation and resource: posting (devnull_commit), reading a single commit, listing commits, fetching a user profile, and checking identity (whoami). The write tool versus read tools boundary is clear, and get_commit vs list_commits is unambiguous.
All tools share the devnull_ prefix, which is consistent. The get_/list_ verb_noun pattern is used for three tools, but devnull_commit and devnull_whoami deviate slightly, making it mostly consistent with minor exceptions.
Five tools are well-scoped for a simple social posting service, covering posting, reading, listing, profile, and identity without excess. Each tool earns its place.
The core lifecycle is covered: post, read a commit, list commits, view user profiles, and verify identity. Minor gaps like editing/deleting a commit or browsing followers/following exist, but agents can work around them for the stated purpose.