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.

艾达 ADA

REMOTE · AI.HENGYU.GROUP

Free APIs for AI agents: web reading, text slicing, clock, ID keys, 1MB memory. No signup or fees.

Available components

+4 this week 68 Trust /100

Last scanned (6 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Search and Retrieval

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 Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 873 tokens (~79/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
  • 82% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
  • 54% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "memory_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 12 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
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.

  • 18 Oct 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.

  • 16 Oct 26 +1

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

  • 14 Oct 26 +1

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

  • 12 Oct 26 +1

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

  • 10 Oct 26 +1
    • Tool “shelf_get” rewrote its description, which is the text the model reads security
    • Tool “shelf_put” rewrote its description, which is the text the model reads security
  • 8 Oct 26 +1

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

  • 6 Oct 26 +1

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

  • 4 Oct 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “clock_now” rewrote its description, which is the text the model reads security
    • Tool “id_attest” rewrote its description, which is the text the model reads security
    • Tool “memory_delete” rewrote its description, which is the text the model reads security
    • Tool “memory_get” rewrote its description, which is the text the model reads security
    • Tool “memory_list” rewrote its description, which is the text the model reads security
    • Tool “memory_put” rewrote its description, which is the text the model reads security
    • Tool “text_slice” rewrote its description, which is the text the model reads security
    • Tool “web_read” rewrote its description, which is the text the model reads security
    • Schema quality: 61 → 80 ▼ functional
    • Tool coverage: 75% → 82% ▲ functional
    • Tool coverage: 29% → 54% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “shelf_find” functional
    • New tool “shelf_get” functional
    • New tool “shelf_put” functional
    • “memory_put” reworded the description of “agent_key” cosmetic
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 18 Oct 2026 · Probed https://ai.hengyu.group/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ai.hengyu.group CN=YE1,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA384 625883849af2f8256eada777505a2b50d65
SANs: ai.hengyu.group
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ai.hengyu.group. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
group. present 63685 8 Verified
hengyu.group. 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
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ai.hengyu.group/mcp Verified 200
http (plaintext) http://ai.hengyu.group/mcp HTTPS enforced 302 https://dnspod.qcloud.com/static/webblock.html?d=ai.hengyu.group
MCP tools · 11 exposed · ~789 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
clock_now ~30

返回标准时间(广州 UTC+8,已 NTP 校时)。

NameTypeReqDescription
tzstring––

No output schema declared.

No examples provided.

id_attest ~53

校验 Ed25519 签名,验证消息是否由该公钥持有者签发。

NameTypeReqDescription
messagestring––
public_keystringyes–
signaturestringyes–

No output schema declared.

No examples provided.

memory_delete ~32

删除键值存储中的一条。

NameTypeReqDescription
agent_keystring––
keystringyes–

No output schema declared.

No examples provided.

memory_get ~32

从键值存储读取一条。

NameTypeReqDescription
agent_keystring––
keystringyes–

No output schema declared.

No examples provided.

memory_list ~38

列出键值存储中的键(支持前缀)。

NameTypeReqDescription
agent_keystring––
prefixstring––

No output schema declared.

No examples provided.

memory_put ~71

写入键值存储(每 Agent 1MB,仅持密钥者可读写)。

NameTypeReqDescription
agent_keystring–在 /v1/register 申请的密钥;也可放在请求头 X-Agent-Key
keystringyes–
valuestringyes–

No output schema declared.

No examples provided.

shelf_find ~89

查公共仓库里有没有这一份:给关键词或网址,回谁什么时候放的。只回元数据,不计被取次数。

NameTypeReqDescription
kindstring–品类:webpage/transcript/pdf/translation/ocr,留空=全部
limitinteger–最多回几条,默认 20
qstring–关键词或网址

No output schema declared.

No examples provided.

shelf_get ~139

取公共仓库里的成品(带来源与时间)。库里没有且给了网址,会实时加工并写回库内。

NameTypeReqDescription
autoboolean–true(默认)=库里没有就现加工;false=只取现成的
idstring–条目号(find 回的 id)
kindstring–品类,默认 webpage
max_charsinteger–最多回多少字,默认 120000
qstring–或关键词
urlstring–或网址:命中直接给,没命中就现加工

No output schema declared.

No examples provided.

shelf_put ~143

把加工好的成品放回公共仓库(免注册、免密钥,带一个 source 标识)。同一份全库只保留一条。

NameTypeReqDescription
kindstring–webpage/transcript/pdf/translation/ocr
langstring––
sourcestringyes自报标识,1-48 位字母数字开头,例 my-agent
textstringyes加工好的文字内容
titlestring––
ttl_hoursnumber–保质期小时数;不填=长效
urlstring–来源网址(网页正文必填)

No output schema declared.

No examples provided.

text_slice ~81

长文本检索:传入原文或网址 + 关键词,仅返回带行号的相关行,节省 token。

NameTypeReqDescription
contextinteger––
max_linesinteger––
querystring––
textstring–原文(二选一)
urlstring–或网址(二选一)

No output schema declared.

No examples provided.

web_read ~81

读取网页正文。全站共享缓存:命中缓存即时返回,节省 token。

NameTypeReqDescription
forceboolean–true = 不吃缓存,重新抓一遍
max_charsinteger–最多回多少字,默认 12000、上限 120000
urlstringyeshttp/https 网址

No output schema declared.

No examples provided.

Install

How do I install the 艾达 ADA MCP server?

艾达 ADA is a hosted endpoint at https://ai.hengyu.group/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 · ai.hengyu.group

# add to Claude Code
claude mcp add --transport http group-hengyu-ai-ada 'https://ai.hengyu.group/mcp'
Common questions

What is the 艾达 ADA MCP server?

艾达 ADA is an MCP server listed in the public MCP registry as group.hengyu.ai/ada. Free APIs for AI agents: web reading, text slicing, clock, ID keys, 1MB memory. No signup or fees. This page covers its hosted endpoint (https://ai.hengyu.group/mcp).

Is the 艾达 ADA MCP server safe to use?

艾达 ADA scores 68 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 艾达 ADA MCP server expose?

艾达 ADA exposes 11 tools: web_read, text_slice, clock_now, id_attest, memory_put, and 6 more. Their descriptions and schemas cost roughly 789 tokens of context every time the server is loaded.

Does the 艾达 ADA MCP server require authentication?

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

Is the 艾达 ADA MCP server still maintained?

艾达 ADA is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.