Foundaree is an MCP server with 27 tools an agent can call, among them book, check, check_errand. It answers at https://foundaree.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 23 September 2026; the last check, on 6 November 2026, succeeded.
Find and book real people by skill, city and availability: doctors, developers, plumbers and more.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
book | Send a booking or order to one person or business on Foundaree, for the user: "book this salon for Saturday 4 pm", "order 2 kg potatoes from this shop", "book this plumber tomorrow morning". Use `kind` and `username` from find. A business m Inputs: name, phone, need, when, area, items |
check | One place to follow up. With a `bookingId` from book: whether the business accepted, declined or finished it. With an `errandId` from find_and_ask: who has accepted, declined or not answered. Without either, when the user connected their Fo Inputs: bookingId, errandId |
check_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; Fo Inputs: errandId |
create_profile_draft | 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. On Inputs: name, category, headline, bio, location, area |
create_qr_code | Make a free dynamic QR code on Foundaree for the signed-in user. The QR holds a fixed Foundaree link (foundaree.com/r/...), so the user can change where it goes later without printing it again. Use it when the user wants a QR code for a men Inputs: name, link |
delete_qr_code | Delete one of the signed-in user's QR codes. Printed copies stop working for good: scans show "no longer active". This cannot be undone. Always warn the user and get a clear yes first, and suggest pausing it instead (update_qr_code with sta Inputs: id |
find | The one search for everything on Foundaree: people and home services (plumber, electrician, tutor, home nurse, driver), delivery (grocery and food riders, couriers, 10-minute delivery store staff), farm products (home-grown vegetables from Inputs: need, place, area, kind, limit |
find_and_ask | 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. Inputs: name, phone, need, when, location, area |
forget | Delete one of the user's saved notes from Foundaree Memory, so no AI sees it again. Get the id from recall. Use it when the user asks you to forget something, or a note is wrong or out of date. Inputs: id |
get | Full details of one result from find: a person (skills, services with prices, areas, hours, verified badges, and public phone/WhatsApp when they chose to show them), a business (what they do, area, services or products with prices, opening Inputs: kind, username |
get_person | 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 for ser Inputs: username |
match_people | 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 sea Inputs: skills, q, location, area, availability, workType |
my_bookings | 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 n |
my_connection_requests | 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. |
my_qr_codes | List the signed-in user's Foundaree QR codes with where each one goes, whether it is working or paused, and how many times it was scanned. Give an id to see one code in detail: its image, scans for the last 7 and 30 days, phone types, and e Inputs: id, search |
recall | Read the user's Foundaree Memory: notes they saved for their AIs from any assistant. Call it at the start of a task where their preferences or facts would help (writing in their style, their business details, their audience), or when they a Inputs: query, topic, limit |
remember | Save something the user wants every AI to know, in their Foundaree Memory: preferences, facts about them or their business, how they like things written ("my shop opens 9 to 7", "write in a friendly, short style", "my audience is small shop Inputs: note, topic |
request_appointment | 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 n Inputs: name, phone, need, when, area, username |
respond_to_booking | 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 a Inputs: bookingId, answer |
respond_to_connection | 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 per Inputs: requestId, answer |
search_opportunities | 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 Inputs: query, includeClosed, limit |
search_organizations | 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. R Inputs: query, limit |
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 Inputs: query, location, area, language, workType, category |
set_my_availability | 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 Inputs: availability |
update_memory | Change one of the user's saved notes when a fact or preference changes ("we now open at 10"). Get the id from recall. Prefer this to saving a second, conflicting note. Inputs: id, note, topic |
update_qr_code | Change one of the signed-in user's QR codes: point it to a new link, rename it, pause it or switch it back on. The printed QR stays exactly the same; the next scan opens the new link. A paused QR shows a "paused" page instead of the link un Inputs: id, link, name, status |
use_service | Call one operation of a partner company's mini app on Foundaree (a cab company, delivery app or shop with its own system): find lists them under `miniApps`, get { kind: "mini_app", username: slug } shows each operation and its fields. Pass Inputs: app, operation, input |
Every block below points at https://foundaree.com/mcp. Pick your client and copy.
claude mcp add --transport http foundaree https://foundaree.com/mcp
{
"mcpServers": {
"foundaree": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://foundaree.com/mcp"]
}
}
}{
"mcpServers": {
"foundaree": {
"url": "https://foundaree.com/mcp"
}
}
}{
"servers": {
"foundaree": {
"type": "http",
"url": "https://foundaree.com/mcp"
}
}
}{
"context_servers": {
"foundaree": {
"url": "https://foundaree.com/mcp"
}
}
}{
"mcpServers": {
"foundaree": {
"serverUrl": "https://foundaree.com/mcp"
}
}
}{
"mcpServers": {
"foundaree": {
"url": "https://foundaree.com/mcp"
}
}
}name: Foundaree
version: 0.0.1
schema: v1
mcpServers:
- name: Foundaree
type: streamable-http
url: https://foundaree.com/mcp{
"mcpServers": {
"foundaree": {
"httpUrl": "https://foundaree.com/mcp"
}
}
}{
"mcpServers": {
"foundaree": {
"type": "http",
"url": "https://foundaree.com/mcp"
}
}
}{
"mcpServers": {
"foundaree": {
"url": "https://foundaree.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Ffoundaree.com%2Fmcp&type=streamable_http&id=foundaree&name=Foundaree
It answered our last check on 6 November 2026 in 858 ms. Over 4 checks since 23 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
27, as returned by the server's own tools/list on 11 November 2026: book, check, check_errand, create_profile_draft, create_qr_code, delete_qr_code, find, find_and_ask, and 19 more.
It answered our last check on 6 November 2026 in 858 ms. Over 4 checks since 23 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://foundaree.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.shujahmhd. Endpoint host: foundaree.com. ARD identifier: urn:air:io.github.shujahmhd:mcp:foundaree.
First indexed 19 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.