The README says outright that the file in this repository is a placeholder and does not contain the MCP implementation — the working server is Explorium's hosted one. So the intended setup is a URL, not a build. That also explains the authentication split: remote connections need no key, while the Docker path does.
A connection to Explorium's Business Data Hub, which runs as a hosted MCP server. This repository holds the configuration and the Docker setup; the tools themselves live at Explorium's endpoint.
- Business matching — find a company by name, domain or business id
- Business enrichment — firmographics, technographics and broader business intelligence for a matched company
- Business events — funding rounds, office changes, hiring trends and other company developments
- Prospect discovery — find professionals and contacts inside a company
- Prospect enrichment — contact details, work history and professional profiles
- Prospect events — role changes, company moves and career milestones
For remote use, none: point a client at https://mcp.explorium.ai/mcp over Streamable HTTP, or https://mcp.explorium.ai/sse, or bridge through mcp-remote for clients that only speak stdio. No API key is required on any of those paths. Self-hosting with the repository's Dockerfile does require a key, supplied as API_ACCESS_TOKEN and obtained from admin.explorium.ai.
One command — npx -y mcp-remote https://mcp.explorium.ai/mcp