Nickthelegend Test Mcp
Smoke-test Smithery remote MCP wiring and tool calls with a trivial greeting server before you depend on production integrations.
Overview
ai.smithery/nickthelegend-test-mcp is a Build-phase MCP server that returns personalized greetings so you can verify Smithery remote MCP setup in your coding agent.
What is this MCP server?
- Generates friendly personalized greetings from agent-driven tool calls
- Optional Pirate Mode for alternate response tone during demos
- Hosted streamable-http remote on Smithery (version 1.15.0 in catalog metadata)
- Bearer {smithery_api_key} header for Smithery authentication
- Useful canary to confirm MCP client config before heavier scrapers or databases
- Catalog server schema version 1.15.0
- Single Smithery streamable-http remote endpoint
- Requires Bearer smithery_api_key via Authorization header
What problem does it solve?
You are not sure whether your agent’s Smithery Bearer auth and streamable-http remote are configured correctly until something simple succeeds end to end.
Who is it for?
Indie builders doing their first Smithery remote install who want a harmless tool surface to validate MCP before production APIs.
Skip if: Teams that need real web scraping, database ops, or any production workflow—this is a demo handshake, not a product feature.
What do I get? / Deliverables
After registration, your agent can call greeting tools reliably, so you can add serious MCP integrations without guessing whether the plumbing was broken.
- Confirmed MCP tool calls returning greeting text from the remote server
- Validated Authorization header pattern reused for other Smithery catalog servers
- Optional Pirate Mode responses for demo or regression checks
Recommended MCP Servers
Journey fit
MCP servers are installed while you wire Claude Code, Cursor, or Codex to external tools during product and agent setup. A minimal demo server belongs on the agent-tooling shelf because its job is validating auth, transport, and tool schemas—not shipping user-facing features.
How it compares
Smithery demo MCP server, not a research scraper or Supabase admin integration.
Common Questions / FAQ
Who is ai.smithery/nickthelegend-test-mcp for?
Solo and indie builders using Claude Code, Cursor, Codex, or Windsurf who need a trivial MCP server to confirm Smithery authentication and tool invocation work.
When should I use ai.smithery/nickthelegend-test-mcp?
Use it immediately after adding your first Smithery remote MCP entry, or whenever MCP tools stop responding and you want to isolate client config from API-key issues on heavier servers.
How do I add ai.smithery/nickthelegend-test-mcp to my agent?
Register the Smithery remote URL https://server.smithery.ai/@nickthelegend/test-mcp/mcp with streamable-http and set the Authorization header to Bearer plus your smithery_api_key, then enable the server in your agent’s MCP settings.