surfacing-feelings
https://surfacing-mcp.knightcorrick.workers.dev
Registry code: aa240e5d7f72bb8a
This server gives you the Surfacing feelings vocabulary: feeling words grouped by category, and physical sensations grouped by body region.
Use it when someone is struggling to name what they feel, or describes a feeling vaguely ("bad", "off", "heavy").
- endpoint
- https://surfacing-mcp.knightcorrick.workers.dev/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is surfacing-feelings live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
- Is surfacing-feelings free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does surfacing-feelings have?
- 4 tools: get_feeling_words, search_words, get_body_sensations, list_categories.
- Is surfacing-feelings safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.5%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- unknown → live
- used for
- find words to name a feeling
- look up body sensations by region
- search feeling vocabulary
- takes → gives
- text → data
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_categories reads open 3h ago
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".
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_feeling_words reads unknown 3h ago
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.
{ "type": "object", "required": [ "category" ], "properties": { "category": { "type": "string", "maxLength": 100, "description": "Category name, for example \"Overwhelmed\" or \"Relational Hurt\"." } }, "additionalProperties": false }arguments 14 linessearch_words reads unknown 18h ago
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".
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Maximum matches to return (default 40)." }, "query": { "type": "string", "maxLength": 100, "minLength": 1, "description": "A word or part of a word." } }, "additionalProperties": false }arguments 21 linesget_body_sensations reads unknown 3h ago
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".
{ "type": "object", "required": [ "region" ], "properties": { "region": { "type": "string", "maxLength": 100, "description": "Body region name, for example \"Breathing\" or \"Legs & Feet\"." } }, "additionalProperties": false }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idaa240e5d7f72bb8a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/aa240e5d7f72bb8a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/aa240e5d7f72bb8a?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.