Skip to content

AIYuCha Domain Intelligence MCP server

io.github.sinianchu9/aiyucha-domain-intelligencesinianchu9streamable-httpv1.0.5Scanned

Analyze public domain names: naming features, structural value, RDAP/ICP evidence, and comparisons.

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AIYuCha Domain Intelligence MCP server can do

The AIYuCha Domain Intelligence MCP server is published by the GitHub account sinianchu9. It has 5 tools. It can create or change data (2 tools: get_domain_history and check_domain_risk), but cannot delete data. 3 tools only read.

5 tools bring in text other people can write (analyze_domain_features, analyze_domain_value, get_domain_history and 2 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • check_domain_riskCheck observed registry RDAP status and reported risk signals.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check observed registry RDAP status and reported risk signals. Unstable backlink and network sources are disabled by default until verified; missing data is not a clean-risk finding.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
  • get_domain_historyRead registration RDAP and available ICP filing evidence.Reads text others write1 finding

    Why it is in this group

    • The name "get_domain_history" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "get_domain_history" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_domain_history" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Read registration RDAP and available ICP filing evidence. Additional archive sources are disabled by default until stability is verified. Does not expose registrant PII.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
Only reads 3Show 3 read-only tools
  • analyze_domain_featuresExamine a registrable domain's spelling, label length, suffix, structural brand fit and possible industries.Reads text others writeNo findings

    Why it is in this group

    • The name "analyze_domain_features" says "analyze": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Examine a registrable domain's spelling, label length, suffix, structural brand fit and possible industries. Rule-based only; no claim of trademark clearance.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • analyze_domain_valueGive a transparent, broad illustrative USD structural price reference based on name and suffix, plus a 0-100 structural score.Reads text others writeNo findings

    Why it is in this group

    • The name "analyze_domain_value" says "analyze": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Give a transparent, broad illustrative USD structural price reference based on name and suffix, plus a 0-100 structural score. Does not fetch comparable transactions or guarantee resale value.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • compare_domainsCompare two distinct registrable domains' transparent structural brand features and heuristic value.Reads text others writeNo findings

    Why it is in this group

    • The name "compare_domains" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Compare two distinct registrable domains' transparent structural brand features and heuristic value. Does not certify market liquidity, ownership, trademark safety or registerability.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://aiyucha.com/mcp: tools/list returned 5 tools to an anonymous client, including get_domain_history (write), check_domain_risk (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_domain_history" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_domain_history" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http aiyucha-domain-intelligence https://aiyucha.com/mcp
claude mcp add --transport http aiyucha-domain-intelligence https://aiyucha.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__aiyucha-domain-intelligence__analyze_domain_features",
      "mcp__aiyucha-domain-intelligence__analyze_domain_value",
      "mcp__aiyucha-domain-intelligence__compare_domains"
    ],
    "ask": [
      "mcp__aiyucha-domain-intelligence__get_domain_history",
      "mcp__aiyucha-domain-intelligence__check_domain_risk"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as aiyucha-domain-intelligence. Review it before you use it.

Capability tags behind 5 rules
  • mcp__aiyucha-domain-intelligence__analyze_domain_features untrusted-input
  • mcp__aiyucha-domain-intelligence__analyze_domain_value untrusted-input
  • mcp__aiyucha-domain-intelligence__get_domain_history untrusted-input
  • mcp__aiyucha-domain-intelligence__check_domain_risk untrusted-input
  • mcp__aiyucha-domain-intelligence__compare_domains untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.sinianchu9/aiyucha-domain-intelligence/verify?hash=0acdfe21348c51fae4de5efda6054fd837954a52dd5e4d306b66c3abebc60e45" | jq -e '.changed == false'

Pinned hash 0acdfe21348c, from Nov 20, 2026, 13:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.sinianchu9/aiyucha-domain-intelligence/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.sinianchu9/aiyucha-domain-intelligence
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.sinianchu9/aiyucha-domain-intelligence.svg)](https://radar.anlyon.com/servers/io.github.sinianchu9/aiyucha-domain-intelligence)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.

AIYuCha Domain Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AIYuCha Domain Intelligence MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AIYuCha Domain Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AIYuCha Domain Intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the AIYuCha Domain Intelligence MCP server have?

5 tools: 2 write, 3 read. get_domain_history, check_domain_risk, analyze_domain_features, analyze_domain_value and compare_domains.

Does the AIYuCha Domain Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AIYuCha Domain Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AIYuCha Domain Intelligence MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.