feat: add KindleSMS server to registry

[lexerAnn]

Add configuration for KindleSMS SMS platform with details on transports, package, and environment variables.

Motivation and Context

How Has This Been Tested?

Breaking Changes

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 Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[github-actions]

Hi @lexerAnn 👋 — thanks for your interest in the MCP Registry!

It looks like this PR is trying to publish an MCP server by adding or editing server files in this repository (under servers/, data/servers/, or in data/seed.json). That isn't how servers get published, so I'm closing this PR automatically.

Servers are published with the mcp-publisher CLI, not by opening a pull request against this repo. The CLI verifies that you own your namespace and submits your server.json directly to the live registry API.

To publish your server, follow the Publishing Quickstart. In short:

# Build the publisher CLI
make publisher

# Authenticate (e.g. via GitHub) and publish your server.json
./bin/mcp-publisher login github
./bin/mcp-publisher publish

Note: data/seed.json is seed data for local development only — adding entries there does not publish anything to the registry.

If you believe this was closed in error, please leave a comment and a maintainer will take a look. 🙇

This is an automated message.