MCP servers › cn.suanlinfang › suanlinfang
MCP server · registry snapshot 2026-11-12 · last checked 2026-11-12
suanlinfang MCP server
Registry name cn.suanlinfang/suanlinfang
SuanLinFang AI Capabilities — the publisher's title
by suanlinfang.cn · domain (the registry's namespace rule)Website ↗
Speech-to-text, text-to-speech, OCR and typed decision-making APIs from suanlinfang.cn. — the publisher's description
Summary
cn.suanlinfang/suanlinfang is a remote MCP server listed in the official MCP registry at version 0.1.3 (marked deprecated there), under the namespace of the domain suanlinfang.cn.
Record checks
0 of 2 record checks met · 7 do not apply
- not met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: deprecated in the registry
- Not ranked by stars: deprecated in the registry
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- a secret: X-SLF-Api-Key
- Last tested
- not tested
Tool list
Not read: It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it. So there is no tool-list size and no result from the three APIs.
Worth knowing before you connect it
- The registry marks this server deprecated.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.1.3, published 2026-11-11 (registry, as of the 2026-11-12 snapshot)
- First listed version
- 2026-11-11 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-12
- Package and repository
- checked 2026-11-12
Dead or stale signals
1 found in the records we hold
- The registry marks this entry deprecated. — MCP registry · 2026-11-12 · all servers with this fact
Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-11-09, listed on 2026-11-12 with version 0.1.3 (published 2026-11-11).
Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12.
What it is
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://suanlinfang.cn/mcp The entry also requires the header X-SLF-Api-Key.
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"suanlinfang": {
"url": "https://suanlinfang.cn/mcp",
"headers": {
"X-SLF-Api-Key": "<X-SLF-Api-Key>"
}
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"suanlinfang": {
"type": "http",
"url": "https://suanlinfang.cn/mcp",
"headers": {
"X-SLF-Api-Key": "${input:x-slf-api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "x-slf-api-key",
"description": "X-SLF-Api-Key",
"password": true
}
]
}Claude Code
claude mcp add --transport http suanlinfang https://suanlinfang.cn/mcp --header "X-SLF-Api-Key: <X-SLF-Api-Key>"
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"suanlinfang": {
"type": "streamableHttp",
"url": "https://suanlinfang.cn/mcp",
"headers": {
"X-SLF-Api-Key": "<X-SLF-Api-Key>"
},
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"suanlinfang": {
"httpUrl": "https://suanlinfang.cn/mcp",
"headers": {
"X-SLF-Api-Key": "<X-SLF-Api-Key>"
}
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.suanlinfang]
url = "https://suanlinfang.cn/mcp"
http_headers = { "X-SLF-Api-Key" = "<X-SLF-Api-Key>" }Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"suanlinfang": {
"url": "https://suanlinfang.cn/mcp",
"headers": {
"X-SLF-Api-Key": "<X-SLF-Api-Key>"
}
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://suanlinfang.cn/mcp --transport http
- Replace <X-SLF-Api-Key> with your own header values; the entry marks X-SLF-Api-Key as secret, so keep the file out of version control.
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real. The command above does not send the required header (X-SLF-Api-Key).
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
- Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.
Own host
- security.txt. No security.txt at https://suanlinfang.cn/.well-known/ (HTTP 404, 2026-11-12). Source: suanlinfang.cn/.well-known/security.txt · read 2026-11-12.
- A2A agent card. No A2A agent card at https://suanlinfang.cn/.well-known/ (HTTP 404, 2026-11-12). Source: suanlinfang.cn/.well-known/agent-card.json · read 2026-11-12.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Choosing
Record checks
Public records · not a safety rating0 of 2 record checks met · 7 do not apply
- Not ranked by downloads: deprecated in the registry
- Not ranked by stars: deprecated in the registry
- Not metRegistry entry is active and says how to run itThe registry marks this entry as deprecated.What changes this check: This check reads the registry entry's status and whether it lists a package or a remote address. Marking an entry deprecated is the publisher's own choice. The registry's documentation says a published version's metadata cannot be changed; a new server.json with a unique version string is how an entry is updated. Versioning published MCP servers
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-12. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about cn.suanlinfang/suanlinfang
Answered from the data aboveWho publishes cn.suanlinfang/suanlinfang?
The registry ties the namespace cn.suanlinfang to the domain suanlinfang.cn; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Is cn.suanlinfang/suanlinfang safe to install?
We do not rate servers as safe or unsafe. 0 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its registry entry is marked deprecated. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has cn.suanlinfang/suanlinfang been security tested?
No. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it. — the server's own choice
Required input the publisher declares: X-SLF-Api-Key (secret).
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “cn.suanlinfang/suanlinfang: MCP server record.” Data checked 2026-11-12. https://protocolprobe.com/mcp/servers/cn.suanlinfang/suanlinfang
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/cn.suanlinfang/suanlinfang)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology