Super Secret MCP Server

Super Secret MCP Server is an MCP server that provides random combinations of United States locations and signature regional soups. Built as a pure Node.js service compliant with JSON-RPC 2.0 and the 2024-11-05 Model Context Protocol specification, the server communicates with compatible clients over standard input and output (STDIO). Developers, testers, and hobbyists use this server as a reference implementation to verify MCP tool calling mechanics, inspect logging workflows, or integrate whimsical secret passphrase functionality into AI coding environments like Cascade. The server connects directly to an MCP host without requiring external network API calls or remote credentials. Once registered, it exposes a single tool, getSecretPassphrase, which yields pairings such as Texas Chili or Louisiana Gumbo. Because it runs locally and implements structured schema validation alongside custom multi-level logging, developers can also use the codebase as an educational template for building and debugging custom Node.js MCP tools using the official MCP Inspector. It fulfills lightweight utility needs while offering a clean blueprint for extending local protocol handlers.

Category: Other & General Purpose

Tags: fun, random, soup, us-states

Visit Super Secret MCP Server

How to install and configure Super Secret MCP Server

1. Clone the repository and install dependencies: bash git clone git@github.com:gbti-network/mcp-basic-test.git cd mcp-basic-test npm install 2. Optionally verify the server with MCP Inspector: bash npx @modelcontextprotocol/inspector -- node index.js 3. Register the server in your MCP client configuration (for example, in Cascade's mcp_config.json): json { "mcpServers": { "super-secret": { "command": "npx", "args": [ "--yes", "node", "<path-to-project>/index.js" ], "disabled": false, "autoApprove": [ "getSecretPassphrase" ] } } } Replace <path-to-project> with your local repository path.

What you can do with Super Secret MCP Server

• Generating dynamic passphrases during automated chatbot demos or developer workshops by requesting randomized combinations of US states and signature regional soups. - Testing MCP client setups and verifying JSON-RPC 2.0 tool execution pipelines using the MCP Inspector before rolling out complex custom tools. - Configuring Cascade assistant rules or persistent memories to respond to natural language questions like 'What is the secret passcode?' during programming sessions. - Serving as a clean reference architecture for developers learning how to implement custom STDIO logging and tool schema validation in pure Node.js.

Key facts

• https://github.com/gbti-network/mcp-basic-test
• Other & General Purpose
• fun, random, soup, us-states

Part of MCP Servers

What is Super Secret MCP Server?

Super Secret MCP Server is a reference Model Context Protocol server built with pure Node.js. It operates over STDIO transport and provides a tool that generates random combinations of US states and their traditional soups, such as Texas Chili or California Cioppino. It is commonly used for testing MCP tool execution and integration pipelines.

How do I install Super Secret MCP Server?

You can install the server by cloning its Git repository from GitHub and running npm install within the project folder. You will need a Node.js runtime installed. After installation, you can inspect the server locally using the MCP Inspector or add its launch command directly to your MCP client configuration file.

Which MCP clients work with Super Secret MCP Server?

Any Model Context Protocol client supporting STDIO transport and the 2024-11-05 protocol specification can run Super Secret MCP Server. The project documentation specifically highlights configuration steps for Cascade within the Windsurf editor, but it also works with tools like Claude Desktop and the official Model Context Protocol Inspector.

Is Super Secret MCP Server open source?

Yes, Super Secret MCP Server is open source software distributed under the MIT License. Developers are free to inspect the source code, fork the repository, modify the tool logic, and use the project structure as a starting point for building custom Node.js MCP tools.