_ registry / mcp streamable-http · checked 3h ago

tw-ai-glossary

https://glossary.penguindriver.com

Registry code: 9fafd9913f52272e

api record

AI 與科技名詞白話解釋（繁體中文）：名詞定義、概念比較、實作教學與搜尋意圖分類，每則附原始來源與查核日期。

endpoint
https://glossary.penguindriver.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is tw-ai-glossary live?
Partly — its last checks failed now and then (checked 3h ago). It answered 0% of checks over the last 30 days.
Is tw-ai-glossary free to use?
Not measured yet.
What tools does tw-ai-glossary have?
6 tools: search_glossary, compare_concepts, get_howto, classify_search_intent, list_topics, explain_term.
Is tw-ai-glossary safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
degraded
uptime, 30 days
0%

90 days 0%· all time 0%

latency
—

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → degraded· timeout after 20000ms
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_glossary unknown never probed

    模糊搜尋本站的 AI 名詞、概念比較與實作教學。

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1
    }
  }
}
    arguments 16 lines
  • compare_concepts unknown never probed

    比較兩個 AI 概念差在哪（如 RAG vs 微調、MCP vs API、SEO vs GEO），回傳結論、比較表與各自適用情境。可給 id，或 a、b 兩個名詞。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "a": {
      "type": "string"
    },
    "b": {
      "type": "string"
    },
    "id": {
      "type": "string"
    }
  }
}
    arguments 14 lines
  • get_howto unknown never probed

    取得 AI 實作教學（建立 MCP 伺服器、llms.txt、FAQPage JSON-LD、robots.txt 封鎖 AI 訓練、x402 流程、計算 Token），含需求、步驟、程式碼與常見錯誤。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "關鍵字，例如 MCP、llms.txt"
    },
    "id": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • classify_search_intent unknown never probed

    判斷一句搜尋或提問屬於資訊探索、商業比較、技術除錯或行動指引哪種意圖，並給出建議答案結構、結構化資料類型與本站相關內容。

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • list_topics unknown never probed

    列出所有名詞（可依分類篩選）、概念比較與實作教學。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "category": {
      "enum": [
        "基礎概念",
        "模型技術",
        "協定與標準",
        "應用與產品",
        "搜尋與行銷",
        "硬體"
      ],
      "type": "string"
    }
  }
}
    arguments 16 lines
  • explain_term unknown never probed

    用白話解釋 AI 或科技名詞（如 MCP、RAG、AI 代理人、幻覺、GEO、x402），回傳定義、運作方式、例子、常見誤解、FAQ 與原始來源。可用中文、英文或別名。

    mcp-tool

    {
  "type": "object",
  "required": [
    "term"
  ],
  "properties": {
    "term": {
      "type": "string",
      "description": "名詞或 id，例如 MCP、檢索增強生成、ai-agent"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9fafd9913f52272e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9fafd9913f52272e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9fafd9913f52272e/badge.svg)](https://brick.blue/agent/9fafd9913f52272e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on penguindriver.com 12 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

4 more sit on this domain. All of them.