# Surfacing Feelings (remote · surfacing-mcp.knightcorrick.workers.dev)

Helps people name what they feel: 796 feeling words and a body map of 243 sensations.

- Trust score: 82/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `surfacing-mcp.knightcorrick.workers.dev`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-surfacingapp-feelings/surfacing-mcp.md), [page](https://verifymcp.io/servers/com-surfacingapp-feelings/surfacing-mcp)

## Channel facts

- Endpoint: `https://surfacing-mcp.knightcorrick.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 517 tokens (~129/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Surfacing Feelings MCP server?

Surfacing Feelings is a hosted endpoint at https://surfacing-mcp.knightcorrick.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-surfacingapp-feelings 'https://surfacing-mcp.knightcorrick.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-surfacingapp-feelings": {
      "url": "https://surfacing-mcp.knightcorrick.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-surfacingapp-feelings": {
      "type": "http",
      "url": "https://surfacing-mcp.knightcorrick.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-surfacingapp-feelings]
url = "https://surfacing-mcp.knightcorrick.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-surfacingapp-feelings": {
      "type": "remote",
      "url": "https://surfacing-mcp.knightcorrick.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-surfacingapp-feelings --url 'https://surfacing-mcp.knightcorrick.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-surfacingapp-feelings:
    url: "https://surfacing-mcp.knightcorrick.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-surfacingapp-feelings": {
      "Transport": "http",
      "Url": "https://surfacing-mcp.knightcorrick.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-surfacingapp-feelings -t streamable-http -u 'https://surfacing-mcp.knightcorrick.workers.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `list_categories` (~62 tokens)

List feeling categories and body regions

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 off" or "I can't describe it".

### `get_feeling_words` (~83 tokens)

Get the feeling words in a category

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.

Input parameters:

- `category` (string, required): Category name, for example "Overwhelmed" or "Relational Hurt".

### `get_body_sensations` (~94 tokens)

Get the physical sensations for a body region

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 tight" or "my jaw is clenched".

Input parameters:

- `region` (string, required): Body region name, for example "Breathing" or "Legs & Feet".

### `search_words` (~99 tokens)

Search feeling words and body sensations

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 "heavy", "tight", "numb", or "off".

Input parameters:

- `limit` (integer): Maximum matches to return (default 40).
- `query` (string, required): A word or part of a word.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-surfacingapp-feelings/surfacing-mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 72
- 2026-10-10: 71
- 2026-10-07: 70
- 2026-10-04: 69
- 2026-10-03: 68
- 2026-10-02: 68

## Common questions

### What is the Surfacing Feelings MCP server?

Surfacing Feelings is an MCP server listed in the public MCP registry as com.surfacingapp/feelings. Helps people name what they feel: 796 feeling words and a body map of 243 sensations. This page covers its hosted endpoint (https://surfacing-mcp.knightcorrick.workers.dev/mcp).

### Is the Surfacing Feelings MCP server safe to use?

Surfacing Feelings scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Surfacing Feelings MCP server expose?

Surfacing Feelings exposes 4 tools: list_categories, get_feeling_words, get_body_sensations, search_words. Their descriptions and schemas cost roughly 338 tokens of context every time the server is loaded.

### Does the Surfacing Feelings MCP server require authentication?

No. We connected to Surfacing Feelings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Surfacing Feelings MCP server still maintained?

Surfacing Feelings is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Surfacing Feelings MCP server?

VerifyMCP ran 12 checks on Surfacing Feelings, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Surfacing Feelings: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://surfacing-mcp.knightcorrick.workers.dev/mcp
- Website: https://surfacingapp.com/feelings.html
- Changelog RSS feed: https://verifymcp.io/servers/com-surfacingapp-feelings/surfacing-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-surfacingapp-feelings/surfacing-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-surfacingapp-feelings/surfacing-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-surfacingapp-feelings/surfacing-mcp