# Foundaree (remote · foundaree.com)

Find and book real people by skill, city and availability: doctors, developers, plumbers and more.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `foundaree.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/shujahmhd-foundaree/foundaree.md), [page](https://verifymcp.io/servers/shujahmhd-foundaree/foundaree)

## Channel facts

- Endpoint: `https://foundaree.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-02.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3912 tokens (~260/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (36% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Foundaree MCP server?

Foundaree is a hosted endpoint at https://foundaree.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http shujahmhd-foundaree 'https://foundaree.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "shujahmhd-foundaree": {
      "url": "https://foundaree.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shujahmhd-foundaree": {
      "type": "http",
      "url": "https://foundaree.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.shujahmhd-foundaree]
url = "https://foundaree.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shujahmhd-foundaree": {
      "type": "remote",
      "url": "https://foundaree.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shujahmhd-foundaree --url 'https://foundaree.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  shujahmhd-foundaree:
    url: "https://foundaree.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "shujahmhd-foundaree": {
      "Transport": "http",
      "Url": "https://foundaree.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add shujahmhd-foundaree -t streamable-http -u 'https://foundaree.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "shujahmhd-foundaree": {
      "type": "http",
      "url": "https://foundaree.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-01 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-29 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 78, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-26 (score 77, 0)

- [security] Tool “search_people” rewrote its description, which is the text the model reads
- [cosmetic] “find_and_ask” added an optional parameter “language”
- [cosmetic] “search_people” added an optional parameter “language”

### 2026-09-25 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-23 (score 76, 0)

- [security] Tool “get_person” rewrote its description, which is the text the model reads
- [security] Tool “search_people” rewrote its description, which is the text the model reads

## MCP tools (14)

### `my_bookings` (~97 tokens)

The user's own booking requests

List the booking requests people sent to the signed-in user: who asked, what they need, when, and whether it is still waiting for an answer. Use it when the user asks what is waiting on Foundaree, who wants to book them, or what they have not answered yet. Needs the user to have connected their Foundaree account. Lead with the ones still waiting, and offer to answer them with respond_to_booking.

### `respond_to_booking` (~105 tokens)

Accept or decline a booking request

Answer one booking request sent to the signed-in user. Get the id from my_bookings first. Always read the request back to the user and get a clear yes before calling this: it is their answer to a real person, not yours. Accepting does not arrange a time — the user still has to call them — so say that.

Input parameters:

- `answer` (string, required): What the user decided.
- `bookingId` (string, required): The request id, from my_bookings.

### `my_connection_requests` (~59 tokens)

People waiting to connect with the user

List the connection requests waiting for the signed-in user, and the ones they sent that are still pending. Use it when the user asks who wants to connect, or what is waiting on Foundaree. Offer to answer them with respond_to_connection.

### `respond_to_connection` (~92 tokens)

Accept or decline a connection request

Answer one connection request sent to the signed-in user. Get the id from my_connection_requests first. Tell the user who it is and what they wrote, and get their yes before calling this. Declining removes the request quietly; the other person is not told they were declined.

Input parameters:

- `answer` (string, required): What the user decided.
- `requestId` (string, required): The request id, from my_connection_requests.

### `set_my_availability` (~102 tokens)

Set whether the user is free for work

Change the signed-in user's availability on their Foundaree profile: available (free for work now), open_to_offers (working, but will listen), or not_looking. This is public and it changes who finds them in search, so confirm with the user before calling it. Useful when they say they have finished a job, are fully booked, or want to be found again.

Input parameters:

- `availability` (string, required): The state to set on the profile.

### `find_and_ask` (~390 tokens)

Find the right people and ask them, in one go

Hand the whole errand to Foundaree: "find me a plumber in Kochi for Saturday morning". Foundaree searches, ranks the way its website does (people free now first), sends a booking request to the best one to three, and reports who was asked. Use this instead of search_people + request_appointment when the user wants it sorted rather than a list to choose from. Needs the user’s OWN name and phone number, which they gave you, and their clear yes before calling: real people will be contacted. Each person asked calls the user back if they can take it; nothing is confirmed until they do, so say that. Keep the returned errandId and use check_errand later to see who said yes. No account needed.

Input parameters:

- `area` (string): Neighbourhood, e.g. Kakkanad. Optional.
- `howMany` (integer): How many people to ask, 1 to 3. Two is a good default: a choice without pestering.
- `language` (string): Only ask people who work in this language, e.g. Malayalam. Leave out if any language is fine.
- `location` (string): City, e.g. Kochi. Strongly recommended.
- `name` (string, required): The user's own name, as they gave it.
- `need` (string, required): What the user needs done, in a sentence or two.
- `phone` (string, required): The user's own phone number, with country code when known, e.g. +91 98470 12345. The person calls back on it.
- `when` (string, required): When they would like it, in plain words, e.g. 'Saturday morning' or 'today after 5 pm'.
- `workType` (string): local_service for trades, repairs, driving and care; professional for office work. Leave out if unsure.

### `check_errand` (~90 tokens)

See who answered an errand

Check on an errand started with find_and_ask: which of the people asked have accepted, declined or not answered yet. Use it when the user asks "did anyone get back to me?". Someone who accepted will call the user on the number they gave; Foundaree does not arrange the time.

Input parameters:

- `errandId` (string, required): The errandId that find_and_ask returned.

### `search_people` (~746 tokens)

Search people

Search public Foundaree profiles by free-text query and/or structured filters; give at least one. Free-text matches name, headline, bio, location, skills, experiences and projects. Each result carries `services` (what the person offers with prices), `languages`, `serviceAreas` (areas they cover) and `workingHours` (one entry per day, 24-hour HH:MM) when they gave them, so you can compare before booking. Each result has `updatedAt`, when the person last edited their profile: prefer recent ones when details matter, and say so when a profile is old. Among equally good matches, recently updated profiles rank a little higher. Structured filters: location (substring), area (neighbourhood substring; also matches the areas a person says they cover), language (a language they work in, e.g. Malayalam), workType (exact: local_service = blue-collar, hands-on work; professional = white-collar work), category (comma-separated trades/professions, OR semantics), availability (exact: available, open_to_offers, not_looking, unspecified), skills (comma-separated, AND semantics), lookingFor (comma-separated, AND semantics). Only the first 100 results can be paged through (offset + limit ≤ 100); add filters to narrow the search. Among people who fit equally well, founding members (Foundaree's first 150 members, `foundingMember`) come first; a better match always ranks higher. Returns JSON with a `results` array of structured people summaries. Results never include phone numbers or emails: use get_person for one profile's public contact details. Each answer has two views: the text content is the JSON described above, and the structured content is a profile-card list (`people`, `total`, `query`). In apps that support MCP Apps (ChatGPT, Claude) the cards render as Foundaree profile cards. A person with `foundareeRole` ("founder" or "team") is part of Foundaree's own team; only Foundaree sets it.

Input parameters:

- `area` (string): Optional neighbourhood filter within the city (case-insensitive substring), e.g. "Kakkanad"
- `availability` (string): Optional availability filter (exact match)
- `category` (string): Optional comma-separated trade/profession filter (OR semantics), e.g. "electrician" or "electrician,carpenter"
- `language` (string): Optional language they work in (whole name, any case), e.g. "Malayalam", "Tamil" or "Hindi"
- `limit` (integer): Maximum number of results. Defaults to 20.
- `location` (string): Optional location filter (case-insensitive substring), e.g. "Bangalore" or "San Francisco"
- `lookingFor` (string): Optional comma-separated looking-for filter (AND semantics), e.g. "cofounder" or "job,freelance"
- `offset` (integer): Pagination offset. Defaults to 0. Paging stops after the first 100 results.
- `query` (string): Optional free-text search query, e.g. "postgres engineer" or "technical co-founder"
- `skills` (string): Optional comma-separated skills filter (AND semantics), e.g. "AI,ML" or "React,TypeScript"
- `workType` (string): Optional audience filter: local_service = blue-collar jobs, hands-on work (electricians, carpenters, drivers, cleaners, carers...); professional = white-collar jobs, office and professional work (dev…

Output parameters:

- `people` (array)
- `query` (object)
- `total` (integer)

### `match_people` (~636 tokens)

Match people to a requirement

Rank public Foundaree profiles against a list of required skills — use when the user describes a need ("a co-founder who knows React and has sold to enterprises", "a dentist in Pune", "someone to rewire my kitchen in Kochi") rather than searching for a known person. Give the required skills as `skills` (or describe the need in `q`; skill terms are then derived from it and `q` also narrows candidates by full text). location, area, workType, category, availability and lookingFor are hard filters; the skills only score: score = matched ÷ required (0–1), where a listed skill counts 1 and a term found in the person's category or lookingFor counts ½. Someone with 3 of 5 skills still appears, below someone with 5; ties break on availability (available first), then founding members (Foundaree's first 150 members), then recency. When nobody matches a single skill, the filtered candidates come back with score 0 and `fallback: true` instead of an empty list. Returns JSON with `items` (each: `person`, `score`, `matchedSkills`, `missingSkills`, `profileUrl`), `total`, `requiredSkills` and `fallback`. Each answer has two views: the text content is the JSON described above, and the structured content is a profile-card list (`people`, `total`, `query`). In apps that support MCP Apps (ChatGPT, Claude) the cards render as Foundaree profile cards. A person with `foundareeRole` ("founder" or "team") is part of Foundaree's own team; only Foundaree sets it.

Input parameters:

- `area` (string): Optional neighbourhood filter within the city (case-insensitive substring), e.g. "Kakkanad"
- `availability` (string): Optional availability filter (exact match)
- `category` (string): Optional comma-separated trade/profession filter (OR semantics), e.g. "driver" or "carpenter,electrician"
- `limit` (integer): Maximum number of ranked results. Defaults to 20.
- `location` (string): Optional location filter (case-insensitive substring), e.g. "Bengaluru" or "Kochi"
- `lookingFor` (string): Optional comma-separated looking-for filter (AND semantics), e.g. "cofounder" or "job,freelance"
- `q` (string): Free-text description of the need, e.g. "someone with React and PostgreSQL experience". Used to derive skills when `skills` is absent, and as a full-text filter.
- `skills` (array): The required skills, e.g. ["React", "PostgreSQL", "Kubernetes"]. Required unless q is given.
- `workType` (string): Optional audience filter: local_service = blue-collar jobs, hands-on work (electricians, carpenters, drivers, cleaners, carers...); professional = white-collar jobs, office and professional work (dev…

Output parameters:

- `people` (array)
- `query` (object)
- `total` (integer)

### `get_person` (~393 tokens)

Get a person profile

Retrieve the full public profile for a username, including skills, experiences, projects, `services` (what they offer with prices: name, price in whole currency units or null for "ask", currency, per job/hour/day/visit/session/month, from = starting price, note), `licence` (a registration number Foundaree's admin looked up on its public register, e.g. a doctor's NMC number: body, number, checkedAt; only once verified, and then "licence" is also in `verifiedBy`), and the phone, WhatsApp and contact email (`phone`, `whatsapp`, `contactEmail`) when the person made them public. `workProof`, when at least one kind is proven, is a count, not a score: "Proof: `proven` of `total`" over GitHub, website and LinkedIn (LinkedIn has no proof yet), with the facts of each proven one: `github` (public facts of a GitHub account they proved is theirs by signing in with it: repos, stars, followers, top languages, last push, and when Foundaree read them) and `website` (their website links back to this profile). `person.updatedAt` is when they last edited the profile. Returns structured JSON with `success`, `found` and `person` fields. Each answer has two views: the text content is the JSON described above, and the structured content is a profile-card list (`people`, `total`, `query`). In apps that support MCP Apps (ChatGPT, Claude) the cards render as Foundaree profile cards. A person with `foundareeRole` ("founder" or "team") is part of Foundaree's own team; only Foundaree sets it.

Input parameters:

- `username` (string, required): Username of the person, e.g. "maya-chen"

Output parameters:

- `people` (array)
- `query` (object)
- `total` (integer)

### `search_organizations` (~171 tokens)

Search companies

Search public company and organization pages on Foundaree by name, what they do, or city: "design studios in Kochi", "a clinic in Pune", "startups building for farmers". Use it when the user needs a company or team rather than one person. Returns JSON with `items` (each: `username`, `name`, `description`, `website`, `location`, `pageUrl`) and `total`. Foundaree is new, so there may be few or none: say so rather than guessing. A company's open roles come from search_opportunities.

Input parameters:

- `limit` (integer): Maximum number of results. Defaults to 10.
- `query` (string, required): Name, kind of company, what they do, or a city, e.g. "design studio Kochi"

### `search_opportunities` (~239 tokens)

Search jobs and openings

Search public openings on Foundaree: jobs, freelance work, internships, projects, co-founder and advisory roles. Use it when the user is looking for work or a role ("React jobs in Bengaluru", "a co-founder role in fintech", "internships in design"), or asks what a company is hiring for. Matches the title, description, city and skills. Only open listings are returned unless `includeClosed` is true. Returns JSON with `items` (each: `username`, `title`, `type`, `companyUsername`, `location`, `description`, `skills`, `status`, `listingUrl`, `companyUrl`) and `total`. People apply on the listing page on Foundaree; this tool does not apply for anyone. Foundaree is new, so there may be few or none: say so rather than guessing.

Input parameters:

- `includeClosed` (boolean): Also return listings that are closed. Defaults to false.
- `limit` (integer): Maximum number of results. Defaults to 10.
- `query` (string, required): Role, skill, kind of work or city, e.g. "React developer Bengaluru"

### `create_profile_draft` (~452 tokens)

Put the user on Foundaree

Start a Foundaree profile for the user. Use it only when the user asks to join Foundaree, to be listed on it, or to create their own profile. Fill in only details the user gave about THEMSELVES: never about someone else, and never guess. Only `name` is required. Nothing is published: this saves a private draft and returns one link (finishUrl). The user opens it, checks the profile, signs in and taps Publish; until then nobody can find it. Show the user the link. It works once, for 7 days. Nobody is emailed or texted.

Input parameters:

- `area`: Neighbourhood or area they work in within the city, e.g. 'Kakkanad'.
- `availability` (string): available = free now; open_to_offers = open to work; not_looking = not looking right now.
- `bio`: A few sentences about them: experience, languages, the work they take.
- `category`: Their trade or job as a short lowercase slug, e.g. plumber, electrician, carpenter, driver, cleaner, tutor, software-engineer, designer, accountant.
- `githubUrl`: Their GitHub page (http:// or https://).
- `headline`: One short line about their work, in their words.
- `intents` (array): What they are open to.
- `linkedinUrl`: Their LinkedIn page (http:// or https://).
- `location`: Their city, e.g. 'Kochi' or 'Kochi, Kerala'.
- `lookingFor` (array): The kind of work they want, as short tags, e.g. ['weekend jobs'].
- `name` (string, required): The person's own name, as they gave it.
- `phone`: Their phone number, with the country code when they gave one. Shown only if they choose so when publishing.
- `portfolioUrl`: Their own website (http:// or https://).
- `skills` (array): Skill names, e.g. ['Pipe fitting', 'Leak repair'].
- `whatsapp`: Their WhatsApp number. Shown only if they choose so when publishing.

Output parameters:

- `expiresAt` (string): When the link stops working (ISO 8601).
- `finishUrl` (string): The link to give the user: they check the profile, sign in and publish there.
- `summary` (string): One line: whose draft it is, and that nothing is public yet.

### `request_appointment` (~323 tokens)

Ask to book a person

Send a booking request to one person on Foundaree, for the user: "book this plumber for Saturday morning", "ask this dentist for an appointment". Use it only when the user asked to book or contact that person, and only with the user's OWN name and phone number, which they gave you: never guess or reuse another number. Before calling, tell the user what you will send and to whom, and get their yes. The person sees the request on Foundaree and by email, and calls the user back on that number if they can take it; nothing is confirmed until they do, so say that to the user. Find the username with search_people or match_people first. One open request per phone number and person; a few per number a day.

Input parameters:

- `area` (string): Where the work is: the user's area or address hint, e.g. 'Kakkanad, near Infopark'. Optional.
- `name` (string, required): The user's own name, as they gave it.
- `need` (string, required): What the user needs done, in a sentence or two.
- `phone` (string, required): The user's own phone number, with country code when known, e.g. +91 98470 12345. The person calls back on it.
- `username` (string, required): Username of the person to book, from search_people, match_people or get_person.
- `when` (string, required): When they would like it, in plain words, e.g. 'Saturday morning' or 'today after 5 pm'.

Output parameters:

- `message` (string): What to tell the user.
- `person` (object)
- `sent` (boolean): True when the request was stored for the person.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/shujahmhd-foundaree/foundaree#diagnostics

## Score history

- 2026-10-02: 80
- 2026-10-01: 80
- 2026-09-30: 79
- 2026-09-29: 79
- 2026-09-28: 78
- 2026-09-27: 78
- 2026-09-26: 77
- 2026-09-25: 77
- 2026-09-24: 77
- 2026-09-23: 76
- 2026-09-22: 76
- 2026-09-21: 75
- 2026-09-20: 74
- 2026-09-19: 74

## Common questions

### What is the Foundaree MCP server?

Foundaree is an MCP server listed in the public MCP registry as io.github.shujahmhd/foundaree. Find and book real people by skill, city and availability: doctors, developers, plumbers and more. This page covers its hosted endpoint (https://foundaree.com/mcp).

### Is the Foundaree MCP server safe to use?

Foundaree scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Foundaree MCP server expose?

Foundaree exposes 14 tools: my_bookings, respond_to_booking, my_connection_requests, respond_to_connection, set_my_availability, and 9 more. Their descriptions and schemas cost roughly 3,895 tokens of context every time the server is loaded.

### Does the Foundaree MCP server require authentication?

No. We connected to Foundaree without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Foundaree MCP server still maintained?

Foundaree is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://foundaree.com/mcp
- Website: https://foundaree.com/
- Changelog RSS feed: https://verifymcp.io/servers/shujahmhd-foundaree/foundaree.xml
- Changelog JSON feed: https://verifymcp.io/servers/shujahmhd-foundaree/foundaree.json
- HTML version of this page: https://verifymcp.io/servers/shujahmhd-foundaree/foundaree