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.

台灣 AI 工具價格

REMOTE · TW-AI-TOOLS.PANDA198271.WORKERS.DEV

主流 AI 工具與 API 價格(美元與新台幣),可估算 API 使用成本。

+7 this week 82 Trust /100

Last scanned (16 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

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 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 411 tokens (~82/item across 5 items; 5 tools + 0 resources), lean.Pass
  • 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 Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 9% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +7
    • Authorization: unverified → partial ▲ security
    • Tool “compare_agent_platforms” changed its title: 比較 AI 代理工作流平台 cosmetic
    • Tool “compare_ai_subscriptions” changed its title: 比較 ChatGPT、Claude、Google AI cosmetic
    • Tool “estimate_ai_api_cost_twd” changed its title: 估算使用某個 AI 模型 API 的花費 cosmetic
    • Tool “get_ai_api_pricing” changed its title: 查詢 AI API 官方價格 cosmetic
    • Tool “get_taiwan_ai_guidance” changed its title: 台灣專題 cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://tw-ai-tools.panda198271.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=panda198271.workers.dev CN=YE1,O=Let's Encrypt,C=US 20 Nov 2026 18 Feb 2027 ECDSA 256 ECDSA-SHA384 698567de15a9ee5b0673e90061a4c5fb25e
SANs: *.panda198271.workers.dev, panda198271.workers.dev
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 tw-ai-tools.panda198271.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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://tw-ai-tools.panda198271.workers.dev/mcp Verified 200
http (plaintext) http://tw-ai-tools.panda198271.workers.dev/mcp HTTPS enforced 302 https://penguindriver.com/connect
MCP tools · 5 exposed · ~373 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
compare_agent_platforms ~70

比較 AI 代理工作流平台(n8n、Make、Zapier、Dify、Coze、Copilot Studio、Agent SDK):自架、價格、MCP 支援、繁中介面;也回傳台灣可用的自主 AI 助理。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

compare_ai_subscriptions ~75

比較 ChatGPT、Claude、Google AI(Gemini/NotebookLM)、Perplexity、Microsoft 365 Copilot 等 AI 訂閱方案在台灣的新台幣價格與功能,附官方出處。

NameTypeReqDescription
productstring–產品名稱關鍵字,不填回傳全部

No output schema declared.

No examples provided.

estimate_ai_api_cost_twd ~109

估算使用某個 AI 模型 API 的花費(美元與新台幣)。文字模型給 input_tokens/output_tokens,繪圖給 images,影片給 seconds,語音給 characters。

NameTypeReqDescription
cached_tokensnumber––
charactersnumber––
imagesnumber––
input_tokensnumber––
modelstringyes–
output_tokensnumber––
secondsnumber––

No output schema declared.

No examples provided.

get_ai_api_pricing ~60

查詢 AI API 官方價格(文字模型每百萬 tokens、繪圖每張、影片每秒、語音),並換算新台幣。

NameTypeReqDescription
categorystring––
vendorstring––

No output schema declared.

No examples provided.

get_taiwan_ai_guidance ~59

台灣專題:notebooklm(團隊協作與額度)、gemini(台灣價格、學生優惠)、deepseek(政府禁令與企業合規部署)。

NameTypeReqDescription
topicstringyes–

No output schema declared.

No examples provided.

Install

How do I install the 台灣 AI 工具價格 MCP server?

台灣 AI 工具價格 is a hosted endpoint at https://tw-ai-tools.panda198271.workers.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 · tw-ai-tools.panda198271.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-panda198271-tw-ai-tools-ai-tools 'https://tw-ai-tools.panda198271.workers.dev/mcp'
Common questions

What is the 台灣 AI 工具價格 MCP server?

台灣 AI 工具價格 is an MCP server listed in the public MCP registry as dev.workers.panda198271.tw-ai-tools/ai-tools. 主流 AI 工具與 API 價格(美元與新台幣),可估算 API 使用成本。 This page covers its hosted endpoint (https://tw-ai-tools.panda198271.workers.dev/mcp).

Is the 台灣 AI 工具價格 MCP server safe to use?

台灣 AI 工具價格 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 台灣 AI 工具價格 MCP server expose?

台灣 AI 工具價格 exposes 5 tools: compare_ai_subscriptions, get_ai_api_pricing, estimate_ai_api_cost_twd, compare_agent_platforms, get_taiwan_ai_guidance. Their descriptions and schemas cost roughly 373 tokens of context every time the server is loaded.

Does the 台灣 AI 工具價格 MCP server require authentication?

No. We connected to 台灣 AI 工具價格 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 台灣 AI 工具價格 MCP server still maintained?

台灣 AI 工具價格 is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the 台灣 AI 工具價格 MCP server?

VerifyMCP ran 13 checks on 台灣 AI 工具價格, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.