Founderhood

What the Founderhood MCP server does

The Founderhood MCP server gives AI agents access to founder discovery data from Founderhood. Its intended use is finding indie founders and their listings based on geographic or topical criteria. Agents can search by city, country, category, or free-form keyword, making it suitable for requests such as finding founders in a particular location or within a particular area of interest.

The service also supports submitting listings. This allows an agent to do more than retrieve existing information: it can send a new listing to Founderhood when the surrounding application provides the required listing details. The available material does not describe moderation, update, or deletion operations.

How it works

Founderhood is provided as a remote MCP server, so an MCP-compatible agent connects to the hosted service rather than running a local repository or database. Authentication is not required according to the supplied description. No environment variables, credentials, or local installation steps are documented in the available material.

An agent can choose a search operation and provide one or more supported criteria: city, country, category, or keyword. It can also request the city list before searching, or retrieve an individual founder listing after finding it. The exact response fields, transport URL, request schemas, and error behavior are not specified.

Tools and capabilities

The Founderhood MCP server exposes the following named tools and operations:

• search_founders searches founder listings using city, country, category, or keyword criteria.
• list_cities returns the cities available for founder discovery.
• get_founder retrieves a founder listing.
• Listing submission is supported, although the supplied material does not provide the submission tool name or its input schema.

These capabilities cover basic discovery, location lookup, detail retrieval, and submission. They do not establish support for messaging founders, scheduling meetings, exporting results, or modifying existing listings.

Limitations and notes

The supplied information does not document rate limits, pagination, result ranking, response formats, transport details, or client-specific setup. It also does not state whether search supports combining multiple filters beyond the listed criteria. Treat the Founderhood MCP server as a focused directory interface rather than assuming broader founder-network features.

Because no authentication is required, deployments should still consider how submitted listings are controlled and reviewed in the consuming application. The available material confirms that listings can be submitted but does not explain validation, approval, duplicate handling, or removal.