signcheck
Registry code: b61166b956ecedf8
确定性 HTTP 消息签名体检。先调 signcheck_pricing 看价格;有爱发电提取码就先调 signcheck_redeem 换 AK(entitlement),没有就按次付款(payment)。带 proof 调 signcheck_verify。
- endpoint
- https://huxin.online/signcheck/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 signcheck live?
- Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
- Is signcheck free to use?
- Not measured yet.
- What tools does signcheck have?
- 3 tools: signcheck_redeem, signcheck_verify, signcheck_pricing.
- Is signcheck 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.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
signcheck_redeem unknown never probed
把爱发电订单上的提取码换成 AK(entitlement):带可用次数与有效期,由卖家私钥签名,可直接用 /seller-key.jwk 自验。不收费;一张码只能换一次,AK 绑定到你这次签证明的 keyid。换到后把 entitlement 传给 signcheck_verify 即可。
{ "type": "object", "required": [ "code", "keyid", "key_jwk", "proof", "ts", "nonce" ], "properties": { "ts": { "type": "integer" }, "code": { "type": "string", "description": "提取码(SC1.… 整段复制,别只抄一半)" }, "keyid": { "type": "string", "description": "已登记钥匙的 keyid(AK 绑到它)" }, "nonce": { "type": "string" }, "proof": { "type": "string", "description": "对 signcheck-mcp/v1|signcheck_redeem|参数摘要|ts|nonce 的 Ed25519 签名" }, "key_jwk": { "type": "object", "description": "{kty,crv,x}" } } }arguments 35 linessigncheck_verify unknown never probed
确定性体检一份 HTTP 消息签名样本(RFC 9421):逐项 checks 给出缺哪个头/覆盖组件够不够/content-digest 是否对得上/created 是否新鲜/签名能否用给定公钥验过,返回 verdict 与可兑现收据。按次计费,0.002 USD/call,先付后跑。
{ "type": "object", "required": [ "request", "key_jwk", "keyid", "proof", "ts", "nonce" ], "properties": { "ts": { "type": "integer" }, "keyid": { "type": "string", "description": "已登记钥匙的 keyid(URL)" }, "nonce": { "type": "string" }, "proof": { "type": "string", "description": "对 signcheck-mcp/v1|工具|参数摘要|ts|nonce 的 Ed25519 签名" }, "key_jwk": { "type": "object", "description": "签名者的 Ed25519 公钥 {kty,crv,x}" }, "max_age": { "type": "integer", "description": "created 允许的最大年龄(秒)" }, "payment": { "description": "X-PAYMENT 同形:dict 或 base64url(JSON)" }, "request": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string" }, "method": { "type": "string" }, "headers": { "type": "object" }, "body_b64": { "type": "string" } }, "description": "{method,url,headers,body_b64}" }, "entitlement": { "type": "string", "description": "signcheck_redeem 发出的 AK(提款码换来的次数包);传了它就不用 payment" } } }arguments 63 linessigncheck_pricing unknown never probed
返回当前价格、收款方、付款凭据形状与调用示例。不收费。
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb61166b956ecedf8.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b61166b956ecedf8/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b61166b956ecedf8?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.