MCP server · Enrich

enrich-so-mcp.yml

Enrich operates a first-party REMOTE MCP server at https://mcp.enrich.so/mcp. It is a Streamable-HTTP MCP endpoint (Express, CORS-open, mcp-session-id exposed) that an MCP client can POST to directly — no local install, no npx package. It is authenticated: an anonymous POST of a JSON-RPC initialize returns HTTP 401 {"error":"Authentication required. Pass API key via Bearer/x-api-key or use OAuth."}, and a POST without a session returns HTTP 400 {"error":"Invalid or missing session ID"}. The server also publishes RFC 8414 OAuth Authorization Server Metadata at https://mcp.enrich.so/.well-known/oauth-authorization-server, with dynamic client registration, PKCE (S256), refresh tokens and a single scope, mcp:tools.

Open docs → Enrich provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Enrich Type: Documentation link Transport: Host: mcp.enrich.so

Documentation

https://mcp.enrich.so/mcp

Documentation link · transport

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.