AetherTech MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port | 3000 |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| text_analysisC | Analyze text with various operations: basic analysis, word counting, sentiment detection, and keyword extraction. Useful for processing and understanding text content. |
| word_countC | Count words in text with optional whitespace handling. Provides detailed statistics about text content. |
| key_value_storeA | Simple in-memory key-value store for temporary data. Supports get, set, delete, and list operations. Data persists while the server is running. |
| mdns_discoveryB | Discover services on the local network using mDNS/Bonjour. Finds services like HTTP, HTTPS, MCP servers, and other network services. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| system-info | Provides basic system information about the MCP server environment |
| store-keys | List all keys in the key-value store |
TDQS
Scored across 4 tools
Most tools are distinct, but word_count overlaps with text_analysis which already includes word counting. This could lead to confusion about which to use.
All tools use snake_case, but the grammatical structure varies (noun_noun vs abbreviation_noun). No verb_noun pattern, but consistent casing and underscore use.
Four tools is borderline low for a server that covers three unrelated domains (text, storage, network). It feels thin but not extremely so.
Each tool provides basic functionality for its domain, but there are gaps (e.g., no detail resolution for mDNS, redundant word_count tool). Overall surface is shallow.