Echoloc MCP

What echoloc-ai/echoloc-mcp MCP server does

The echoloc-ai/echoloc-mcp MCP server exposes company technographics and related intelligence to MCP-compatible agents. Its dataset covers more than 760,000 companies and tracks over 10,000 technologies. The information is derived from public job posts, which provides visibility into backend, data, cloud, and AI tooling that may not be visible in a company’s website source.

Profiles can include firmographics, hiring activity, hiring velocity, departments, leadership hires, and technology-stack context. Technology signals distinguish between tools a company is adopting, replacing, or evaluating rather than presenting only a static usage flag.

All exposed operations are read-only. Discovery methods such as initialization and tool listing do not require an API key, while tool calls consume one credit each.

How it works

The echoloc-ai/echoloc-mcp MCP server is hosted at https://api.echoloc.ai/mcp and uses stateless Streamable HTTP. Authenticate requests with the X-API-Key header; the service also accepts an Authorization: Bearer header. The remote endpoint can be configured directly in clients that support HTTP MCP connections.

The server provides three tools:

• search_companies_by_technologies finds companies associated with one or more technologies. Queries can match any or all supplied technologies, and results are ranked by usage. Matching is case-insensitive.
• get_company_by_domain looks up a domain such as walgreens.com and returns a company profile with firmographics, hiring statistics, and technology adoption context.
• list_technologies returns the technology catalog and the number of companies associated with each technology.

Setup and configuration

Create an echoloc account, obtain an API key from the API settings page, and add the remote endpoint to an MCP client. Cursor and other HTTP-capable clients can use a configuration containing the endpoint URL and X-API-Key header. Claude Code can register the endpoint with its HTTP transport configuration.

For clients that accept only stdio, the repository includes a dependency-free mcp_stdio_bridge.py script. The bridge forwards JSON-RPC requests to the hosted service and reads the API key from ECHOLOC_API_KEY. A Docker image can also run the bridge with the same environment variable.

The documented free key allows 100 requests per month. Higher limits, bulk feeds, and licensing questions are directed to echoloc support.

Tools and capabilities

The echoloc-ai/echoloc-mcp MCP server supports technology-oriented company research, including finding organizations that use a selected stack, identifying companies changing technology direction, and inspecting a known domain’s hiring and technology signals. The catalog tool can help discover supported technology names before running a company search.

Example questions include which financial-services companies are adopting Snowflake, what technology stack and hiring signals are associated with a particular domain, and which companies are replacing VMware. Direct JSON-RPC calls are also possible against the hosted endpoint.

Limitations and notes

The tools are read-only and each tool call uses one credit. The free tier is limited to 100 requests per month. The dataset is based on signals extracted from public job posts, so results represent detected hiring-related evidence rather than a guaranteed complete inventory of every technology a company uses.

The hosted service requires an API key for tool calls. Clients that cannot connect to Streamable HTTP need the included stdio bridge or Docker setup. The material does not specify a license for the repository or bridge.