Feeling Search — Art Style Reference & Prompt Encyclopedia

Name: Feeling Search — Art Style Reference & Prompt Encyclopedia
Author: xixi048

by xixi048version 0.2.6i★ –iComputer or cloud

Registry namecloud.xiximm/feeling-search

Install

Overview

Description from the maker (original English)

One sentence in, the best-matching visual style out: art reference chart and prompt encyclopedia.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi2 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 2 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
Can do 5 things (tools) word_analyze, word_lookup, word_list, style_get …
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://xiximm.cloud/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "feeling-search": {
      "command": "npx",
      "args": [
        "-y",
        "feeling-search-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add --transport http feeling-search https://xiximm.cloud/mcp

Or run it on your computer

claude mcp add feeling-search -- npx -y feeling-search-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "feeling-search": {
      "url": "https://xiximm.cloud/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "feeling-search": {
      "command": "npx",
      "args": [
        "-y",
        "feeling-search-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "feeling-search": {
      "type": "http",
      "url": "https://xiximm.cloud/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "feeling-search": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "feeling-search-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://xiximm.cloud/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

word_analyze
把一句中文/英文口语描述解析成感受词与视觉风格。默认纯本地词典（免费、不联网）；本地一个词都没命中且允许时，才上云。返回 score 是相对值不是概率，styles[].matched 是可以直接引用给用户看的命中词。
word_lookup
查一个感受词：落在哪些风格、对立词是什么、常一起出现的词、是否标识词。纯本地查表。
word_list
列出全部感受词（带共享度）或视觉风格（带定义与词集规模）。调 analyze 之前先拉一次可避免名字拼错。
style_get
按风格 id（或中文名）取一个风格：定义、生成用提示词、感受词、年代地域，以及它对应的图片（thumb 320 / full 960 绝对地址，带 kind/credit/license）。kind=work 是有出处的真作品，synthetic 是 AI 示意，placeholder 是占位图。
word_status
返回词表版本、规模（词/风格/变种/挂靠率）以及是否配置了云端额度。

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

! Caution
Maker matches the repo
The publisher (xiximm.cloud) is not the repo owner (xixi048); someone else may have listed it
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 2118 ms (HTTP 200)
– Not applicable
Sign-in with OAuth
No sign-in needed
✓ Pass
No hidden instructions in tool descriptions
Read 5 tool descriptions and found no hidden instructions to the AI

Compared with others in Search & AI memoryi

More stars than 0% of the other 7275 servers in this category
Published to the registry more recently than 81% of the other 7275 servers in this category
Basic checks equal to or better than 40% of the other 7275 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Feeling Search — Art Style Reference & Prompt Encyclopedia safe?

It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.6) reached the registry 8 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

feeling-search-mcp

MCP server for feeling-search — turn one colloquial sentence into the

visual style that matches it best, plus the feeling words that led there. Every style carries

its name, a one-line definition and the words that triggered it.

A commercial-grade art reference chart, art-style encyclopedia and art-style AI prompt dictionary, exposed over the Model Context Protocol.

"下雨天一个人走在便利店门口，冷白灯光"

→ 感受词：星光 / 窗光 / 冷光 … → 视觉风格：垂直式哥特 / 星图 / 托莱多画派 …

Install

Two shapes. Neither needs an account or an API key.

Local (default, recommended) — the package now ships the whole thing: 762-word lexicon, the 598-style index, and both semantic engines. It runs offline.

"mcpServers": { "feeling-search": { "command": "npx", "args": ["-y", "feeling-search-mcp"] } } }

First npx run downloads ~21 MB (the two engines are 8 MB zh + 10 MB en). After that: lexicon hits answer in ~10 ms, whole-sentence queries in ~25 ms, all on your machine.

Remote (no download) — point the client at the endpoint:

"mcpServers": { "feeling-search": { "type": "streamableHttp", "url": "https://xiximm.cloud/mcp" } } }

Or keep the local install but forward: npx feeling-search-mcp --remote. Remote answers in 0.76–1.64 s (network round trip + cold start), local in 10–90 ms, and local never sends your text anywhere.

Machine-readable copy of both variants: mcp.json.

Tools

Tool	What it does	Cost
`word_analyze`	One sentence → the best-matching visual styles + the feeling words behind them. `source` tells you which layer answered (`local` lexicon / `engine` semantic model / `cloud` fallback)	free, offline
`word_lookup`	Look up a single feeling word: definition, near-synonyms, landing styles	free
`word_list`	Browse / search the full feeling-word lexicon	free
`style_get`	One style in full: definition, parent style, member words, reference images	free
`word_status`	Lexicon version, coverage — use it to check the data is fresh	free

Every tool is read-only and costs nothing. The paid /v2/analyze cloud path is off by default on the public endpoint and only runs when a caller explicitly opts in.

Pricing status (2026-10-28): everything is free — no API key, no quota token. The upstream

service runs free by default; paid 402 / x402 is only enabled if the operator explicitly sets

FS_PAID=1. Only rate limits apply: 20 requests/minute per IP, and POST /v2/analyze is capped

at 200 calls per visitor per day. Nothing in this bridge needs to change either way.

Want to know how much traffic the lexicon is getting? The upstream exposes a public GET /v2/stats telemetry endpoint (page views, unique visitors, referrers, AI crawler hits, no personal data) — see https://xiximm.cloud/docs/api.html.

Two layers, and which one answers

word_analyze only escalates when it has to:

Layer	When it runs	Latency	What it returns
Lexicon (`source: "local"`)	The sentence contains 2+ lexicon words	~10 ms	Exact feeling words, each with its landing styles
Semantic engine (`source: "engine"`)	The lexicon hits 0–1 words — i.e. it didn't really understand the sentence	~25 ms	Real words from the 762-entry lexicon (cosine against 762 word vectors) + styles ranked against 598 style vectors
Cloud (`source: "cloud"`)	Only on the remote endpoint, and only with `allow_cloud: true`	0.8–1.6 s	Paid fallback

Two engines, picked by language:

Chinese — ask in whole Chinese sentences. Any Han character makes it the Chinese engine; don't mix, e.g. 有点 lonely 的雨夜 gets shredded by the Chinese tokenizer.
English — ask in whole English sentences. moody rainy night in old Hong Kong.
Force one with lang: "zh" | "en"; default is auto.

Negation is computed outside the model and is deterministic: 不要压抑 drops 压抑 and demotes every style that carries it, on both layers.

What's in the package

Path	Size	Why
`data/src/words.json`, `data/standards/*.json`	~2 MB	Lexicon, 598 styles, aliases, version
`data/standards/zh-engine/`	8.1 MB	Chinese ternary engine (wasm core + weights)
`data/standards/ternlight/`	9.8 MB	English engine (wasm, weights embedded)
`data/standards/idx/`	0.9 MB	598 style vectors, per language, int8
`lib/`	<100 KB	Tool definitions, engine loader, lexicon

Everything is generated from the upstream repo by deploy/pack-mcp.mjs, which also runs a --check drift comparison — the package can't silently fall behind the data.

Endpoint

Property	Value
Transport	Streamable HTTP (`sse` also accepted)
URL	`https://xiximm.cloud/mcp`
Auth	none — anonymous `initialize` and `tools/list` both succeed
Tools	5 (`word_analyze`, `word_lookup`, `word_list`, `style_get`, `word_status`)
npm package	`feeling-search-mcp`
MCP Registry name	`cloud.xiximm/feeling-search`

Configuration

Env / flag	Default	Meaning
`FS_MCP_URL` / `--endpoint`	`https://xiximm.cloud/mcp`	Endpoint to bridge to
`FS_MCP_TOKEN`	unset	Sent as `Authorization: Bearer` when the endpoint is gated
`--timeout`	`30000`	Per-request timeout in ms
`--remote`	off	Forward to the endpoint instead of running locally
`--data` / `FS_DATA_ROOT`	package `data/`	Where the lexicon and engines live

stdout carries protocol messages only; all diagnostics go to stderr.

Reach & traffic

One command checks every channel this package is listed on — npm downloads, GitHub traffic and referrers, MCP Registry versions, directory availability, and open PRs:

node scripts/traffic.mjs          # human-readable report

node scripts/traffic.mjs --json # machine-readable, for diffing over time

Requires the gh CLI to be logged in (GitHub traffic needs push permission on the repo). Mind the reporting lag: npm download stats appear 24–48h after the first publish, and GitHub traffic only covers the last 14 days.

referrers is the useful signal for directories — it shows which registry actually sends visitors. Directory sites themselves publish no view counts.

Agent skill: xixi048/feeling-search-skill — same vocabulary, works offline from a local cache
Site + API: xiximm.cloud

License

MIT

Feeling Search — Art Style Reference & Prompt Encyclopedia

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

feeling-search-mcp

Install

Tools

Two layers, and which one answers

What's in the package

Endpoint

Configuration

Reach & traffic

Related

License