io.github.Akkshay10/MCPClientMock
NPM · MOCKSERVER-MCP
MCP server for James Bloom MockServer - create expectations, verify requests, and manage mock state
Available components
Last scanned (6 hours ago)
Scores higher than 58% of npm servers
Category Testing and QA
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency43
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 324 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 289 tokens (~48/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → 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 6 Nov 2026 · Analysed npm/mockserver-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
mockserver_clear ~47
Clear expectations and recorded requests from MockServer. Optionally filter by request matcher.
| Name | Type | Req | Description |
|---|---|---|---|
| httpRequest | object | – | Optional request matcher to clear specific expectations. If not provided, clears all. |
No output schema declared.
No examples provided.
mockserver_create_expectation ~102
Create a mock HTTP expectation on MockServer. Define request matching criteria and the response to return.
| Name | Type | Req | Description |
|---|---|---|---|
| httpRequest | object | yes | Request matching criteria (method, path, headers, body, etc.) |
| httpResponse | object | – | Response configuration |
| id | string | – | Optional expectation identifier |
| timeToLive | object | – | How long this expectation should remain active |
| times | object | – | How many times this expectation should be matched |
No output schema declared.
No examples provided.
mockserver_reset ~24
Perform a full reset of MockServer, clearing all expectations and recorded requests.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mockserver_retrieve_requests ~40
Retrieve recorded requests from MockServer. Optionally filter by request matcher.
| Name | Type | Req | Description |
|---|---|---|---|
| httpRequest | object | – | Optional request matcher to filter recorded requests |
No output schema declared.
No examples provided.
mockserver_status ~26
Get MockServer connection status and configuration. Returns host, port, and reachability.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mockserver_verify ~50
Verify that requests matching criteria were received by MockServer. Returns verification result with match count.
| Name | Type | Req | Description |
|---|---|---|---|
| httpRequest | object | yes | Request matching criteria |
| times | object | – | Expected number of matching requests |
No output schema declared.
No examples provided.
How do I install the io.github.Akkshay10/MCPClientMock MCP server?
io.github.Akkshay10/MCPClientMock runs locally as an npm package, launched with npx -y mockserver-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mockserver-mcp
claude mcp add akkshay10-mcpclientmock -- npx -y mockserver-mcp
What is the io.github.Akkshay10/MCPClientMock MCP server?
io.github.Akkshay10/MCPClientMock is an MCP server listed in the public MCP registry as io.github.Akkshay10/MCPClientMock. MCP server for James Bloom MockServer - create expectations, verify requests, and manage mock state. This page covers its npm package (mockserver-mcp).
Is the io.github.Akkshay10/MCPClientMock MCP server safe to use?
io.github.Akkshay10/MCPClientMock scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 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.Akkshay10/MCPClientMock MCP server expose?
io.github.Akkshay10/MCPClientMock exposes 6 tools: mockserver_create_expectation, mockserver_verify, mockserver_clear, mockserver_reset, mockserver_retrieve_requests, mockserver_status. Their descriptions and schemas cost roughly 289 tokens of context every time the server is loaded.
Is the io.github.Akkshay10/MCPClientMock MCP server still maintained?
io.github.Akkshay10/MCPClientMock is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Akkshay10/MCPClientMock MCP server under?
io.github.Akkshay10/MCPClientMock declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.Akkshay10/MCPClientMock MCP server?
VerifyMCP ran 16 checks on io.github.Akkshay10/MCPClientMock, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.