io.github.mrfentmen/microcks-mcp
NPM · MICROCKS-MCP
MCP server for Microcks: services, import job MCP: real tools for real work.
Available components
Last scanned (23 hours ago)
Scores higher than 32% 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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1257 tokens (~36/item across 34 items; 34 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_service" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 34 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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.
- 8 Nov 26 63
First indexed and scored.
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 21 Nov 2026 · Analysed npm/microcks-mcp@1.0.0
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 | 31 |
| 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 →
activate_job ~29
Activate an import job so it runs on its schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Import job id. |
No output schema declared.
No examples provided.
count_services ~16
Count the services registered in Microcks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
count_test_results ~34
Count how many conformance tests have been recorded for a service.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | Microcks service id. |
No output schema declared.
No examples provided.
create_job ~92
Create an import job that regularly imports API artifacts from a Git repository.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether the job runs on schedule. |
| branch | string | – | Branch to import, default 'main'. |
| frequency | string | – | Cron-like import frequency, e.g. '0 0 * * *'. |
| name | string | yes | Human-readable job name. |
| repository | string | yes | Git repository URL. |
No output schema declared.
No examples provided.
create_secret ~46
Create a secret that import jobs and tests can reference.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description. |
| name | string | yes | Secret name. |
| value | string | yes | Secret value. |
No output schema declared.
No examples provided.
create_test ~65
Run a conformance test against a deployed endpoint for one Microcks service.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | Microcks service id to test. |
| testEndpoint | string | yes | Base URL of the deployed API to test against. |
| timeout | integer | – | Test timeout in milliseconds. |
No output schema declared.
No examples provided.
delete_job ~34
Delete an import job. Destructive: the job stops importing artifacts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Import job id to delete. |
No output schema declared.
No examples provided.
delete_secret ~34
Delete a Microcks secret. Destructive: anything referencing it will fail.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Secret id to delete. |
No output schema declared.
No examples provided.
delete_service ~40
Delete a service from Microcks. Destructive: the mock endpoints for this service stop working.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Microcks service id to delete. |
No output schema declared.
No examples provided.
export_snapshot ~19
Export the whole Microcks repository as a YAML snapshot.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_conformance_aggregate ~24
Read the aggregate conformance metrics for the whole Microcks instance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_features_config ~26
Read which optional Microcks features are enabled (async, AI copilot, …).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_global_invocations ~33
Read aggregated invocation statistics for a given day.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | Day as a Unix timestamp (seconds). |
No output schema declared.
No examples provided.
get_job ~31
Get one import job by id, including its last execution status.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Import job id. |
No output schema declared.
No examples provided.
get_latest_global_invocations ~20
Read invocation statistics for the most recent days.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_service ~38
Get one Microcks service by its id, including type, version and labels.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Microcks service id (a UUID). |
No output schema declared.
No examples provided.
get_service_conformance ~30
Read conformance metrics for one service.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | Microcks service id. |
No output schema declared.
No examples provided.
get_service_invocations ~40
Read invocation statistics for one service name and version.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceName | string | yes | Service name. |
| serviceVersion | string | yes | Service version. |
No output schema declared.
No examples provided.
get_top_invocations ~48
List the most-invoked services for a day.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | Day as a Unix timestamp (seconds). |
| limit | integer | – | Maximum number of services to return. |
No output schema declared.
No examples provided.
import_snapshot ~44
Import a Microcks snapshot. Pass the YAML/JSON document itself, not a file path.
| Name | Type | Req | Description |
|---|---|---|---|
| snapshot | string | yes | Snapshot content (YAML or JSON) to import. |
No output schema declared.
No examples provided.
latest_test_results ~21
Show the most recent conformance test results across every service.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_jobs ~23
List the import jobs that pull API definitions from Git repositories into Microcks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_resources ~50
Fetch a stored artifact by name (openapi.yaml, postman.json, …) exactly as Microcks serves it.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Resource file name, e.g. 'openapi.yaml'. |
No output schema declared.
No examples provided.
list_secrets ~23
List the secrets stored in Microcks (names only, never values).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_service_labels ~21
List every label key already used by services in Microcks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_service_resources ~30
List the artifact resources attached to one service.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | Microcks service id. |
No output schema declared.
No examples provided.
list_services ~71
List the APIs and services mocked by this Microcks instance, newest first. Optional filters: name and labels (comma-separated key=value pairs).
| Name | Type | Req | Description |
|---|---|---|---|
| labels | string | – | Filter by labels, e.g. "domain=payments,status=stable". |
| name | string | – | Filter by service name (substring match). |
No output schema declared.
No examples provided.
list_test_results ~32
List the conformance test results recorded for a service.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | Microcks service id. |
No output schema declared.
No examples provided.
search_services ~40
Search Microcks services by name. Use this when you only know part of the name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name or partial name to search for. |
No output schema declared.
No examples provided.
start_job ~28
Start an import job immediately, outside its schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Import job id. |
No output schema declared.
No examples provided.
stop_job ~28
Stop an import job so it no longer runs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Import job id. |
No output schema declared.
No examples provided.
update_job ~50
Update an import job. Microcks uses POST (not PUT) for job updates.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Import job id. |
| job | object | yes | Full job object with the fields to change. |
No output schema declared.
No examples provided.
update_secret ~47
Replace the value of an existing Microcks secret.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional new description. |
| id | string | yes | Secret id. |
| value | string | yes | New secret value. |
No output schema declared.
No examples provided.
update_service_metadata ~50
Replace the metadata of a service (labels, annotations and similar key/value data).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Microcks service id. |
| metadata | object | yes | Metadata object to store on the service. |
No output schema declared.
No examples provided.
How do I install the io.github.mrfentmen/microcks-mcp server?
io.github.mrfentmen/microcks-mcp runs locally as an npm package, launched with npx -y microcks-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 · microcks-mcp
claude mcp add mrfentmen-microcks-mcp -- npx -y microcks-mcp
What is the io.github.mrfentmen/microcks-mcp server?
io.github.mrfentmen/microcks-mcp is listed in the public MCP registry as io.github.mrfentmen/microcks-mcp. MCP server for Microcks: services, import job MCP: real tools for real work. This page covers its npm package (microcks-mcp).
Is the io.github.mrfentmen/microcks-mcp server safe to use?
io.github.mrfentmen/microcks-mcp scores 63 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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.mrfentmen/microcks-mcp server expose?
io.github.mrfentmen/microcks-mcp exposes 34 tools: list_services, search_services, count_services, list_service_labels, get_service, and 29 more. Their descriptions and schemas cost roughly 1,257 tokens of context every time the server is loaded.
Is the io.github.mrfentmen/microcks-mcp server still maintained?
io.github.mrfentmen/microcks-mcp 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 licence is the io.github.mrfentmen/microcks-mcp server under?
io.github.mrfentmen/microcks-mcp 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.mrfentmen/microcks-mcp server?
VerifyMCP ran 15 checks on io.github.mrfentmen/microcks-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.mrfentmen/microcks-mcp: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.