io.github.duiduixu/ampleMcpServer
NUGET · STERLINGXU_SAMPLEMCPSERVER · SCANNED SEP 20
生成随机数MCP Server
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 95 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 76 tokens (~38/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the io.github.duiduixu/ampleMcpServer MCP server?
io.github.duiduixu/ampleMcpServer runs locally as a NuGet package, launched with dnx sterlingxu_SampleMcpServer@0.1.1-beta --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · sterlingxu_SampleMcpServer
claude mcp add duiduixu-amplemcpserver -- dnx sterlingxu_SampleMcpServer@0.1.1-beta --yes
{
"mcpServers": {
"duiduixu-amplemcpserver": {
"command": "dnx",
"args": [
"sterlingxu_SampleMcpServer@0.1.1-beta",
"--yes"
]
}
}
} {
"servers": {
"duiduixu-amplemcpserver": {
"command": "dnx",
"args": [
"sterlingxu_SampleMcpServer@0.1.1-beta",
"--yes"
]
}
}
} codex mcp add duiduixu-amplemcpserver -- dnx sterlingxu_SampleMcpServer@0.1.1-beta --yes
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"duiduixu-amplemcpserver": {
"type": "local",
"command": [
"dnx",
"sterlingxu_SampleMcpServer@0.1.1-beta",
"--yes"
],
"enabled": true
}
}
} mcp_servers:
duiduixu-amplemcpserver:
command: "dnx"
args: ["sterlingxu_SampleMcpServer@0.1.1-beta", "--yes"] {
"McpServers": {
"duiduixu-amplemcpserver": {
"Transport": "stdio",
"Command": "dnx",
"Arguments": [
"sterlingxu_SampleMcpServer@0.1.1-beta",
"--yes"
]
}
}
} {
"mcpServers": {
"duiduixu-amplemcpserver": {
"command": "dnx",
"args": [
"sterlingxu_SampleMcpServer@0.1.1-beta",
"--yes"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 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.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed nuget/sterlingxu_SampleMcpServer@0.1.1-beta
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unreadable |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_city_weather ~33
Describes random weather in the provided city.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | Name of the city to return weather for |
No output schema declared.
No examples provided.
get_random_number ~43
Generates a random number between the specified minimum and maximum values.
| Name | Type | Req | Description |
|---|---|---|---|
| max | integer | – | Maximum value (exclusive) |
| min | integer | – | Minimum value (inclusive) |
No output schema declared.
No examples provided.
What is the io.github.duiduixu/ampleMcpServer MCP server?
io.github.duiduixu/ampleMcpServer is an MCP server listed in the public MCP registry as io.github.duiduixu/ampleMcpServer. 生成随机数MCP Server. This page covers its NuGet package (sterlingxu_SampleMcpServer).
Is the io.github.duiduixu/ampleMcpServer MCP server safe to use?
io.github.duiduixu/ampleMcpServer scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.duiduixu/ampleMcpServer MCP server expose?
io.github.duiduixu/ampleMcpServer exposes 2 tools: get_random_number, get_city_weather. Their descriptions and schemas cost roughly 76 tokens of context every time the server is loaded.
Is the io.github.duiduixu/ampleMcpServer MCP server still maintained?
io.github.duiduixu/ampleMcpServer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.