microservice.md

md.microservicePublished by microservice.mdOfficial publisherv0.1.0Updated Oct 30, 2026

Read your microservice catalog: MICROSERVICE.md files, contracts, and who depends on what.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP server that lets an assistant read a microservice catalog: MICROSERVICE.md files, service contracts, and dependency relationships.

What you can do
  • Read MICROSERVICE.md catalog files describing services
  • Look up service contracts
  • Trace which services depend on which others
  • No tool list is published, so exact operations are not documented
When to use it
Useful when an assistant needs context about a microservice landscape — service ownership, contracts, or dependency chains — while working on code, architecture questions, or change impact analysis.
Requirements
Remote streamable HTTP endpoint at mcp.microservice.md; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth account, so the assistant can read whatever catalog data that account can see; review what the catalog exposes before connecting. Read-only scope is implied by the description but not confirmed by a tool list.

Installation

In SourceWeft

  1. Open microservice.md in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/md.microservice%2Fcatalog/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "microservice-md": {
      "type": "http",
      "url": "https://mcp.microservice.md/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Microservice integrations

Diogenes Autonomous Microservice Gateway

Published by GitHub account stand-out-of-my-sun

Remote gateway of 71 microservices that let an assistant screen agent commands, audit crypto contracts and payments, and call Google Gemini models.

Streamable HTTPWeb executable
Finance71 toolsOct 26, 2026