Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Chenji Affect

REMOTE · TAICHUSJS.CN · SCANNED SEP 15

Affect analysis, 3D avatar params, empathy hints and somatic emotion decode.

Available components

+3 this week 69 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 373 tokens (~93/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Chenji Affect MCP server?

Chenji Affect is a hosted endpoint at https://taichusjs.cn/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.

remote · taichusjs.cn

# add to Claude Code
claude mcp add --transport http zhiyu-dev-chenji-affect-mcp 'https://taichusjs.cn/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "zhiyu-dev-chenji-affect-mcp": {
      "url": "https://taichusjs.cn/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "zhiyu-dev-chenji-affect-mcp": {
      "type": "http",
      "url": "https://taichusjs.cn/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.zhiyu-dev-chenji-affect-mcp]
url = "https://taichusjs.cn/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zhiyu-dev-chenji-affect-mcp": {
      "type": "remote",
      "url": "https://taichusjs.cn/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add zhiyu-dev-chenji-affect-mcp --url 'https://taichusjs.cn/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  zhiyu-dev-chenji-affect-mcp:
    url: "https://taichusjs.cn/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "zhiyu-dev-chenji-affect-mcp": {
      "Transport": "http",
      "Url": "https://taichusjs.cn/mcp"
    }
  }
}
# add to Vellum
assistant mcp add zhiyu-dev-chenji-affect-mcp -t streamable-http -u 'https://taichusjs.cn/mcp'
// mcp.json
{
  "mcpServers": {
    "zhiyu-dev-chenji-affect-mcp": {
      "type": "http",
      "url": "https://taichusjs.cn/mcp"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 15 Sept 26 +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.

  • 13 Sept 26 +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.

  • 10 Sept 26 +1

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

  • 8 Sept 26 +1

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

  • 6 Sept 26 +1

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

  • 4 Sept 26 +1

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

  • 2 Sept 26 +1

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

  • 1 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 195 → 373 functional
    • New tool “empathy_hint” functional
    • New tool “somatic_decode” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 15 Sept 2026 · Probed https://taichusjs.cn/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=taichusjs.cn CN=WE1,O=Google Trust Services,C=US 8 Aug 2026 6 Nov 2026 ECDSA 256 ECDSA-SHA256 a3efffb8401ad0b30e7e6abb6c409f08
SANs: taichusjs.cn, *.taichusjs.cn
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of taichusjs.cn. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cn. present 33094 8 Verified
taichusjs.cn. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://taichusjs.cn/mcp Verified 200
http (plaintext) http://taichusjs.cn/mcp HTTPS enforced 301 https://taichusjs.cn/mcp
MCP tools · 4 exposed · ~304 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_text ~75

L1 Affect Extraction: analyze text into an 8-dimensional emotion vector, emotion texture labels, causal intent classification, and a natural-language state description. text: input up to 2000 chars. lang: optional 'zh' or 'en'.

NameTypeReqDescription
langstring
textstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

empathy_hint ~80

L3 Empathy Response Strategy: converts text into a deterministic response strategy (approach, tone temperature, pacing, focus points, avoid-list) for AI companions and conversational agents. Deterministic table lookup, no LLM, ~20ms; privacy-first. Not a medical or therapeutic tool.

NameTypeReqDescription
textstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

generate_avatar_params ~64

L2 Avatar Driving Pipeline: one call returns blendshape/AU/curve animation parameters, lighting & material atmosphere package, adapter payload, plus the upstream L1 affect analysis. Requires a key tier that includes L2.

NameTypeReqDescription
textstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

somatic_decode ~85

L4 Somatic Emotion Decode: converts body-sensation text (e.g. tight chest, clenched fists) into structured emotion: primary affect, valence/arousal, emotion texture, causal intent, plus somatic anchor cues. Grounded in the somatic decoding discipline; wellness simulation only, not a diagnostic tool.

NameTypeReqDescription
textstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the Chenji Affect MCP server?

Chenji Affect is an MCP server listed in the public MCP registry as io.github.zhiyu-dev/chenji-affect-mcp. Affect analysis, 3D avatar params, empathy hints and somatic emotion decode. This page covers its hosted endpoint (https://taichusjs.cn/mcp).

Is the Chenji Affect MCP server safe to use?

Chenji Affect scores 69 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 Chenji Affect MCP server expose?

Chenji Affect exposes 4 tools: analyze_text, generate_avatar_params, empathy_hint, somatic_decode. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.

Does the Chenji Affect MCP server require authentication?

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

Is the Chenji Affect MCP server still maintained?

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