mcp-server-tester
LocalAbout mcp-server-tester
A Node.js web project for checking whether an MCP server is reachable through its Smithery Registry installation code. It provides a backend API and frontend, with the API returning server details or an error.
Key features
- 01Check server availability by installation code
- 02Query the Smithery Registry
- 03Return server data or connection errors
- 04Backend and frontend setup
Use cases
- 01Verify an MCP server's registry availability
- 02Retrieve registry details for a server
- 03Build a simple MCP server-checking interface
MCP support
The API checks MCP server availability by querying the Smithery Registry with a supplied installationCode; it does not itself expose an MCP server interface.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEProject Setup Guide
This guide will walk you through the process of setting up both the backend and frontend for the project.
Step 1: Setting up the Backend
-
Navigate to the
backenddirectory.cd backend -
Install the required dependencies by running the following command:
npm install -
Create a
.envfile in thebackendfolder and add the following environment variables:PORT=5000 FRONTEND_URL=http://localhost:5173 -
To run the server, use the following command:
npm run devThe server will now be running at
http://localhost:5000.
Step 2: Setting up the Frontend
-
Navigate to the
frontenddirectory.cd frontend -
Install the required dependencies by running:
npm install -
Create a
.envfile in thefrontendfolder and add the following environment variable:VITE_BACKEND_URL=http://localhost:5000 -
To run the client, use the following command:
npm run devThe client will now be running at
http://localhost:5173.
Additional Information
- Ensure that both the backend and frontend are running simultaneously.
- You can test the full application by visiting
http://localhost:5173in your browser after both the backend and frontend servers are up and running.
MCP Server Check API
This is a simple Node.js Express endpoint that checks the availability of an MCP server by querying the https://registry.smithery.ai/servers/{installationCode} endpoint using the installationCode provided in the request body. The server responds with either a success message and server data or an error message if the connection fails.
Endpoint
POST /test-server
Request Body
{
"installationCode": "your-installation-code"
}
Response
{
"success": true,
"message": "MCP Server is reachable",
"data": {
"qualifiedName": "server-qualified-name",
"displayName": "Server Display Name",
"deploymentUrl": "https://deployment-url.com",
"connections": [
{
"type": "http",
"url": "https://connection-url.com",
"configSchema": {}
}
]
}
}
For more information
For more detailed information, visit the Smithery Registry Documentation.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.