Add Serenn: search verified field service technicians via MCP

[DATOZAMIR]

Description

Add Serenn MCP server — a tool for searching verified field service technicians (appliance repair, HVAC, plumbing) by location, trade, brand, and appliance type. The server wraps the public GET https://serenn.ai/api/ai/search endpoint. No API key required.

npm: [serenn-mcp-server](https://www.npmjs.com/package/serenn-mcp-server)
Source: [github.com/Serenn-AI/serenn/tree/main/packages/mcp-server](https://github.com/Serenn-AI/serenn/tree/main/packages/mcp-server)

Publishing Your Server

Note: We are no longer accepting PRs to add servers to the README. Instead, please publish your server to the [MCP Server Registry](https://github.com/modelcontextprotocol/registry) to make it discoverable to the MCP ecosystem.
To publish your server, follow the [quickstart guide](https://github.com/modelcontextprotocol/registry/blob/main/docs/modelcontextprotocol-io/quickstart.mdx). You can browse published servers at https://registry.modelcontextprotocol.io/.

Published to npm as serenn-mcp-server. Will publish to the MCP Registry via mcp-publisher as well.

Server Details

• Server: serenn (new community server)
• Changes to: Adds one tool (search_technicians) and one resource (llms.txt)

Motivation and Context

There's no MCP server for finding local service technicians. When users ask Claude "find someone to fix my Samsung fridge in Austin," there's no tool to call. This server connects Claude to Serenn's directory of photo-verified field service professionals across the US, returning verified job history, specialties, common repairs, and company contact info.

How Has This Been Tested?

• Tested with Claude Desktop via stdio transport
• Scenarios tested: search by location only, location + trade, location + trade + brand + type, invalid location (error handling), API timeout handling
• Verified JSON response parsing and error messages

Breaking Changes

None. New server — no existing configurations affected.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the [MCP Protocol Documentation](https://modelcontextprotocol.io)
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

The server is read-only (no mutations, no auth required). It's a thin stdio wrapper around a public REST API. The tool includes readOnlyHint: true safety annotation. Install: npx -y serenn-mcp-server.