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.

io.github.aixingzhe/sagelib

REMOTE · WWW.SAGELIB.COM

List, compare, and call 68 LLMs with live pricing through one Chinese API gateway.

Available components

+4 this week 65 Trust /100

Last scanned (16 hours ago)

Scores higher than 46% 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 Security57
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 291 tokens (~97/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 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.

  • 15 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 61

    First indexed and scored.

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://www.sagelib.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.sagelib.com CN=YE2,O=Let's Encrypt,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA384 65552d4efaf1316f14348e218d7059674e8
SANs: api.sagelib.com, sagelib.com, www.sagelib.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 www.sagelib.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
sagelib.com. 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://www.sagelib.com/mcp Verified 200
http (plaintext) http://www.sagelib.com/mcp HTTPS enforced 301 https://www.sagelib.com/mcp
MCP tools · 3 exposed · ~291 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
call_model ~122

通过本站网关调用指定模型(OpenAI 兼容接口)。必须提供用户自己的网关令牌 api_key,服务端不保存密钥。

NameTypeReqDescription
api_keystringyes本站令牌(sk- 开头),仅用于本次请求
max_tokensinteger–可选,最大输出 token
modelstringyes模型标识,如 claude-sonnet-5-5
promptstringyes用户提示词
systemstring–可选,系统提示词

No output schema declared.

No examples provided.

compare_models ~64

对比指定模型:上下文长度、类型、输入/输出单价。传入 2–6 个模型标识。

NameTypeReqDescription
codesarrayyes模型标识列表,如 ["claude-sonnet-5-5","gpt-6-sol"]

No output schema declared.

No examples provided.

list_models ~105

列出本站当前在架的大模型:模型标识、名称、类型、上下文长度、输入/输出单价。可按类型(text/image/audio/video)或关键词过滤。

NameTypeReqDescription
app_typestring–text / image / audio / video,留空返回全部
keywordstring–按模型标识或显示名模糊匹配
limitinteger–最多返回多少条,默认 30

No output schema declared.

No examples provided.

Install

How do I install the io.github.aixingzhe/sagelib MCP server?

io.github.aixingzhe/sagelib is a hosted endpoint at https://www.sagelib.com/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 · www.sagelib.com

# add to Claude Code
claude mcp add --transport http aixingzhe-sagelib 'https://www.sagelib.com/mcp'
Common questions

What is the io.github.aixingzhe/sagelib MCP server?

io.github.aixingzhe/sagelib is an MCP server listed in the public MCP registry as io.github.aixingzhe/sagelib. List, compare, and call 68 LLMs with live pricing through one Chinese API gateway. This page covers its hosted endpoint (https://www.sagelib.com/mcp).

Is the io.github.aixingzhe/sagelib MCP server safe to use?

io.github.aixingzhe/sagelib scores 65 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 io.github.aixingzhe/sagelib MCP server expose?

io.github.aixingzhe/sagelib exposes 3 tools: list_models, compare_models, call_model. Their descriptions and schemas cost roughly 291 tokens of context every time the server is loaded.

Does the io.github.aixingzhe/sagelib MCP server require authentication?

No. We connected to io.github.aixingzhe/sagelib without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.aixingzhe/sagelib MCP server still maintained?

io.github.aixingzhe/sagelib 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 io.github.aixingzhe/sagelib MCP server?

VerifyMCP ran 12 checks on io.github.aixingzhe/sagelib, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.aixingzhe/sagelib: Authorization. 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.