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

sagelib-gateway

https://www.sagelib.com

Registry code: 2d6bac1eb0d19c28

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://www.sagelib.com/mcp
protocol
streamable-http ·2024-11-05
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 sagelib-gateway live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is sagelib-gateway free to use?
Yes — the hub reached it with no key and no payment.
What tools does sagelib-gateway have?
3 tools: call_model, compare_models, list_models.
Is sagelib-gateway 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
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
733ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 3 tools
1 open 2 never probed 1 of 3 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.

  • list_models open 1h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "最多返回多少条，默认 30"
    },
    "keyword": {
      "type": "string",
      "description": "按模型标识或显示名模糊匹配"
    },
    "app_type": {
      "type": "string",
      "description": "text / image / audio / video，留空返回全部"
    }
  }
}
    arguments 17 lines
  • call_model unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "model",
    "prompt",
    "api_key"
  ],
  "properties": {
    "model": {
      "type": "string",
      "description": "模型标识，如 claude-sonnet-5-5"
    },
    "prompt": {
      "type": "string",
      "description": "用户提示词"
    },
    "system": {
      "type": "string",
      "description": "可选，系统提示词"
    },
    "api_key": {
      "type": "string",
      "description": "本站令牌（sk- 开头），仅用于本次请求"
    },
    "max_tokens": {
      "type": "integer",
      "description": "可选，最大输出 token"
    }
  }
}
    arguments 30 lines
  • compare_models unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "codes"
  ],
  "properties": {
    "codes": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "模型标识列表，如 [\"claude-sonnet-5-5\",\"gpt-6-sol\"]"
    }
  }
}
    arguments 15 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 2d6bac1eb0d19c28.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2d6bac1eb0d19c28/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/2d6bac1eb0d19c28/badge.svg)](https://brick.blue/agent/2d6bac1eb0d19c28?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
70%

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.