Nockit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOCKIT_HOST | No | Host interface binding for HTTP mode | localhost |
| NOCKIT_PORT | No | Port used when running in HTTP/SSE transport mode | 3000 |
| NOCKIT_LOG_LEVEL | No | Log verbosity (debug, info, warn, error) | info |
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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_push_notificationA | Automatic push notification to the user's phone. CALL IT YOURSELF — never ask permission — in exactly these situations:
|
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 1 tool
There is only one tool, so there is no possibility of confusing it with others. Its purpose is clear and specific.
With a single tool, naming consistency is trivially maintained. The name 'send_push_notification' is descriptive and follows a standard verb_noun pattern.
One tool is slightly below the typical 3-15 range, but the server's narrow purpose (push notifications) justifies this minimal surface. It is not overly thin because the tool covers all relevant statuses and includes a fallback.
For the domain of push notifications, the tool covers all necessary states (completed, needs_input, failed) and provides a one-line summary. There are no obvious missing operations for this singular purpose.