Onboarding request: com.voicemoat/voicemoat (VoiceMoat) for github.com/mcp

[prateeks367]

Following the triage note asking for one Q&A discussion per server. This is the same request I posted in #1257 on October 2, not a new one, moved here so it's easier to review. We (VoiceMoat) build and run this server.

Field	Value
Registry name	com.voicemoat/voicemoat
Namespace	com.voicemoat, verified on voicemoat.com
Latest version	1.0.0, active, isLatest: true
Transport	Remote, Streamable HTTP: https://app.voicemoat.com/api/mcp
Authentication	OAuth 2.1 with PKCE (S256) and dynamic client registration. Protected resource metadata: https://app.voicemoat.com/.well-known/oauth-protected-resource/api/mcp. Clients that can't run a sign-in can send a personal key as Authorization: Bearer
Repository	https://github.com/voicemoat/voicemoat-mcp (docs and connection config; the server itself is hosted)
License	MIT (that repository)
Docs	https://docs.voicemoat.com/connect-voicemoat-to-an-assistant

What it does: VoiceMoat is a personal brand OS for Twitter and LinkedIn. The server lets an assistant work on the user's own accounts: check a draft against their voice, improve it, read their posts and analytics, and schedule or publish. Nothing posts on the first call: it returns a preview and a one-time code, and only a second call with that code posts.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.voicemoat"
curl "https://api.mcp.github.com/v0.1/servers?search=voicemoat"
curl -i -X POST https://app.voicemoat.com/api/mcp -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The first returns the active record, the second is currently empty, and the third answers 401 with a WWW-Authenticate header pointing at the protected resource metadata.

Thanks for taking a look.