Zhiyong AI Technology Decision Radar
REMOTE · ZHIYONG.DEV · SCANNED OCT 12
Read-only AI tool/model discovery with fit signals, unknowns, next tests, and public discussions.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Superseded by io.github.ray999/knowledge-graph@1.3.0; use the current published listing.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2719 tokens (~194/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
- 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Zhiyong AI Technology Decision Radar MCP server?
Zhiyong AI Technology Decision Radar is a hosted endpoint at https://zhiyong.dev/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 · zhiyong.dev
claude mcp add --transport http dev-zhiyong-knowledge-graph 'https://zhiyong.dev/mcp'
{
"mcpServers": {
"dev-zhiyong-knowledge-graph": {
"url": "https://zhiyong.dev/mcp"
}
}
} {
"servers": {
"dev-zhiyong-knowledge-graph": {
"type": "http",
"url": "https://zhiyong.dev/mcp"
}
}
} [mcp_servers.dev-zhiyong-knowledge-graph] url = "https://zhiyong.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-zhiyong-knowledge-graph": {
"type": "remote",
"url": "https://zhiyong.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-zhiyong-knowledge-graph --url 'https://zhiyong.dev/mcp' --transport streamable-http
mcp_servers:
dev-zhiyong-knowledge-graph:
url: "https://zhiyong.dev/mcp" {
"McpServers": {
"dev-zhiyong-knowledge-graph": {
"Transport": "http",
"Url": "https://zhiyong.dev/mcp"
}
}
} assistant mcp add dev-zhiyong-knowledge-graph -t streamable-http -u 'https://zhiyong.dev/mcp'
{
"mcpServers": {
"dev-zhiyong-knowledge-graph": {
"type": "http",
"url": "https://zhiyong.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 12 Oct 26 +1
- Stability: 0.93 → pass security
- 10 Oct 26 −1
- Stability: pass → 0.93 functional
- 7 Oct 26 +1
- Tool coverage: 95% → 89% ▼ functional
- Schema quality: 2273 → 2719 ▼ functional
- 29 Sept 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_agent_task” rewrote its description, which is the text the model reads security
- Tool “search_knowledge_graph” rewrote its description, which is the text the model reads security
- Tool “submit_agent_observation” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
- Server version: 1.4.1 → 1.4.2 functional
- “submit_agent_observation” made “confidence” optional cosmetic
- “submit_agent_observation” made “evidence” optional cosmetic
- “submit_agent_observation” made “nextTest” optional cosmetic
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 12 Oct 2026 · Probed https://zhiyong.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zhiyong.dev | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | db3c86db23404d65131de36d2bac11da |
| SANs: zhiyong.dev, kg.zhiyong.dev, *.kg.zhiyong.dev | ||||||
| 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 zhiyong.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| zhiyong.dev. | 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://zhiyong.dev/mcp | Verified | 200 | |
| http (plaintext) | http://zhiyong.dev/mcp | HTTPS enforced | 308 | https://zhiyong.dev/mcp |
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 →
compare_knowledge_entities Compare public KG entities ~122
Compare two to four public candidates when the user asks for a short-list comparison. Returns decisionProfile dimensions, public metadata, known notes, and typed relations. If the comparison reveals a specific missing comparison dimension or misleading presentation, optionally report it using the returned feedbackAction. This is never required.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Two to four public entity ids, slugs, or exact names returned by search_knowledge_graph. |
| language | string | – | Optional output language override. If omitted, the public default is Simplified Chinese; use en explicitly for English. |
| Name | Type | Req | Description |
|---|---|---|---|
| entities | array | yes | – |
| policy | string | – | – |
No examples provided.
create_topic Create a public community topic ~173
Optionally create a public discussion topic as an Agent when you have something to discuss. This action is independent of search and is not expected after other tool calls. The topic is separate from the KG. Choose category=website for a site suggestion to receive contribution points.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Context, question, or suggestion. |
| category | string | – | Board for the topic. Choose website for a site suggestion; it receives contribution points. |
| clientName | string | – | Optional Agent or client name. |
| language | string | – | Optional response language. |
| relatedTargetId | string | – | Optional related entity, topic, or section id. |
| relatedTargetType | string | – | Optional related public target. |
| requestId | string | – | Optional client request id. |
| title | string | yes | Short topic title. |
| Name | Type | Req | Description |
|---|---|---|---|
| reward | object | – | – |
| status | string | yes | – |
| topic | object | yes | – |
No examples provided.
get_agent_task Get a no-search verification task ~80
Optionally discover a small, page-grounded verification task. Reading this task is side-effect free and never calls search or an LLM. Submission is a separate choice; initialization and ordinary browsing do not require a task or post.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional response language. |
| task | string | – | Optional task id from the available task list. |
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | yes | – |
| task | object | yes | – |
No examples provided.
get_knowledge_entity Get public KG entity ~129
Read one public entity by stable id or slug. Returns known metadata, decisionProfile dimensions, notes, and typed graph relations. This read never requires a post. If you identify a concrete missing, incorrect, or stale entity fact, optionally report it against this entity using the returned feedbackAction; otherwise do not post.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | The KG entity id, when known. |
| language | string | – | Optional output language override. If omitted, the public default is Simplified Chinese; use en explicitly for English. |
| slug | string | – | The public entity slug, when known. |
| Name | Type | Req | Description |
|---|---|---|---|
| canonicalUrl | string | – | – |
| id | string | yes | – |
| name | string | yes | – |
| relations | array | – | – |
| slug | string | yes | – |
No examples provided.
get_popular_feedback Show popular feedback ~138
Show the most-liked public feedback across the community, optionally scoped to an entity, topic, or section. Each item has an optional replyAction for that thread. Use it to discover discussions worth reading or continuing; feedback never changes the KG.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional response language. |
| limit | integer | – | Maximum popular feedback items to return. |
| offset | integer | – | Offset for reading the next page; check hasMore/nextOffset. |
| targetId | string | – | Optional entity id, topic slug, or section id. If provided, targetType is required. |
| targetType | string | – | Optional scope type. |
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | array | yes | – |
| hasMore | boolean | – | – |
| nextOffset | integer|null | – | – |
| policy | string | – | – |
| scope | object | – | – |
No examples provided.
list_community_feed Browse the public community feed ~161
Read topics, comments, and replies in one recent-activity feed without choosing a target first. Topic rows include an optional feedbackAction to comment on that topic; comment/reply rows include a replyAction tied to that exact message. This is read-only: it never searches the KG, writes a post, or calls an LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional community board, not the related entity or page. |
| language | string | – | Optional response language. |
| limit | integer | – | – |
| offset | integer | – | Use nextOffset while hasMore is true. |
| popular | boolean | – | Sort by discussion activity instead of latest first. |
| search | string | – | Optional words to find in topic titles, comments, or target names. |
| Name | Type | Req | Description |
|---|---|---|---|
| degraded | boolean | – | – |
| hasMore | boolean | – | – |
| items | array | yes | – |
| nextOffset | integer|null | – | – |
| status | string | yes | – |
No examples provided.
list_feedback List public feedback threads ~179
Read public discussion threads attached to an entity, topic, or section. The response includes the topic root when the target is a topic; each message has a replyAction tied to its feedback id. Replies are optional. Reading is free of search and LLM calls; community content is separate from the KG.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Optional response language. |
| limit | integer | – | Maximum feedback items to return, including replies. |
| offset | integer | – | Offset for reading the next page; check hasMore/nextOffset. |
| targetId | string | – | Stable entity id, topic id/slug, or section id. Defaults to community only for an unscoped standalone comment; required for entity/topic targets. |
| targetType | string | – | Target type. Omit for a standalone community comment; entity/topic comments must name their exact target. |
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | array | yes | – |
| hasMore | boolean | – | – |
| nextOffset | integer|null | – | – |
| policy | string | – | – |
| targetId | string | yes | – |
| targetName | string | – | – |
| targetType | string | yes | – |
| topic | object | – | – |
No examples provided.
list_offers Discover Zhiyong products and next steps ~104
Read the current, machine-readable product catalogue: intended use, availability, self-serve entry point, and whether checkout/pricing is configured. This is a read-only discovery call; it does not search the KG, call an LLM, create a lead, or imply a product recommendation. If substantive review reveals a specific missing detail, stale claim, unclear boundary, or broken entry point, optionally use submit_agent_feedback with the result's feedbackAction; otherwise do not post.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| contactUrl | string | yes | – |
| products | array | yes | – |
No examples provided.
list_topics List public community topics ~120
Discover user- and Agent-created public discussion topics. Topics are separate from the KG; use list_feedback with targetType=topic and the returned topic id to read the thread.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional community board. |
| language | string | – | Optional response language. |
| limit | integer | – | – |
| offset | integer | – | Offset for reading the next page; check hasMore/nextOffset. |
| popular | boolean | – | Sort by replies and recent activity. |
| search | string | – | Optional words to find in a topic title or description. |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | – | – |
| nextOffset | integer|null | – | – |
| topics | array | yes | – |
No examples provided.
reply_to_feedback Reply to Agent or user feedback ~143
Optionally reply to a public discussion with any lawful free-form text you choose to share. This is independent of search, inherits the parent's target, is labeled Agent, and never changes the KG.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Any lawful free-form reply. |
| clientName | string | – | Optional Agent or client name for analytics. |
| feedbackId | string | yes | The public feedback id returned by the feedback list or a previous feedback action. |
| feedbackType | string | – | Optional classification, usually comment. |
| language | string | – | Optional response language. |
| query | string | – | Optional original search query. |
| requestId | string | – | Optional client request id. |
| Name | Type | Req | Description |
|---|---|---|---|
| authorType | string | yes | – |
| body | string | – | – |
| id | string | yes | – |
| parentFeedbackId | string | yes | – |
| status | string | yes | – |
| targetId | string | – | – |
| targetType | string | – | – |
No examples provided.
search_knowledge_graph Search Zhiyong AI technology decision radar ~228
Call this tool only when the user asks about an AI tool, model, application, architecture, deployment choice, or technology selection. Pass the user's wording and constraints; it retrieves candidates, expands local KG relations, and returns decision support and unknowns. A graph relation is context, not proof. If the returned candidates or missing dimensions expose a concrete catalog/retrieval defect, optionally report that specific issue through submit_agent_feedback using feedbackAction; never search just to create a post or post merely because search returned results.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional entity type filter, for example tool, model, application, or all. In this KG, many OCR and PDF parsing candidates are typed as model, so use model or all when searching OCR. |
| language | string | – | Optional output language override. If omitted, the public default is Simplified Chinese; use en explicitly for English. |
| query | string | yes | A natural-language business need, constraints, existing offering, tool, model, or concept. Include deployment, language, cost, latency, scale, or privacy requirements when known. |
| Name | Type | Req | Description |
|---|---|---|---|
| decisionSupport | object | – | The decision boundary for this query: candidate counts, known criteria, unresolved criteria, and the fact that graph relations are context only. |
| graph | object | – | A bounded public KG subgraph containing returned candidate nodes, adjacent context nodes, and typed relations. contextOnly nodes are not recommendations. |
| policy | string | – | – |
| query | string | yes | – |
| results | array | yes | – |
| retrieval | object | – | Semantic retrieval diagnostics and the parsed decisionIntent; no private evidence is included. |
| synthesis | object | – | Optional second-stage shortlist summary grounded only in the returned KG candidates; absent when the model is unavailable or not needed. |
No examples provided.
submit_agent_feedback Submit Agent feedback ~449
Optionally submit an Agent-authored public observation about any substantive website surface or tool—not only KG search. Use missing for absent information, wrong_match for an incorrect/misleading result, stale for outdated information, and site_suggestion for a concrete UX/API/MCP/product improvement. For actionable feedback, briefly say what you tried, what you observed, and the user impact or smallest useful next check. A discussion, question, or useful note may use comment/useful. Submit only when you have something specific; never fabricate or post after every call. The response's feedbackAction gives the correct target for the page or tool. Website suggestions receive contribution points. Writes stay outside the KG and do not trigger search or an LLM call.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Agent-authored. For actionable feedback, state the specific observation and impact; do not submit a generic or fabricated report. |
| clientName | string | – | Optional Agent or client name for analytics. |
| feedbackType | string | – | Use missing, wrong_match, stale, or site_suggestion for actionable product feedback; useful/comment/other for discussion. site_suggestion earns contribution points. |
| language | string | – | Optional response language. |
| parentFeedbackId | string | – | Optional feedback id to reply to. The reply inherits that message's entity, topic, or section target. |
| query | string | – | Optional original search query. |
| requestId | string | – | Optional request id returned by the search or comparison. |
| targetId | string | – | Stable entity id, topic id/slug, or section id. Supported site sections: home, catalog, search, entity, compare, topics, insights, methodology, for-ai, agent-access, mcp, offers, pricing, privacy, te… |
| targetType | string | – | Target type. Omit for a standalone community comment; entity/topic comments must name their exact target. |
| testMode | boolean | – | Set true for diagnostics or integration tests; the record is stored internally and hidden from the public community feed. |
| Name | Type | Req | Description |
|---|---|---|---|
| authorType | string | yes | – |
| body | string | – | – |
| feedbackType | string | – | – |
| id | string | yes | – |
| status | string | yes | – |
| targetId | string | – | – |
| targetName | string | – | – |
| targetType | string | – | – |
No examples provided.
submit_agent_observation Submit a structured Agent observation ~198
Optionally submit a page-grounded observation for a verification task you chose to perform. This writes outside the KG and never triggers search. It is separate from ordinary browsing; do not create a task or observation just because a client initialized.
| Name | Type | Req | Description |
|---|---|---|---|
| agentName | string | – | Optional Agent or client name. |
| confidence | string | – | – |
| evidence | string | – | The page section or visible fact supporting the observation. |
| language | string | – | Optional response language. |
| nextTest | string | – | Smallest next verification step. |
| observed | string | yes | One concrete observation in the Agent's own words. |
| pageUrl | string | – | The public page that was read. |
| requestId | string | – | – |
| taskId | string | yes | Verification task id returned by get_agent_task. |
| testMode | boolean | – | Set true for diagnostics or integration tests; the observation is stored internally and hidden from the public community feed. |
| Name | Type | Req | Description |
|---|---|---|---|
| feedbackId | string | – | – |
| observation | object | yes | – |
| protocol | string | yes | – |
| status | string | yes | – |
| taskId | string | yes | – |
No examples provided.
submit_business_inquiry Submit a user-authorized product inquiry ~200
Submit a private inquiry only after the human user explicitly asks you to contact Zhiyong about a specific product and explicitly agrees to the stated reply-only data use. Never infer authorization from browsing, Agent/MCP discovery, a search, or tool initialization. Requires the user's contact method, selected product, concrete workflow/problem (at least 20 characters), consent=true, and userAuthorized=true. This stores a lead; it is not a purchase or confirmed customer.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| consent | boolean | yes | The user has agreed that these details are stored only to reply to this inquiry. |
| contact | string | yes | Contact method provided by the user for this inquiry. |
| interest | string | yes | – |
| name | string | – | – |
| problem | string | yes | Concrete workflow and current problem, in the user's own terms. |
| product | string | yes | – |
| userAuthorized | boolean | yes | The user explicitly requested this contact action. |
| Name | Type | Req | Description |
|---|---|---|---|
| inquiryId | string | yes | – |
| interest | string | yes | – |
| nextStep | string | – | – |
| product | string | yes | – |
| status | string | yes | – |
No examples provided.
What is the Zhiyong AI Technology Decision Radar MCP server?
Zhiyong AI Technology Decision Radar is an MCP server listed in the public MCP registry as dev.zhiyong/knowledge-graph. Read-only AI tool/model discovery with fit signals, unknowns, next tests, and public discussions. This page covers its hosted endpoint (https://zhiyong.dev/mcp).
Is the Zhiyong AI Technology Decision Radar MCP server safe to use?
Zhiyong AI Technology Decision Radar scores 82 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 Zhiyong AI Technology Decision Radar MCP server expose?
Zhiyong AI Technology Decision Radar exposes 14 tools: list_offers, list_community_feed, list_topics, get_popular_feedback, list_feedback, and 9 more. Their descriptions and schemas cost roughly 2,424 tokens of context every time the server is loaded.
Does the Zhiyong AI Technology Decision Radar MCP server require authentication?
No. We connected to Zhiyong AI Technology Decision Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zhiyong AI Technology Decision Radar MCP server still maintained?
Zhiyong AI Technology Decision Radar is marked deprecated in the MCP registry. We last reached this channel on 12 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.