Add Mink Viking Experience to Community Servers

[mink-prog]

Summary

Adds the Mink Viking Experience MCP server to the Community Servers section. First public MCP server built by an Icelandic tour operator and (as far as I can find) the first traditional tourism business in the list — most existing entries are dev tools, data services, or infrastructure.

Server details

• Endpoint: https://mink.is/wp-json/mink-mcp/v1/mcp
• Manifest: https://mink.is/.well-known/mcp
• Transport: Streamable HTTP
• Protocol version: 2025-11-25 (with backcompat for 2025-06-18 and 2025-03-26)
• Authentication: OAuth 2.1 with RFC 7591 Dynamic Client Registration — optional, not required. Unauthenticated access works identically.
• Publisher: Mink Viking Experience / Serfraedingur.is
• Implementation: PHP WordPress mu-plugin (managed hosting on Rocket.net + Cloudflare Enterprise)

Capabilities

• 5 tools: check_availability, find_next_available, get_pricing, get_business_info, get_booking_url — all annotated with readOnlyHint: true
• 4 resources: mink://summary (full knowledge base), mink://faq/en (82 FAQ in English), mink://faq/is (82 FAQ in Icelandic), mink://terms
• 1 prompt: plan_reykjavik_day — templated workflow for AI agents planning a Reykjavik day that includes a Mink session
• 7 currencies with live WCML exchange rates: EUR, USD, GBP, CAD, AUD, CNY, ISK (pre-computed totals — no LLM arithmetic)
• Rate limited 60 req/min per IP

Why it belongs in Community Servers

Most current Community Servers are developer tools (Git, databases, filesystems, observability). A small-business tourism use case diversifies the catalog and demonstrates MCP working as a real-world consumer-facing integration surface. The architecture is reproducible — any WooCommerce-based operator can adapt the same pattern (full writeup at https://mink.is/from-email-to-ai-native/).

Verification

Anyone can verify the server with one curl, no auth needed:

curl -X POST https://mink.is/wp-json/mink-mcp/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
  | jq '.result.tools | map(.name)'
# → ["check_availability","find_next_available","get_pricing","get_business_info","get_booking_url"]

Live availability for a specific date in any supported currency:

curl -X POST https://mink.is/wp-json/mink-mcp/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"check_availability","arguments":{"date":"2026-04-14","participants":2,"currency":"USD"}}}' \
  | jq .

OAuth 2.1 / DCR (optional)

For clients that require authentication (ChatGPT Apps, Claude Connectors Directory, enterprise platforms), the server implements:

• RFC 8414 Authorization Server Metadata at /.well-known/oauth-authorization-server
• RFC 9728 Protected Resource Metadata at /.well-known/oauth-protected-resource
• RFC 7591 Dynamic Client Registration at /wp-json/mink-mcp/v1/register
• OAuth 2.1 Authorization Code + PKCE S256 flow
• client_credentials grant
• RFC 7009 Token Revocation

Unauthenticated MCP access continues to work unchanged, so Claude Desktop / Cursor / Cline users can connect with no setup.

Contact

• Server contact: mcp@serfraedingur.is
• Architecture writeup and "why we built this": https://mink.is/from-email-to-ai-native/

[olaservo]

Thanks for contributing to the MCP servers repo!

We've retired the third-party server list from the README in favor of the MCP Registry — see #3950 for context. The Official Integrations and Community Servers sections no longer exist in the README, so this PR no longer has a target.

Going forward, please publish your server to the MCP Registry using the quickstart guide:
https://github.com/modelcontextprotocol/registry/blob/main/docs/modelcontextprotocol-io/quickstart.mdx

That's where server discovery now happens. Thanks for building on MCP!

---

Note: I'm working through the backlog with help from Claude Code to give everyone a prompt response.