MCP Server Development

Server Requirements

To be listed in Tairon's directory, MCP servers must meet these requirements:

Core Requirements

MCP v1.0+ Support

  • Implement all required MCP endpoints

  • Follow protocol specifications

  • Provide proper error handling


Documented API

  • Complete API documentation

  • Function descriptions and examples

  • Parameter and return type definitions


Security Audit Preferred

  • Optional but recommended security review

  • Vulnerability assessments

  • Best practices compliance


Open Source or Verifiable Builds

  • Public source code repository, OR

  • Verifiable build artifacts

  • Reproducible deployments


MCP Endpoint Reference

GET /health – Health Check

Basic status check used to confirm that a server is operational.

Method: GET URL: https://your-server.com/health

Response Example:

  • status: Should return ok if the server is operational

  • uptime: Time (in seconds) the server has been up

  • timestamp: ISO 8601 timestamp of the check


GET /capabilities – Function Discovery

Returns a list of callable functions exposed by the MCP server.

Method: GET URL: https://your-server.com/capabilities

Response Example:

  • name: Function identifier to be used with /execute

  • description: Human-readable explanation of function

  • inputs: List of expected input keys

  • outputs: List of output keys


POST /execute – Function Execution

Main execution endpoint for calling any available function listed in /capabilities.

Method: POST URL: https://your-server.com/execute Headers:

Request Example:

Response Example:

  • function: Must match a name returned by /capabilities

  • input: Object with named parameters expected by the function

  • output: Object with named result keys as defined by the server


Development Templates

Node.js Template

Python Template


Testing Your Server

Before submitting to Tairon, test your server locally:

Last updated