# SigLint — HTTP Message Signature Doctor (remote · huxin.online)

RFC 9421 / Web Bot Auth signature doctor: per-check verdicts, digest, freshness, signed receipt.

- Trust score: 61/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `huxin.online`: 61/100 (this document), [markdown](https://verifymcp.io/servers/online-huxin-signcheck/signcheck-mcp.md), [page](https://verifymcp.io/servers/online-huxin-signcheck/signcheck-mcp)

## Channel facts

- Endpoint: `https://huxin.online/signcheck/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 912 tokens (~228/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SigLint — HTTP Message Signature Doctor MCP server?

SigLint — HTTP Message Signature Doctor is a hosted endpoint at https://huxin.online/signcheck/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.

### Claude

```bash
claude mcp add --transport http online-huxin-signcheck 'https://huxin.online/signcheck/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "online-huxin-signcheck": {
      "url": "https://huxin.online/signcheck/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "online-huxin-signcheck": {
      "type": "http",
      "url": "https://huxin.online/signcheck/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.online-huxin-signcheck]
url = "https://huxin.online/signcheck/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "online-huxin-signcheck": {
      "type": "remote",
      "url": "https://huxin.online/signcheck/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add online-huxin-signcheck --url 'https://huxin.online/signcheck/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  online-huxin-signcheck:
    url: "https://huxin.online/signcheck/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "online-huxin-signcheck": {
      "Transport": "http",
      "Url": "https://huxin.online/signcheck/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add online-huxin-signcheck -t streamable-http -u 'https://huxin.online/signcheck/mcp'
```

### Other

```json
{
  "mcpServers": {
    "online-huxin-signcheck": {
      "type": "http",
      "url": "https://huxin.online/signcheck/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 61, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “signcheck_trial” rewrote its description, which is the text the model reads
- [cosmetic] “signcheck_trial” reworded the description of “keyid”
- [cosmetic] “signcheck_trial” reworded the description of “proof”
- [cosmetic] “signcheck_trial” made “key_jwk” optional
- [cosmetic] “signcheck_trial” made “keyid” optional
- [cosmetic] “signcheck_trial” made “nonce” optional
- [cosmetic] “signcheck_trial” made “proof” optional
- [cosmetic] “signcheck_trial” made “ts” optional

### 2026-11-19 (score 61, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 620 → 864
- [functional] New tool “signcheck_trial”

### 2026-11-17 (score 60, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “signcheck_verify” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 184 → 206
- [functional] Schema quality: fair → good

### 2026-11-16 (score 59, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional] New tool “signcheck_redeem”
- [cosmetic] “signcheck_verify” added an optional parameter “entitlement”

### 2026-11-15 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 60)

First indexed and scored.

## MCP tools (4)

### `signcheck_verify` (~286 tokens)

确定性体检一份 HTTP 消息签名样本（RFC 9421）：逐项 checks 给出缺哪个头/覆盖组件够不够/content-digest 是否对得上/created 是否新鲜/签名能否用给定公钥验过，返回 verdict 与可兑现收据。按次计费，0.002 USD/call（demo 账本，仅联调）；真实收款：19.00 CNY / 200 次提取码。先付后跑。

Input parameters:

- `entitlement` (string): signcheck_redeem 发出的 AK（提款码换来的次数包）；传了它就不用 payment
- `key_jwk` (object, required): 签名者的 Ed25519 公钥 {kty,crv,x}
- `keyid` (string, required): 已登记钥匙的 keyid（URL）
- `max_age` (integer): created 允许的最大年龄（秒）
- `nonce` (string, required)
- `payment`: X-PAYMENT 同形：dict 或 base64url(JSON)
- `proof` (string, required): 对 signcheck-mcp/v1|工具|参数摘要|ts|nonce 的 Ed25519 签名
- `request` (object, required): {method,url,headers,body_b64}
- `ts` (integer, required)

### `signcheck_redeem` (~199 tokens)

把爱发电订单上的提取码换成 AK（entitlement）：带可用次数与有效期，由卖家私钥签名，可直接用 /seller-key.jwk 自验。不收费；一张码只能换一次，AK 绑定到你这次签证明的 keyid。换到后把 entitlement 传给 signcheck_verify 即可。

Input parameters:

- `code` (string, required): 提取码（SC1.… 整段复制，别只抄一半）
- `key_jwk` (object, required): {kty,crv,x}
- `keyid` (string, required): 已登记钥匙的 keyid（AK 绑到它）
- `nonce` (string, required)
- `proof` (string, required): 对 signcheck-mcp/v1|signcheck_redeem|参数摘要|ts|nonce 的 Ed25519 签名
- `ts` (integer, required)

### `signcheck_trial` (~257 tokens)

免费试用一次：把自己的请求样本（method/url/headers/body_b64，可选 key_jwk）贴进来，跑同一套 RFC 9421 体检，返回 verdict + 通过/失败计数 + 最多 3 条失败明细（完整 checks 与可兑现收据需要提取码）。不需要注册、不需要钥匙、不需要签名、不需要付款。同一 IP 24h 一次。适合先判断「我的签名到底缺什么」。

Input parameters:

- `key_jwk` (object): 签名者的 Ed25519 公钥 {kty,crv,x}
- `keyid` (string): 可选：已登记钥匙的 keyid。给了就按这把钥匙限额度（校验更严）
- `max_age` (integer): created 允许的最大年龄（秒）
- `nonce` (string)
- `proof` (string): 可选：对 signcheck-mcp/v1|signcheck_trial|参数摘要|ts|nonce 的 Ed25519 签名
- `request` (object, required): {method,url,headers,body_b64}
- `ts` (integer)

### `signcheck_pricing` (~30 tokens)

返回当前价格、收款方、付款凭据形状与调用示例。不收费。

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/online-huxin-signcheck/signcheck-mcp#diagnostics

## Score history

- 2026-11-21: 61
- 2026-11-20: 61
- 2026-11-19: 61
- 2026-11-18: 60
- 2026-11-17: 60
- 2026-11-16: 59
- 2026-11-15: 60
- 2026-11-14: 60

## Common questions

### What is the SigLint — HTTP Message Signature Doctor MCP server?

SigLint — HTTP Message Signature Doctor is an MCP server listed in the public MCP registry as online.huxin/signcheck. RFC 9421 / Web Bot Auth signature doctor: per-check verdicts, digest, freshness, signed receipt. This page covers its hosted endpoint (https://huxin.online/signcheck/mcp).

### Is the SigLint — HTTP Message Signature Doctor MCP server safe to use?

SigLint — HTTP Message Signature Doctor scores 61 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 SigLint — HTTP Message Signature Doctor MCP server expose?

SigLint — HTTP Message Signature Doctor exposes 4 tools: signcheck_verify, signcheck_redeem, signcheck_trial, signcheck_pricing. Their descriptions and schemas cost roughly 772 tokens of context every time the server is loaded.

### Does the SigLint — HTTP Message Signature Doctor MCP server require authentication?

No. We connected to SigLint — HTTP Message Signature Doctor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SigLint — HTTP Message Signature Doctor MCP server still maintained?

SigLint — HTTP Message Signature Doctor 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 SigLint — HTTP Message Signature Doctor MCP server?

VerifyMCP ran 12 checks on SigLint — HTTP Message Signature Doctor, 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 SigLint — HTTP Message Signature Doctor: 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.

## Links

- Remote endpoint: https://huxin.online/signcheck/mcp
- Website: https://huxin.online/signcheck/
- Changelog RSS feed: https://verifymcp.io/servers/online-huxin-signcheck/signcheck-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/online-huxin-signcheck/signcheck-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/online-huxin-signcheck/signcheck-mcp.json
- HTML version of this page: https://verifymcp.io/servers/online-huxin-signcheck/signcheck-mcp
