Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Stock Ticker MCP Server search for Apple stock price"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A simple MCP server that responds with a rude message when queried about stocks. This is a demo implementation of the Model Context Protocol (MCP).
Single tool: search_stock that returns a rude message
Compatible with Claude Desktop
Related MCP server: finance-mcp
To install Stock Ticker Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @LoSinCos/stock-ticker-mcp --client claude# Create and activate virtual environment
python -m venv .venv
source .venv/bin/activate
# Install dependencies
uv pip install -r requirements.txtAdd the server configuration to your Claude Desktop config:
{
"mcpServers": {
"stock_ticker_server": {
"command": "uv",
"args": ["--directory", "/path/to/stock-ticker-mcp", "run", "server.py"]
}
}
}Restart Claude Desktop
Look for the hammer icon to access the tool
This tool is meant to search stocks but just returns a practical joke. Args: stock_ticker: a stock ticker symbol that will be ignored Example payload: "AAPL"
Returns: str: A practical joke Example Response: "haha jokes on your, no stock ticker for you"
| Name | Required | Description | Default |
|---|---|---|---|
| stock_ticker | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully discloses that the parameter is ignored and the return is a joke, providing complete behavioral transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description includes an example and essential information, but could be more concise without losing clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simple nature, the description is reasonably complete, covering behavior, parameter, and example output. No output schema exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, but the description adds that 'stock_ticker' will be ignored, which is critical context beyond the schema definition.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool returns a practical joke, not real stock data. It is clear in its intent, though it does not differentiate from potential sibling tools as none are provided.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for when a joke is desired, but does not explicitly state when to use or avoid it, nor mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0search_stockScored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool has a clear name and description, though its functionality is a joke.
With a single tool, naming is trivially consistent. The name 'search_stock' follows a clear verb_noun pattern.
A single tool that does not perform its advertised function is extremely inappropriate for a stock ticker server. The server should have multiple tools for searching, retrieving, and managing stock data.
The server has a severe gap: it provides no actual stock data functionality. The only tool returns a joke, making the surface completely incomplete for any real use.
Model Context Protocol server for Studex tools, notifications, and profile integrations
MCP server for querying Forkast documentation
