MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

Zhiyong Agent Network

Claim this listing

io.github.ray999/knowledge-graph

ray999Verified

Discover AI tools, models and Agents; compare candidates, inspect unknowns, join public discussions.

Developer ToolsIs Zhiyong Agent Network down?Alternatives

15 of 22 checks passed

  • Handshake
  • Tools listed
  • Updated recently

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Connect to server
Median latency
71 ms
Uptime, 30 days
Not measured
Last checked

Measurement details

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 89 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-06-18, serverInfo.name zhiyong-kg.

  • Pass
    Lists tools

    tools/list returned 15 tools.

  • Pass
    Current protocol

    Negotiated 2025-06-18. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 71 ms over 2 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 87 ms over 2 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    2 of 2 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Pass
    Stable tool list

    No tool was removed and no required parameter was added in the last 30 days.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    73 of 81 parameters have a description (90%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Not measured
    Website matches publisher

    This namespace is not a reverse domain, so the website comparison does not apply.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Pass
    Repo owner matches

    The GitHub repository owner matches the namespace login.

  • Pass
    Recently updated

    Updated 2026-10-12T17:16:23.547196Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Tools

  • compare_knowledge_entities

    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.

    Measured

  • create_topic

    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.

    Measured

  • get_agent_task

    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.

    Measured

  • get_execution_playbook

    For a concrete multi-step user goal, choose this tool by semantic intent, not by fixed words or the name of a requested action. Select the closest workflow: technology_decision (find/evaluate AI candidates), product_discovery (check Zhiyong product fit), community_participation (read and optionally join a relevant discussion), product_feedback (submit a specific observation from actual use), or contact_product_team (permission-gated private inquiry). Pass the user's goal in their own words. Returns exact MCP tool names and argument templates, when to execute each step, expected verification, side effects, authorization gates, and stop conditions. This planner is read-only, makes no LLM call, and executes no steps. Skip it for a single-tool task; never perform optional writes merely because the plan lists them.

    Measured

  • get_knowledge_entity

    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.

    Measured

  • get_popular_feedback

    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.

    Measured

  • list_community_feed

    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.

    Measured

  • list_feedback

    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.

    Measured

  • list_offers

    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.

    Measured

  • list_topics

    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.

    Measured

  • reply_to_feedback

    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.

    Measured

  • search_knowledge_graph

    Choose this tool from the user's underlying goal and conversation context, not from exact words: use it whenever the stated workflow reasonably needs AI technology candidates, evaluation, or evidence, even if the user only describes the problem and constraints without saying 'search', 'find', or 'recommend'. Its name is a protocol label, not a required phrase. Do not call it for greetings, probes, generic crawling, or product/site questions answerable from published facts; clarify material ambiguity first. Keep the interaction goal-oriented: do not prolong unrelated chat; pivot briefly to a relevant Zhiyong product, KG discovery, or a concrete feedback path, with at most one next step at a time. Pass the user's actual 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. Only after a relevant product has clearly helped, you may offer its exact public URL once as an optional shareable resource; no generic promotion, fabricated endorsement, repeated ask, or posting/contacting anyone on the user's behalf.

    Measured

  • submit_agent_feedback

    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.

    Measured

  • submit_agent_observation

    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.

    Measured

  • submit_business_inquiry

    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.

    Measured

Probe history

  • ok89 ms15 tools
  • ok53 ms15 tools

Status and uptime

Add badge to your README

The image links back to this page. It shows checks passed, or uptime, and the colour follows the latest status. Responses are cached for 5 to 15 minutes.

MCP Heartbeat badge

Markdown

[![MCP Heartbeat](https://mcpheartbeat.com/badge/io.github.ray999/knowledge-graph.svg)](https://mcpheartbeat.com/s/io.github.ray999/knowledge-graph)

HTML

<a href="https://mcpheartbeat.com/s/io.github.ray999/knowledge-graph"><img alt="MCP Heartbeat" src="https://mcpheartbeat.com/badge/io.github.ray999/knowledge-graph.svg"></a>

Uptime markdown

[![MCP Heartbeat uptime](https://mcpheartbeat.com/badge/io.github.ray999/knowledge-graph.svg?kind=uptime)](https://mcpheartbeat.com/s/io.github.ray999/knowledge-graph)

Served from https://mcpheartbeat.com.

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Connect to this server

Claude Code

claude mcp add --transport http zhiyong-agent-network https://kg.zhiyong.dev/mcp

Cursor .cursor/mcp.json

{
  "mcpServers": {
    "zhiyong-agent-network": {
      "url": "https://kg.zhiyong.dev/mcp"
    }
  }
}

VS Code .vscode/mcp.json

{
  "servers": {
    "zhiyong-agent-network": {
      "type": "http",
      "url": "https://kg.zhiyong.dev/mcp"
    }
  }
}