microservices.sh

NPM · @MICROSERVICES-SH/MCP · 2 COMPONENTS · SCANNED AUG 3

MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.

Available components

remote · api.microservices.sh 36 npm · @microservices-sh/mcp 81

−14 this week 81 81 Trust /100

Trust breakdown (6 categories)

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 →

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 & Transparency97

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 46 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability81

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 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

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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @microservices-sh/mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add sh-microservices-mcp -- npx -y @microservices-sh/mcp

# add to Codex CLI

codex mcp add sh-microservices-mcp -- npx -y @microservices-sh/mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sh-microservices-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@microservices-sh/mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add sh-microservices-mcp --command npx --arg -y --arg @microservices-sh/mcp

# ~/.hermes/config.yaml

mcp_servers:
  sh-microservices-mcp:
    command: "npx"
    args: ["-y", "@microservices-sh/mcp"]

// mcp.json

{
  "mcpServers": {
    "sh-microservices-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@microservices-sh/mcp"
      ]
    }
  }
}

Changelog

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.

2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
31 Jul 26 −11
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
27 Jul 26 +36
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: excellent functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
26 Jul 26 59

First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 3 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/@microservices-sh/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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
Discovery method:: attestation_endpoint

Dependencies 0 packages

0 packages in the resolved dependency tree.

MCP tools — 17 exposed · ~1,706 tokens

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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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 Output Examples

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 Output Examples

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.

Input Output Examples

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 [email protected].
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.

Input Output Examples

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 [email protected].
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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	59
27 Jul	95
28 Jul	95
30 Jul	77
31 Jul	66
1 Aug	66
2 Aug	81
3 Aug	81