Sigao Li — personal MCP server
REMOTE · API.SIGAOLI.COM
Read-only access to Sigao Li's profile, CV and case studies. Bilingual (EN/ZH).
Available components
Last scanned (33 minutes ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 228 tokens (~76/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 Management97
- Stability observed for 29 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 4 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
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.
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 −1
- Stability: pass → 0.93 functional
- 9 Oct 26 +43
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: Authorisation 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. security
- Tool coverage: unverified → 100 ▲ functional
- 6 Oct 26 −43
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 5 Nov 2026 · Probed https://api.sigaoli.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sigaoli.com | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | dff8d528eaf59e2f1354d8855a6b07c7 |
| SANs: sigaoli.com, api.sigaoli.com, *.api.sigaoli.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.sigaoli.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sigaoli.com. | absent | 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://api.sigaoli.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.sigaoli.com/mcp | Inconclusive | 406 |
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 →
get_case_study Get case study ~78
Full text of one project case study by slug (challenge / approach / impact). Call with an unknown slug to get the list of valid slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the returned content ('en' or 'zh'). |
| slug | string | yes | Case study slug, e.g. "gisphere-llm". |
No output schema declared.
No examples provided.
get_profile Get profile ~45
Who Sigao Li is: identity, career narrative, contact links, and self-introduction.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the returned content ('en' or 'zh'). |
No output schema declared.
No examples provided.
list_experience List experience ~48
Full CV: current role, professional experience, research, education, volunteering, awards, skills, certifications.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the returned content ('en' or 'zh'). |
No output schema declared.
No examples provided.
How do I install the Sigao Li — personal MCP server server?
Sigao Li — personal MCP server is a hosted endpoint at https://api.sigaoli.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 · api.sigaoli.com
claude mcp add --transport http com-sigaoli-profile 'https://api.sigaoli.com/mcp'
What is the Sigao Li — personal MCP server server?
Sigao Li — personal MCP server is listed in the public MCP registry as com.sigaoli/profile. Read-only access to Sigao Li's profile, CV and case studies. Bilingual (EN/ZH). This page covers its hosted endpoint (https://api.sigaoli.com/mcp).
Is the Sigao Li — personal MCP server server safe to use?
Sigao Li — personal MCP server scores 75 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 Sigao Li — personal MCP server server expose?
Sigao Li — personal MCP server exposes 3 tools: get_profile, list_experience, get_case_study. Their descriptions and schemas cost roughly 171 tokens of context every time the server is loaded.
Does the Sigao Li — personal MCP server server require authentication?
No. We connected to Sigao Li — personal MCP server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sigao Li — personal MCP server server still maintained?
Sigao Li — personal MCP server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.