microservices.sh
NPM · @MICROSERVICES-SH/MCP · 2 COMPONENTS · SCANNED SEP 20
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
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 & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to microservices-sh/mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 94 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1706 tokens (~100/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_preview" implies "deploy" 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 17 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 microservices.sh MCP server?
microservices.sh runs locally as an npm package, launched with npx -y @microservices-sh/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 · @microservices-sh/mcp
claude mcp add sh-microservices-mcp -- npx -y @microservices-sh/mcp
{
"mcpServers": {
"sh-microservices-mcp": {
"command": "npx",
"args": [
"-y",
"@microservices-sh/mcp"
]
}
}
} {
"servers": {
"sh-microservices-mcp": {
"command": "npx",
"args": [
"-y",
"@microservices-sh/mcp"
]
}
}
} codex mcp add sh-microservices-mcp -- npx -y @microservices-sh/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sh-microservices-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@microservices-sh/mcp"
],
"enabled": true
}
}
} openclaw mcp add sh-microservices-mcp --command npx --arg -y --arg @microservices-sh/mcp
mcp_servers:
sh-microservices-mcp:
command: "npx"
args: ["-y", "@microservices-sh/mcp"] {
"McpServers": {
"sh-microservices-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@microservices-sh/mcp"
]
}
}
} assistant mcp add sh-microservices-mcp -t stdio -c npx -a -y @microservices-sh/mcp
{
"mcpServers": {
"sh-microservices-mcp": {
"command": "npx",
"args": [
"-y",
"@microservices-sh/mcp"
]
}
}
} 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.
- 20 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.
- 18 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 13 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.
- 11 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.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- 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 npm/@microservices-sh/mcp@0.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | microservices-sh/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/microservices-sh/mcp/.github/workflows/publish.yml@refs/tags/v0.1.3 |
| Rekor log index | 1858100881 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:213cd304fe860b4d310a2cc2ffa3cf9889e12ec3e0845d77b0cea98042cf14ecb17a807ce75fe071f70fbd9e3f9c1aa6137af6072ecdf97a9df656e87 |
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 →
check_updates Check Updates ~50
Check locked module versions against the bundled registry snapshot. Use this to identify available module updates before plan_module_upgrade.
| Name | Type | Req | Description |
|---|---|---|---|
| lock | object | – | Optional existing microservices.lock.json content to compare against known module versions. |
No output schema declared.
No examples provided.
compose_app Compose App ~118
Compose a template and selected modules into a checked app contract and lockfile plan without writing files. Use this to preview the exact app composition before generate_project or deployment planning.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Template configuration overrides for generated source, runtime bindings, or module-specific settings. |
| modules | array | – | Optional microservices.sh module ids to include, such as auth, booking, customer, payment, files, or audit-log. |
| templateId | string | – | Template id to use for app composition. Omit to use the registry default template. |
No output schema declared.
No examples provided.
create_preview_plan Create Preview Plan ~141
Create a local preview-deployment readiness plan without mutating remote state. Use this before deploy_preview to review resources, checks, errors, warnings, and required approval steps.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Template configuration overrides for generated source, runtime bindings, or module-specific settings. |
| mode | string | – | Deployment topology mode: embedded for one Worker app, service for separated service modules. |
| modules | array | – | Optional microservices.sh module ids to include, such as auth, booking, customer, payment, files, or audit-log. |
| templateId | string | – | Template id to use for app composition. Omit to use the registry default template. |
No output schema declared.
No examples provided.
deploy_preview Deploy Preview ~242
Prepare a remote preview deployment through the microservices.sh control plane. This is a mutating tool and requires confirm: preview; call create_preview_plan first and only proceed after human review.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | Actor label for audit logs, such as the agent, user, or workflow initiating the preview. |
| apiKey | string | – | Optional API key for the control plane. Prefer MICROSERVICES_API_KEY or MICROSERVICES_TOKEN in the environment. |
| apiUrl | string | – | Optional control-plane URL. Defaults to MICROSERVICES_API_URL or https://api.microservices.sh. |
| config | object | – | Template configuration overrides for generated source, runtime bindings, or module-specific settings. |
| confirm | string | yes | Required literal confirmation for this mutating preview-deployment tool. |
| modules | array | – | Optional microservices.sh module ids to include, such as auth, booking, customer, payment, files, or audit-log. |
| name | string | – | Project or deployment display name recorded in the preview deployment request. |
| templateId | string | – | Template id to use for app composition. Omit to use the registry default template. |
No output schema declared.
No examples provided.
generate_project Generate Project ~122
Generate project source files in memory for agent inspection. This tool does not write files; use it to review planned source, docs, migrations, and config before creating or editing a local project.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Template configuration overrides for generated source, runtime bindings, or module-specific settings. |
| modules | array | – | Optional microservices.sh module ids to include, such as auth, booking, customer, payment, files, or audit-log. |
| templateId | string | – | Template id to use for app composition. Omit to use the registry default template. |
No output schema declared.
No examples provided.
get_deployment_status Get Deployment Status ~122
Read a remote preview deployment status from the microservices.sh control plane. Use this after deploy_preview to poll status, inspect errors, or retrieve deployment metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Optional API key for the control plane. Prefer MICROSERVICES_API_KEY or MICROSERVICES_TOKEN in the environment. |
| apiUrl | string | – | Optional control-plane URL. Defaults to MICROSERVICES_API_URL or https://api.microservices.sh. |
| deploymentId | string | yes | Deployment id returned by deploy_preview or the microservices.sh control plane. |
No output schema declared.
No examples provided.
get_module_doc Get Module Doc ~60
Return an LLM-readable documentation page for a module, including rules, implementation notes, and agent guidance. Use this before coding against a module contract.
| Name | Type | Req | Description |
|---|---|---|---|
| moduleId | string | yes | Module id whose documentation should be returned, for example booking or payment. |
No output schema declared.
No examples provided.
get_secrets_status Get Secrets Status ~116
Report required secret names and configured/missing status for a template/module composition without exposing secret values. Use this before deployment planning or remote preview deploys.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Template configuration overrides for generated source, runtime bindings, or module-specific settings. |
| modules | array | – | Optional microservices.sh module ids to include, such as auth, booking, customer, payment, files, or audit-log. |
| templateId | string | – | Template id to use for app composition. Omit to use the registry default template. |
No output schema declared.
No examples provided.
inspect_module Inspect Module ~77
Inspect one module contract in detail, including permissions, hooks, events, resources, storage needs, and customization points. Use this before editing or adding a module so the agent understands the module boundaries.
| Name | Type | Req | Description |
|---|---|---|---|
| moduleId | string | yes | Module id returned by list_modules, for example auth, booking, customer, payment, files, or audit-log. |
No output schema declared.
No examples provided.
inspect_template Inspect Template ~63
Inspect one app template contract, including supported modules, default configuration, runtime metadata, and generation behavior. Use this before composing or generating a project from a specific template id.
| Name | Type | Req | Description |
|---|---|---|---|
| templateId | string | yes | Template id returned by list_templates, for example booking-sveltekit. |
No output schema declared.
No examples provided.
list_module_docs List Module Docs ~37
List LLM-readable documentation pages available for module implementation guidance. Use this to discover local docs before get_module_doc or before changing generated source.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_modules List Modules ~47
List available verified microservices.sh modules with ids, categories, summaries, versions, and maturity status. Use this to discover production building blocks before inspect_module, compose_app, or plan_add_module.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates List Templates ~48
List available microservices.sh app templates, including template ids and summaries. Use this before inspect_template, compose_app, generate_project, or run_checks when choosing a foundation for a new Cloudflare app.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_add_module Plan Add Module ~109
Plan an approval-gated module addition against an optional existing microservices.lock.json. This tool reports intended lockfile changes and required review gates without writing files.
| Name | Type | Req | Description |
|---|---|---|---|
| lock | object | – | Optional existing microservices.lock.json content used to calculate a safe add plan. |
| moduleId | string | – | Module id or module@version selector to add, for example payment or booking@0.1.0. |
| version | string | – | Optional explicit target version when moduleId does not include @version. |
No output schema declared.
No examples provided.
plan_module_upgrade Plan Module Upgrade ~124
Plan a module version change and report approval gates, compatibility notes, and lockfile impact. Use this before applying a module upgrade.
| Name | Type | Req | Description |
|---|---|---|---|
| lock | object | – | Optional existing microservices.lock.json content used to calculate upgrade impact. |
| moduleId | string | – | Module id or module@version selector to upgrade, for example auth or payment@0.1.0. |
| to | string | – | Optional target version. Omit to let the planner choose the latest known version. |
| version | string | – | Optional current version when it is not available from the lockfile. |
No output schema declared.
No examples provided.
run_checks Run Checks ~114
Run local contract and readiness checks for a template/module composition. Use this before deployment planning to verify module compatibility, generated artifacts, and operational guardrails.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Template configuration overrides for generated source, runtime bindings, or module-specific settings. |
| modules | array | – | Optional microservices.sh module ids to include, such as auth, booking, customer, payment, files, or audit-log. |
| templateId | string | – | Template id to use for app composition. Omit to use the registry default template. |
No output schema declared.
No examples provided.
validate_config Validate Config ~116
Validate a template, module list, and configuration object before generation or deployment. Use this to catch unsupported modules, missing settings, and invalid config before side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Template configuration overrides for generated source, runtime bindings, or module-specific settings. |
| modules | array | – | Optional microservices.sh module ids to include, such as auth, booking, customer, payment, files, or audit-log. |
| templateId | string | – | Template id to use for app composition. Omit to use the registry default template. |
No output schema declared.
No examples provided.
What is the microservices.sh MCP server?
microservices.sh is an MCP server listed in the public MCP registry as sh.microservices/mcp. MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps. This page covers its npm package (@microservices-sh/mcp).
Is the microservices.sh MCP server safe to use?
microservices.sh scores 94 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. Its build provenance is signed and verified. 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 microservices.sh MCP server expose?
microservices.sh exposes 17 tools: list_templates, inspect_template, list_modules, inspect_module, list_module_docs, and 12 more. Their descriptions and schemas cost roughly 1,706 tokens of context every time the server is loaded.
Is the microservices.sh MCP server still maintained?
microservices.sh 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.
What licence is the microservices.sh MCP server under?
microservices.sh declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.