_ registry / mcp streamable-http · checked 1h ago

feeling-search

https://xiximm.cloud

Registry code: c05414d6ecc0d0d3

api record

感觉检索:把一句口语描述换成准确的感受词,再落到具体的视觉风格。

工具选择:

endpoint
https://xiximm.cloud/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 it live, free and safe measured by this hub
Is feeling-search live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is feeling-search free to use?
Yes — the hub reached it with no key and no payment.
What tools does feeling-search have?
5 tools: word_lookup, word_analyze, style_get, word_list, word_status.
Is feeling-search 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
435ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

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.

  • word_list open 1h ago

    列出全部感受词(带共享度)或视觉风格(带定义与词集规模)。调 analyze 之前先拉一次可避免名字拼错。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "kind": {
          "enum": [
            "words",
            "styles"
          ],
          "type": "string",
          "default": "words",
          "description": "枚举哪一类"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • word_status open 1h ago

    返回词表版本、规模(词/风格/变种/挂靠率)以及是否配置了云端额度。

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • word_lookup unknown never probed

    查一个感受词:落在哪些风格、对立词是什么、常一起出现的词、是否标识词。纯本地查表。

    mcp-tool

    {
      "type": "object",
      "required": [
        "word"
      ],
      "properties": {
        "word": {
          "type": "string",
          "maxLength": 30,
          "minLength": 1,
          "description": "要查的词,如「留白」「枯淡」"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • word_analyze unknown never probed

    把一句中文/英文口语描述解析成感受词与视觉风格。默认纯本地词典(免费、不联网);本地一个词都没命中且允许时,才上云。返回 score 是相对值不是概率,styles[].matched 是可以直接引用给用户看的命中词。

    mcp-tool

    {
      "type": "object",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "要解析的描述,最长 500 字"
        },
        "words": {
          "type": "integer",
          "default": 6,
          "maximum": 12,
          "minimum": 1,
          "description": "返回几个感受词"
        },
        "styles": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 0,
          "description": "返回几个视觉风格"
        },
        "allow_cloud": {
          "type": "boolean",
          "default": false,
          "description": "本地零命中时是否允许上云(远端默认关闭;显式传 true 才会消耗额度)"
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • style_get unknown 1h ago

    按风格 id(或中文名)取一个风格:定义、生成用提示词、感受词、年代地域,以及它对应的图片(thumb 320 / full 960 绝对地址,带 kind/credit/license)。kind=work 是有出处的真作品,synthetic 是 AI 示意,placeholder 是占位图。

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "风格 id(如 synthwave)或中文名(如 合成器波)"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c05414d6ecc0d0d3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c05414d6ecc0d0d3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c05414d6ecc0d0d3/badge.svg)](https://brick.blue/agent/c05414d6ecc0d0d3?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.

_ how we know
card completeness
90%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.