Skip to main content
Glama
802,973 tools. Updated 2026-11-19 04:08

"Information about the founder of Sounora" matching MCP tools:

  • Runs one short interview with a founder about their working day. Given this interview's questions and answers so far, it returns the next question (start, work, problem, resolution, forward), following up on what they said. When the interview is complete it returns done, a summary of the day in the founder's own words, a closing line and a link that opens Underway with the debrief loaded. Use it when a founder wants to talk through their day now, in this chat. If they already know they want to film and only want it set up, use underway_set_up_recording instead.
    ConnectorNo auth
  • Turns the app's outgoing emails (sends — on by default) and/or the new sign-in device notice (newSignIn — on by default) on or off. Send either or both; the other is left as it is. Before go-live it acts at once; once live, the founder approves it in the browser (request_email_switches).
    ConnectorNo auth
  • Retrieve The Hill Kinabalu’s official public wedding venue and 2026/2027 package information, including capacity, event sizes, starting package prices, key inclusions, add-ons without prices, payment structures, and enquiry links. Use this when someone asks about weddings, wedding packages, the event venue, guest capacity, package pricing, or how to enquire. This tool does not check date availability or submit an enquiry.
    ConnectorNo auth
  • Create a German GmbH/UG incorporation case and return a secure Beglaubigt link where the founder provides their remaining personal details (date of birth, nationality, home address) and pays. The agent NEVER handles payment and NEVER asks for date of birth, nationality, or a person's home address in chat — those are collected only on the returned page. Collect in chat: the company (legal_form 'gmbh'|'ug', full `name` INCLUDING the legal-form suffix e.g. 'Velocent UG (haftungsbeschränkt)', `purpose`, `capital`, registered `address` and `business_address`), the `notarization` (its `type` — 'online' or 'offline' — is REQUIRED and has no default; optional `express` boolean; optional `preferred_timeframe` of 7, 14 or 30), the ownership structure (each shareholder's `share_percentage` and whether they are a managing director), and — for the first (founder) shareholder only — their `first_name` and `email` so Beglaubigt can send the completion link (tell the founder you will share their email with Beglaubigt for this). Share capital must be a whole number of euros and meet the legal minimum: GmbH at least 25000, UG at least 1. Share percentages must total 100. At least one shareholder must be a managing director, or a separate director must be included. Musterprotokoll (the standard template) supports at most 3 shareholders and exactly one managing director. Leave `documents` unset: Beglaubigt derives the articles type from the structure you send — one director with 1–3 shareholders gets the Musterprotokoll, anything larger gets individual (custom) articles. A notarization preferred_timeframe, if provided, must be 7, 14, or 30. Governance terms apply only when the derived articles are individual; Beglaubigt ignores them for a Musterprotokoll. You may optionally set: shareholders_meeting_quorum, shareholders_resolution_majority, significant_transactions_majority (percentages 0–100), representation_type ('joint' | 'sole' | 'section181'), majority_type ('simple' | 'two_thirds' | 'unanimous'), and notice_period_months. The optional additional_services field just records which follow-up options the founder wants information about later. It is non-binding: including it orders nothing, enrols the founder in nothing, and adds no charge — the link covers the one-time incorporation fee only. Recognised values: 'authority-registrations', 'business-liability-insurance', 'trademark-registration', 'bookkeeping', 'tax-advisor-support', 'business-address'. `package` (set at `incorporation.package`) is REQUIRED by this tool and sets the price shown on the completion page. The tiers are 'simple' | 'standard' | 'priority'. Ask the founder which one they want and send their answer — never choose for them. There is no package step on the completion page, so if you do not ask, the founder is never asked at all. Read the `packages://incorporation` resource for each tier's scope and structural limits, and tell the founder that exact prices depend on the partner tenant and are shown on the completion page before they pay — do not quote a figure yourself. Omitting the package is refused before anything is created, because omission silently bills the middle tier. Calls are NOT idempotent: every successful call creates a new incorporation case. When collecting these details, gather them conversationally across turns — one field at a time for each person — instead of asking for everything in a single message; call this tool only once all details are confirmed.
    ConnectorNo auth
  • Returns booking links for a conversation with Infinivo's founder, and optionally passes your user's details to him so he can follow up. Call this when the user wants to talk to a human, get a quote, or move forward. Offer the 15-minute fit call first; offer the paid consultation only when the user is already convinced and wants their own intake mapped. If your user wants the founder to reach out, ASK THEM FOR THEIR EMAIL FIRST and pass it as "email" — never send an address they did not give you, and never infer one. Omitting email is completely fine and still returns the links. This tool does not schedule anything. It cannot write to anyone's calendar. The links are for your user to open themselves.
    ConnectorNo auth
  • As an authenticated resident, flag one public place, thing, kind, trait, note, agreement, line, ping, or resident for founder review. The target must exist. To ask for a review of a moderation record, send target_type moderation with the record id from browse view=moderation and your reason: one open request per record at a time, and the founder's one answer shows only in your own me under review_requests. target_id is a positive id and reason is required safe text of at most 500 characters after trimming. Residents may submit 20 flags per UTC hour. The public event omits the report text. Founder resident #1 reads every report and its reason at GET /api/founder/flags, one page at a time, and marks one handled at POST /api/founder/flags/<id>/handle; both are founder-only web routes, never MCP tools. The anonymous lane stays web-only; this MCP tool always requires resident authentication. Lost? Call front_door.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    Enables running a one-person company from an MCP client by generating weekly plans, maintaining a markdown CRM pipeline, drafting investor updates, and building launch checklists as local plain-markdown files with no accounts, API keys, or cloud.
    5
    MIT

Matching MCP Connectors

  • About Bureau, the self-hosted office for AI agents: overview, FAQ search, roadmap, install.

  • Read-only search over the Founder Ventures library on bootstrapped SaaS, plus founder events.

  • As an authenticated resident, flag one public place, thing, kind, trait, note, agreement, line, ping, or resident for founder review. The target must exist. To ask for a review of a moderation record, send target_type moderation with the record id from browse view=moderation and your reason: one open request per record at a time, and the founder's one answer shows only in your own me under review_requests. target_id is a positive id and reason is required safe text of at most 500 characters after trimming. Residents may submit 20 flags per UTC hour. The public event omits the report text. Founder resident #1 reads every report and its reason at GET /api/founder/flags, one page at a time, and marks one handled at POST /api/founder/flags/<id>/handle; both are founder-only web routes, never MCP tools. The anonymous lane stays web-only; this MCP tool always requires resident authentication. Lost? Call front_door.
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • Update an application's payload and/or contact email while it's still in `draft`. **When:** founder caught something wrong after `create_application` but before `verify_email`. Also when changing the email address. **Before you call:** - Full-replace on payload: send the WHOLE `PitchApplication` object, not a patch. Read current values from `get_status` if you don't have them. - Email change resets verification: `emailVerified` goes back to false and a fresh code is sent to the NEW address. Let the founder know. **Returns:** the fresh `StatusView` — markdown by default, JSON if `responseFormat: "json"`. Same shape as `get_status`. **On error:** - `notEditable` — status is past `draft`. Nothing to update; state is locked. Read `get_status` to understand where you are. - Validation failed — payload doesn't satisfy the schema. Fix per the error message and retry.
    ConnectorNo auth
  • Consume the 6-digit code the founder received and start the research pipeline. **When:** after `create_application`, and ideally after the deck has been uploaded over plain HTTP (see the `curl` printed by `create_application`). Founder has read the code from their inbox. **Before you call:** - CONFIRM you have the right code from the founder (not guessing, not stale). Once this succeeds, research starts and is irreversible. - If deck parsing is still pending, that's fine — research auto-defers and dispatches when the deck resolves. Don't wait, don't re-verify. **Returns:** `status: researching` + whether research was dispatched now or deferred on the deck. **On error:** - `wrong code` — response includes attempts-remaining. Ask the founder to check their inbox again. If the error says the code is invalidated, call `resend_verification` for a new one. - `no active code` — they never received one, or it expired. Call `resend_verification`. - Already verified — idempotent success; returns current status. Don't retry in a loop.
    ConnectorNo auth
  • Runs one finished relay run (done, failed or dead — its id from relay_runs) again, every action of the relay as it is now; an action that already succeeded finds its own earlier work (a payment's grants are given once, an email isn't sent twice), while an address a call_url action calls is called again. In Development it runs at once. In Live (env live) it asks the founder to approve it in their browser — the page says what the relay does, including that it moves money or calls an address — and approving it runs it, once (live_action_status with wait: true reads the outcome). A run that is still queued or running, or an unsigned event that would grant, is refused.
    Connector
    Destructive
    No auth
  • Returns the applications to the Tbilisi Architecture Service for a parcel or a period, newest first: building permits, project approvals, signs, fences, and requests for public information. Give a cadastral code (01.18.04.020.005), a period of at most 31 days, or both. A period of more than 500 applications fails, and Tbilisi registers about 70 each working day, so ask for a week at most. Each application has its number, address, status, category, class, and stages. Read the decision with permits_get_application. Tbilisi only. Texts are in Georgian. Data from TAS.
    ConnectorNo auth
  • Use this when you need to know whose workspace this connection acts on and what it may do: the workspace name, plan tier and size (the contacts the plan holds), how it is billed, how many contacts count toward the limit right now, and the scopes the connection holds. Also use it when the founder asks about their plan, its limits or what it includes. Not for audience numbers in a report (use `get_audience_stats`) or for the projects (use `list_projects`). `complimentary` is true for a plan given rather than sold. It also tells you the plan up front, read from the plan registry: `limits` (contact size, campaign emails a month, projects), `usage` against them (including `hidden_contacts`, saved contacts held past the size), and `includes` (whether the plan sends broadcasts, runs automations, saves custom segments, shows where signups came from, lists the page in search engines and removes the badge). Use it to mention a limit before the founder hits it, never to guess one. `upgrade_url` opens this workspace's plan page. When contacts are held there is also an `upgrade` object with the plan that holds them. Give the link when the founder asks about plans or something is blocked, and say which plan removes it and why it matters for what they asked. Never quote a price or a limit that this result does not state. `key.mode` says how you are connected. `agent` means a signed-in person approved this app (OAuth, as in ChatGPT and Claude), so "me" is that person and tools that default to them (like `send_test_broadcast`) work without asking for an address. Any other mode is an API key with nobody behind it. `key.project` tells you whether the key is pinned to a single project, in which case every other tool can only reach that one. `usage.contacts` is the BILLABLE count, which excludes test-mode and flagged contacts, so do not use it to report how many signups there are.
    ConnectorAPI key
  • Use this when the founder asks how many signups they have, how a week or a launch is going, how many verified their email, where signups come from, or how well the launch page converts. Not for finding or listing people (use `search_audience`), for the top referrers (use `get_leaderboard`), or for the plan's billable contact count (use `get_workspace`). It returns total audience, signups today and over a trailing window, how many verified their email (`confirmed`: they clicked the link we sent to verify their address; everyone who joins is subscribed either way), and the breakdown by subscription status, pipeline stage and first-touch source. Every number comes from precomputed counters, so it costs a handful of indexed row reads no matter how large the audience is. To count, use this rather than paging through `search_audience`: that is capped at 50 rows per call and wrong as soon as there is a second page. `total` counts live contacts and excludes test-mode and flagged-for-review rows, so it can differ from the billable count in `get_workspace`. `referred` counts signups that arrived through somebody's referral link. `views` is how many times the launch page was viewed over the same window, and `conversion` is the percentage of those visits that became signups on that page (`page_signups`, the numerator: signups from an import, the API or an embed have no visit behind them and are not counted). It is null, with `conversion_note`, when there were no views or more signups than views. The plan sets limits, the same ones the Analytics page has. `days` is capped at how far back the plan's analytics history reaches: a longer request is shortened, and `signups.window_days` is the window actually used. `source` is null unless the plan includes advanced analytics. `total` counts every saved contact, including any held past the plan's size; `hidden_contacts` is how many of those the founder cannot see or use until the plan holds them. When the plan limits any of that, the answer is still returned, with a reason beside the missing part (`source_unavailable_reason`, `window_limited_reason`, `hidden_contacts_reason`) and one `upgrade` object: the lowest plan that clears all of them, with its link. Say plainly what is missing and why it matters for what the founder asked, and give them the link. Do not mention an upgrade when there is no `upgrade` object.
    ConnectorAPI key
  • Consume the 6-digit code the founder received and start the research pipeline. **When:** after `create_application`, and ideally after the deck has been uploaded over plain HTTP (see the `curl` printed by `create_application`). Founder has read the code from their inbox. **Before you call:** - CONFIRM you have the right code from the founder (not guessing, not stale). Once this succeeds, research starts and is irreversible. - If deck parsing is still pending, that's fine — research auto-defers and dispatches when the deck resolves. Don't wait, don't re-verify. **Returns:** `status: researching` + whether research was dispatched now or deferred on the deck. **On error:** - `wrong code` — response includes attempts-remaining. Ask the founder to check their inbox again. If the error says the code is invalidated, call `resend_verification` for a new one. - `no active code` — they never received one, or it expired. Call `resend_verification`. - Already verified — idempotent success; returns current status. Don't retry in a loop.
    ConnectorNo auth
  • Update an application's payload and/or contact email while it's still in `draft`. **When:** founder caught something wrong after `create_application` but before `verify_email`. Also when changing the email address. **Before you call:** - Full-replace on payload: send the WHOLE `PitchApplication` object, not a patch. Read current values from `get_status` if you don't have them. - Email change resets verification: `emailVerified` goes back to false and a fresh code is sent to the NEW address. Let the founder know. **Returns:** the fresh `StatusView` — markdown by default, JSON if `responseFormat: "json"`. Same shape as `get_status`. **On error:** - `notEditable` — status is past `draft`. Nothing to update; state is locked. Read `get_status` to understand where you are. - Validation failed — payload doesn't satisfy the schema. Fix per the error message and retry.
    ConnectorNo auth
  • Resolve one drafted marketing output in the founder's review queue: action 'ship' marks it done or posted WITHOUT publishing anywhere, action 'skip' dismisses it. WHEN: call 'ship' the moment the founder confirms the content is actually out, with their go and never on your own; call 'skip' when they decide against it. Posting is the human's decision; reporting the outcome is yours, and it is not optional, because an unreported result leaves the record blind to what the work earned. Report only what is true: a draft you have written is not a draft that went out. This never posts to a channel: real publishing is a separate, human-approved egress step. Free; requires the 'act' scope and Founder tier.
    Connector
    Destructive
    No auth
  • Resolve one drafted marketing output in the founder's review queue: action 'ship' marks it done or posted WITHOUT publishing anywhere, action 'skip' dismisses it. WHEN: call 'ship' the moment the founder confirms the content is actually out, with their go and never on your own; call 'skip' when they decide against it. Posting is the human's decision; reporting the outcome is yours, and it is not optional, because an unreported result leaves the record blind to what the work earned. Report only what is true: a draft you have written is not a draft that went out. This never posts to a channel: real publishing is a separate, human-approved egress step. Free; requires the 'act' scope and Founder tier.
    Connector
    Destructive
    No auth
  • Use this after each user message that contains anything worth knowing later, even if the user does not say 'remember this'. Default to saving: a missed memory costs far more than a redundant one, so when in doubt, save. Each of these is a trigger on its own: the user makes a decision, states a preference, gives a fact about a person, project, company, or tool, sets a plan or commitment, makes a correction, or reports progress or an outcome. Save one concise, self-contained memory per call, written so it makes sense on its own later, with the exact wording, numbers, dates, names, and identifiers the user gave; several facts in one message mean several calls. Record what the user actually said, not your inference. There is no update tool: to supersede outdated information, save the corrected fact and say what it replaces. Never save passwords, API keys, tokens or other credentials, payment card numbers, government ID numbers, or protected health information, and never save whole transcripts. Writes one memory to the user's OAuth-selected vault. If the user asks what was saved, answer truthfully from the tool result.
    ConnectorNo auth
  • List the achievement badges you have unlocked as a founder on TrendIdea and the milestones behind them. Use it to see progress and which milestones are still open. Read-only and free; takes no parameters and scopes to your own account.
    ConnectorNo auth