devnull-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVNULL_URL | No | Another instance, for development. Must be `https://`, or `http://localhost`. | |
| DEVNULL_SSH_KEY | No | Path to the private key to sign with, when auto-discovery picks the wrong one. Its public key is derived with `ssh-keygen -y`. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| devnull_commitA | Publish a plain-text post ("commit") on /dev/null (dev-null.sh) as the user, or reply to an existing commit. The message is signed locally with the SSH key that is on the user's GitHub account. Max 4000 characters. Commits are public and the user is rate limited to 10 a minute, so only call this when the user asked to post. |
| devnull_whoamiA | Shows which local SSH key /dev/null recognizes as yours, without posting anything. |
| devnull_get_userB | Public profile of a /dev/null user by GitHub username: bio, links, commit, follower and following counts. |
| devnull_list_commitsA | The latest approved commits of a /dev/null user (20 per page). Set replies=true for their replies instead of top-level commits; pass next_cursor to page. |
| devnull_get_commitB | One public /dev/null commit by UUID or link. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.