Webhook MCP Server Registry: HTTP Discovery & AI Enrichment

Discover, enrich, register, and health-check MCP servers via a single webhook-powered API

This n8n workflow exposes a webhook-based MCP Server Registry that performs HTTP discovery from a seed list, enriches tool/resource metadata using an HTTP AI enrichment endpoint, upserts results into a central catalog, and returns action-specific reports (discover, search, register, health, or list) to your clients.

What this workflow does

When a client sends a POST request to the configured webhook endpoint, the workflow:

• Validates the request payload and builds a request context (including requestId, query, serverUrl, and tools/resources).
• Performs HTTP discovery by probing a configured seed list of MCP server URLs and collecting discovery results (with optional simulation of discovery status codes).
• Enriches metadata with an AI HTTP endpoint to improve descriptions, categories, tags, and capability flags for tools/resources.
• Upserts into a central registry by calling an HTTP registry endpoint to register or update the server, tools, resources, and metadata.
• Runs health checks using an HTTP health endpoint (including status/latency) and then logs an audit event via an HTTP logging endpoint.
• Returns a structured response tailored to the requested action: catalog list, registration result, search hits, or a health summary.

Use cases

• SaaS operators maintaining an up-to-date catalog of MCP servers and their capabilities.
• Automation engineers building a reliable MCP onboarding flow: discover → enrich → register → verify health.
• n8n users creating an internal “searchable registry” for tools and resources exposed by MCP servers.

Technical details

• n8n nodes used: Webhook, Code, HTTP Request, Wait, Respond to Webhook, plus Sticky Note.
• Integrations performed via HTTP calls: discovery endpoint, AI enrichment endpoint, registry endpoint, health endpoint, and logging/audit endpoint.

Setup: Configure the n8n webhook path and share the production webhook URL with any system that will call this Webhook MCP Server Registry API.