Surfacing MCP server

Which servers in the official MCP registry are Surfacing's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Surfacing

Whose server it is

Registry namecom.surfacingapp/feelingsverified in the MCP registry

The registry name sits under surfacingapp.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14

Stateanswerschecked 2026-10-14
Tools4
Server calls itselfsurfacing-feelings
Server version1.0.3
Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 67 ms.

Tools it offers4 tools · read 2026-10-14

list_categories
Lists every category in the Surfacing feelings list (796 curated feeling words), with example words, plus every body region for physical sensations. Relevant when someone is trying to name or understand what they feel, for example "I feel…
get_feeling_words
Returns every word in one category of the Surfacing feelings list, such as "Sadness", "Fear & Anxiety", "Contempt & Malice", or "Calm & Grounded". Relevant when someone wants a more precise word for a feeling.
get_body_sensations
Returns the physical sensations people report in one body region of the Surfacing body map, such as "Heart & Chest", "Stomach", or "Face & Expression". Relevant when someone describes a feeling through their body, for example "my chest is…
search_words
Searches all 796 feeling words and 243 body sensations in the Surfacing list for a word or fragment and returns each match with its category or body region. Relevant when someone uses a vague or partial word for how they feel, such as…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "feelings": {
      "type": "http",
      "url": "https://surfacing-mcp.knightcorrick.workers.dev/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.