Mcp Server Tester

What is Mcp Server Tester?

Mcp Server Tester is a web application that lets users test the connectivity and functionality of an MCP server by providing its URL or installation code. It is built for developers and integrators who need to quickly verify that an MCP server is reachable and responding as expected.

How to use Mcp Server Tester?

Clone the repository, install dependencies with npm install, start the backend with node server.js (runs on http://localhost:3000), then open index.html in a browser. Alternatively, use the live demo at creative-torte-69268c.netlify.app. Enter a valid MCP server URL (e.g., from Smithery), click “Test MCP Server”, and view the result displayed on the page.

Key features of Mcp Server Tester

• Accepts an MCP server URL or installation code
• Verifies connectivity and fetches a response
• Displays results clearly on the webpage
• Handles errors gracefully
• Deployed on Netlify (frontend) and Render (backend)

Use cases of Mcp Server Tester

• Check if a newly deployed MCP server is reachable before integrating it into an application
• Rapidly test multiple MCP server endpoints to confirm they return expected data
• Debug connectivity issues by seeing error messages from the backend request

FAQ from Mcp Server Tester

What should I do if I see “Cannot GET /”?

Ensure your backend has a / route defined. The backend should return a message like “MCP Server Tester Backend is running!”.

Why does the frontend show “Unexpected token '<'”?

This typically means the backend is down or not responding. Check the Render logs for errors and restart the backend if necessary.

How do I fix a “Failed to fetch” error?

Verify that the backendUrl in script.js points to the correct running backend. For the live app, it should be https://mcp-server-tester-e4xf.onrender.com.

What runtime and dependencies are required?

The backend requires Node.js and Express.js. The frontend uses only HTML, CSS, and JavaScript (no build step). Install dependencies with npm install before starting the backend.

Does this tool store or share the tested MCP server URLs?

The README does not mention any data storage. It sends the URL to the backend, which fetches a response and returns it to the frontend—no permanent storage is implied.