_ registry / mcp streamable-http · checked 3h ago

fundz-mcp-server

https://mcp-app.fundz.net

Registry code: 94ed543b48f2f39f

api record

Fundz is verified event intelligence on companies: funding rounds (including SEC Form D raises that never get a press release), executive moves and open seats, acquisitions, contracts, product launches, hiring, office expansions and permits, layoffs (WARN), SEC filings and their full text, plus the user's own scored daily leads, contacts and LinkedIn network. Results are read against the targeting and plan on the user's Fundz account. Sign in to Fundz when prompted; a Pro or Strategic plan is required.

An open-ended question about the user's day or what changed ("anything new?", "catch me up",…

endpoint
https://mcp-app.fundz.net
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fundz-mcp-server live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is fundz-mcp-server free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does fundz-mcp-server have?
42 tools: get_engage_opportunities, get_contact_reveal_quota, search_office_permits, search_executive_changes, remove_from_watchlist, get_investor_profile, pick_best_contact, search_raised_and_hiring, ….
Is fundz-mcp-server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.5%· all time 99.5%

latency
1,076ms

last good check

priced tools
0

of 42 tools

_ answered our checks, 90 days 222 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • get daily scored sales leads
  • search funding rounds and acquisitions
  • find executive changes
  • get company contacts
  • look up investor profiles
takes → gives
text → data
tools
20 reads5 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 42 tools
42 auth-required 42 of 42 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_engage_opportunities auth-required 16h ago

    Engage opportunities: recent LinkedIn posts by people in the user's OWN network (or at their target accounts) about a company with a fresh Fundz event, each with why it matched, the post link, a suggested DM and comment in the user's voice, and its status (delivered, contacted, replied, booked). Same list as app.fundz.net/engage. Needs Engage set up (LinkedIn connections uploaded). Use with get_daily_leads (icp: "all") for one deduplicated account list across every ICP plus warm network paths. Never send a DM or comment for the user; show the draft and let them post it.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 90,
          "minimum": 1,
          "description": "How far back, in days (default 14, max 90)."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max opportunities (default 20)."
        },
        "status": {
          "enum": [
            "open",
            "all"
          ],
          "type": "string",
          "description": "\"open\" (default) = not yet contacted or dismissed; \"all\" includes contacted, replied, booked and dismissed."
        }
      }
    }
    arguments 26 lines
  • get_contact_reveal_quota reads auth-required 27h ago

    How many contact reveals the user has left this month, their monthly cap, and the upgrade link if they are out.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • search_office_permits auth-required 20h ago

    Office build-out permits, the Permits tab of app.fundz.net/office-expansions: commercial tenant build-out, alteration and new-building permits from city records in New York, Los Angeles, Chicago, Boston, San Francisco and Seattle, with the named tenant (private and public companies), address, estimated build-out cost, permit status and a Fundz company link when matched. A permit is usually pulled 30 to 90 days after a lease is signed, so it is an early sign a company is adding space and about to hire. By default only permits that name a tenant or owner-occupier, cost $250K or more, and are not food, retail or salon fit-outs or certificates of occupancy (finished work) are returned; set min_cost, include_consumer or include_completed to widen. Use together with search_office_expansions (SEC 8-K leases, public companies, any geography) for the full expansion picture. Filter by city, state, company, work type, minimum cost and filing date. Page through every match with page; use since to get only permits filed on or after a date.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "city": {
          "type": "string",
          "description": "One or more of NYC, SF, LA, CHI, BOS, SEA or the city name, comma-separated. Default: all six."
        },
        "days": {
          "type": "number",
          "description": "Only permits filed in the last N days (default 60)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). The reply ends with the total and next_page when there are more."
        },
        "sort": {
          "type": "string",
          "description": "\"newest\" (default) or \"cost\" (largest build-out first)"
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only permits filed on or after this ISO date, e.g. \"2026-10-01\". Overrides days."
        },
        "state": {
          "type": "string",
          "description": "US state 2-letter code(s), comma-separated, e.g. \"NY, MA\""
        },
        "min_cost": {
          "type": "number",
          "description": "Minimum estimated build-out cost in USD. Default 250000 (smaller permits are rarely an expansion signal); set 0 or 1 to see every size. Not applied by default when company_name is given."
        },
        "work_type": {
          "type": "string",
          "description": "One or more of: tenant_improvement, new_building, alteration, fitout, other (comma-separated)"
        },
        "company_name": {
          "type": "string",
          "description": "Tenant, owner or applicant name (partial, case-insensitive)"
        },
        "matched_only": {
          "type": "boolean",
          "description": "Only permits matched to a Fundz company profile"
        },
        "include_unnamed": {
          "type": "boolean",
          "description": "Also return permits that name no tenant (landlord or developer work). Default false."
        },
        "include_consumer": {
          "type": "boolean",
          "description": "Also return cafe, restaurant, retail, salon, gym and hotel fit-outs and food-service vendors. Default false: a coffee shop build-out is not a hiring signal."
        },
        "include_completed": {
          "type": "boolean",
          "description": "Also return certificates of occupancy (the work is finished, not starting). Default false."
        }
      }
    }
    arguments 62 lines
  • search_executive_changes reads auth-required 6h ago

    Find executive appointments and departures. Search by role (CEO, CTO, CFO, etc.), change type (Appointment/Departure), company name, and date range. Set open_seats_only for officer seats that just opened at public companies: an 8-K departure where the filing names no permanent successor (exec search, recruiting and interim placements). Set source "sec_form3" for new officers taken from their own SEC Form 3 filing. Set source "job_posting" for C-level, president and general counsel seats that private companies are advertising on their own job boards (seats that never reach an SEC filing).

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Number of days to look back (e.g., 7, 30, 60)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only results Fundz added on or after this ISO date, e.g. \"2026-10-01\" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new."
        },
        "source": {
          "type": "string",
          "description": "Only hires from this source. \"sec_form3\" = new officers from their own SEC Form 3 filing (often roles below the C-suite that press releases miss). \"job_posting\" = open C-level / president / general counsel seats posted on private companies' own job boards (uses days up to 120, page and limit; other filters are ignored)."
        },
        "industry": {
          "type": "string",
          "description": "Industry title, e.g. \"Information Technology\""
        },
        "keywords": {
          "type": "string",
          "description": "Free-text keywords matched against title/description (comma-separated for several)"
        },
        "location": {
          "type": "string",
          "description": "City, state or country title, e.g. \"Texas\""
        },
        "role_type": {
          "type": "string",
          "description": "Executive role (e.g., \"CEO\", \"CTO\", \"CFO\", \"CMO\", \"COO\", \"VP\")"
        },
        "change_type": {
          "type": "string",
          "description": "Type of change: \"Appointment\" or \"Departure\""
        },
        "company_name": {
          "type": "string",
          "description": "Filter by company name"
        },
        "saved_filter": {
          "type": "string",
          "description": "Name of one of the user's saved executive-changes filters (see get_saved_filters); its criteria are applied and any explicit filters above are added on top"
        },
        "executive_name": {
          "type": "string",
          "description": "Filter by executive name"
        },
        "open_seats_only": {
          "type": "boolean",
          "description": "Only officer seats that are still open: 8-K departures naming no permanent successor (none named, an interim in the seat, or a search announced) and no later hire filed. Public companies; uses company_name and days, other filters are ignored."
        },
        "new_since_last_pull": {
          "type": "boolean",
          "description": "Only rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account."
        }
      }
    }
    arguments 66 lines
  • remove_from_watchlist changes data auth-required never probed

    Remove a company from the user's Fundz watchlist (favorites).

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "Company id or slug to remove"
        }
      }
    }
    arguments 12 lines
  • get_investor_profile reads auth-required 13h ago

    An investor firm's deal record AND how a founder actually gets in: total deals, deals in the last 90 days, companies backed, median round size, stage mix, first and last cheque, plus the firm's real intake route (warm intro only, open application, scout programme) with the source. Use this for "should we approach them and how".

    mcp-tool

    {
      "type": "object",
      "required": [
        "investor_id"
      ],
      "properties": {
        "investor_id": {
          "type": "number",
          "description": "Investor id from search_investors"
        }
      }
    }
    arguments 12 lines
  • pick_best_contact auth-required never probed

    Returns the one person to email at a company: the most senior match for the buyer titles saved on this user's Fundz account whose email address is verified and whose address belongs to that company. It saves reading get_company_contacts and comparing verified, catch-all, invalid and unrevealed addresses by hand. An invalid address is never returned. A catch-all address is returned only when allow_catch_all is true, which is for when the user has said that is acceptable. Anyone this user already contacted, on any lane, is left out and listed separately. Cost: when no verified address is held for the company, this reveals contacts there, which spends one of the user's monthly contact reveals (the result shows how many are left). It does that for at most reveal_budget companies per hour (default 5); beyond that it spends nothing and says so, so the user can decide. Set reveal to false to spend nothing. When nobody verified is found the result says so; that company is best skipped. The result names the person, their title, the address status and why they were chosen, ready to pass to get_smartsend_draft.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "reveal": {
          "type": "boolean",
          "description": "false to never spend a reveal in this call. Default true."
        },
        "company": {
          "type": "string",
          "description": "Company id, slug, domain or name"
        },
        "reveal_budget": {
          "type": "integer",
          "maximum": 25,
          "minimum": 0,
          "description": "Most companies to reveal contacts at within one hour, across calls (default 5, max 25). Raise it only when the user asked for a bigger batch."
        },
        "allow_catch_all": {
          "type": "boolean",
          "description": "true only after the user said a catch-all address (the domain accepts every address, so the mailbox cannot be confirmed) is acceptable. Default false."
        }
      }
    }
    arguments 26 lines
  • search_raised_and_hiring auth-required 10h ago

    Raised & Hiring, the same list as app.fundz.net/funded-and-hiring: companies with a verified funding round in the last 12 months that have open job postings now, scored and refreshed daily, with the latest round, open postings and exec hires in the last 90 days, and hiring signals. Every company listed has at least one open posting; an exec hire alone does not qualify. Filter by US state, funding series, company name, company size, the role they are hiring (title_family, keyword, department) or new this week. Page through every match with page; use since to get only companies that joined the list on or after a date. To find companies hiring a leadership role, USE title_family (for example title_family "sales_leadership" for "hiring a VP Sales, Head of Sales, Sales Director or CRO"), never a single keyword: titles vary ("VP Sales" returns nothing at a company that posts "Director of Sales"). keyword also takes several titles joined with " OR " or "|". department "Sales" also covers Go-to-market, GTM, Revenue and Business Development.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). The reply ends with the total and next_page when there are more."
        },
        "sort": {
          "enum": [
            "score",
            "funding_date",
            "newest"
          ],
          "type": "string",
          "description": "score (default), funding_date (latest round first) or newest (most recently added first)"
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only companies that joined the list on or after this ISO date, e.g. \"2026-10-01\" (sorts newest first)"
        },
        "state": {
          "type": "string",
          "description": "US state name or 2-letter code, comma-separated for several, e.g. \"Texas, CO\""
        },
        "series": {
          "type": "string",
          "description": "Latest funding series, comma-separated, e.g. \"Seed, Series A\""
        },
        "keyword": {
          "type": "string",
          "description": "Only companies with an open posting whose title contains this. Several: \"Director of Sales OR Head of Sales\"."
        },
        "new_only": {
          "type": "boolean",
          "description": "Only companies that joined the list in the last 7 days"
        },
        "department": {
          "type": "string",
          "description": "Only companies with an open posting in this department. \"Sales\" also matches Go-to-market, GTM, Revenue, Commercial and Business Development."
        },
        "company_name": {
          "type": "string",
          "description": "Company name (partial, case-insensitive)"
        },
        "my_territory": {
          "type": "boolean",
          "description": "Only companies inside the locations of the user's saved filters"
        },
        "title_family": {
          "type": "string",
          "description": "Title family: one OR set of roles, comma-separated for several. sales_leadership = VP / Vice President / Head of / Director of Sales, Revenue or GTM, plus CRO and Chief Revenue Officer. sales_manager = Sales Manager titles (add it when the user says \"sales leaders and managers\"). marketing_leadership, engineering_leadership, finance_leadership."
        },
        "employees_max": {
          "type": "number",
          "description": "Maximum employee count (same handling of unknown headcount)"
        },
        "employees_min": {
          "type": "number",
          "description": "Minimum employee count. Companies with no headcount on file are kept, marked \"headcount unknown\" and ranked after the known in-range ones."
        }
      }
    }
    arguments 67 lines
  • search_fund_formations reads auth-required 3h ago

    New investment funds raising capital, from SEC Form D filings: fund name, target or raised amount and the filing. Use this for "who is raising a fund", LP and allocator work, or to catch a firm standing up a new vehicle before it is announced.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "min_amount": {
          "type": "number",
          "description": "Minimum amount in dollars, e.g. 50000000 for $50M"
        },
        "company_name": {
          "type": "string",
          "description": "Fund or firm name (partial, case-insensitive)"
        }
      }
    }
    arguments 22 lines
  • search_major_events reads auth-required 25h ago

    Material corporate events drawn from SEC filings, each with a plain-English description and a category (executive change, acquisition, funding, contract, product launch, expansion, regulatory and so on). Broader than search_sec_filings: use this to scan for what materially happened, and search_sec_filings when the user wants the filings themselves.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Days to look back (default 7)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only results Fundz added on or after this ISO date, e.g. \"2026-10-01\" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new."
        },
        "category": {
          "enum": [
            "funding",
            "hiring",
            "acquisition",
            "contract_agreement",
            "product_launch",
            "award",
            "company_expansion",
            "regulatory_change",
            "rapid_growth",
            "other"
          ],
          "type": "string",
          "description": "Event category. hiring = executive changes, acquisition = M&A, funding = financial events."
        },
        "company_name": {
          "type": "string",
          "description": "Company name (partial, case-insensitive)"
        }
      }
    }
    arguments 42 lines
  • search_sec_filings reads auth-required 3h ago

    Recent SEC 8-K filings with a plain-English AI summary of what actually happened: leadership changes, material agreements, results, restructuring. Use this for "what did company X just file" or to scan a window for material events. Public companies only.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Days to look back (default 7)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 10, max 50)"
        },
        "company_name": {
          "type": "string",
          "description": "Company name (partial, case-insensitive)"
        }
      }
    }
    arguments 22 lines
  • search_agreements reads auth-required 10h ago

    Search for partnership agreements and strategic alliances. Filter by agreement type, company names, and date range.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Number of days to look back (e.g., 7, 30, 60)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only results Fundz added on or after this ISO date, e.g. \"2026-10-01\" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new."
        },
        "industry": {
          "type": "string",
          "description": "Industry title, e.g. \"Information Technology\""
        },
        "keywords": {
          "type": "string",
          "description": "Free-text keywords matched against title/description (comma-separated for several)"
        },
        "location": {
          "type": "string",
          "description": "City, state or country title, e.g. \"Texas\""
        },
        "company_name": {
          "type": "string",
          "description": "Filter by company name"
        },
        "partner_name": {
          "type": "string",
          "description": "Filter by partner company name"
        },
        "agreement_type": {
          "type": "string",
          "description": "Type of agreement (e.g., \"Partnership\", \"Strategic Alliance\", \"Joint Venture\")"
        },
        "new_since_last_pull": {
          "type": "boolean",
          "description": "Only rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account."
        }
      }
    }
    arguments 50 lines
  • get_daily_leads reads auth-required 25h ago

    Get your personalized daily lead recommendations based on your targeting preferences. Returns AI-scored companies that match your ideal customer profile. A new list is built every day, weekends included, and each day's list stands alone (Monday's list does not repeat Saturday's or Sunday's). To catch up on days you missed, pass days (e.g. days: 3 on a Monday returns Saturday, Sunday and Monday). For "who should I reach out to": get_lead_detail on the strongest few, then give a short ranked action plan: the dated event, why it fits (Timing, Relevance, Relationships), who to contact (who_do_i_know first for a warm intro, then get_company_contacts) and the first line of an opener. Say when a lead's fit is weak rather than padding the list.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "icp": {
          "type": "string",
          "description": "Which ICP's list. Omit for the main ICP. Pass an extra ICP's name or id (get_targeting_preferences lists them, e.g. \"ICP2\") for that list alone, or \"all\" for the main list plus every active extra ICP merged, one row per company, each tagged with the ICP(s) that picked it."
        },
        "days": {
          "type": "integer",
          "maximum": 14,
          "minimum": 1,
          "description": "How many days of daily lists to return, counting today (1 = today only, the default; 3 on a Monday = the weekend plus today; max 14). With icp \"all\" the result opens with how many companies each ICP returned, so a thin ICP is visible at once."
        }
      }
    }
    arguments 16 lines
  • get_lead_detail reads auth-required 5d ago

    Get the FULL scoring breakdown for one company in today's daily leads: match score and data confidence, buying stage, hiring and exec-hire forecasts, ML predictions with a timeframe, the key insights behind the score, the recommended play, and the suggested contacts. Use this whenever asked why a lead scored what it did, or for the same depth the Fundz lead inbox shows.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "Company name or organization id from today's daily leads"
        }
      }
    }
    arguments 12 lines
  • get_targeting_preferences reads auth-required 22h ago

    Get your current targeting preferences including industries, locations, company sizes, and buying signals you are tracking. Call this FIRST when the user asks what Fundz can do for them, asks for help getting started, or opens with a vague question: then answer for THIS user (their industries, locations, company sizes and events, not a generic feature list) and offer 5 specific questions they could ask next, written for their role (e.g. a recruiter: open executive seats, new CFOs, interim appointments; a seller: today's leads, who just raised and is hiring, a market-update email). If targeting is empty, ask what they sell or who they place and save it with update_targeting_preferences.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • update_targeting_preferences changes data auth-required never probed

    Save who the user wants as customers (or, for a recruiter, as clients) to their Fundz account: industries, locations, company sizes, the events to watch, and the three answers that decide how well the daily leads fit: who buys (buyer_description), three to five example customers (example_customers) and what is not a fit (avoid_companies). The lead scorer reads those three for every company it considers; without a who-buys sentence or at least two example customers Fundz can only match on industry, size and location, and niche buyers get missed. Pass what the user said in their own words as ideal_customer_profile; pass industries, locations and employee_ranges directly when you have them. Send everything you have together in ONE call. On an account with no lead list today, this save starts building the first list straight away from whatever is on file at that moment, so the who-buys answers belong in the same call, not a later one; the result says when the list will be ready (about five minutes) and every later Fundz result reports the build status. Setup counts as complete in the Fundz app (no setup screen on first sign-in) once what the company sells, a location, a company size and either a who-buys sentence of 40+ characters or two example customers are on file; the result says which of these is still missing. What the company sells and the buyer job titles are saved with save_sender_profile, not here. This changes the saved targeting that the daily lead list is scored against, so read back what was saved.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "deal_size": {
          "type": "array",
          "items": {
            "enum": [
              "under_10k",
              "10k_50k",
              "50k_250k",
              "over_250k"
            ],
            "type": "string"
          },
          "description": "Typical deal size, one or more of: under_10k, 10k_50k, 50k_250k, over_250k. Optional. It tells the scorer what size of company can afford the user; it never hides a company."
        },
        "locations": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Target locations (e.g., [\"San Francisco\", \"New York\", \"United States\"])"
        },
        "industries": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Specific industries to target (e.g., [\"Software\", \"Healthcare\", \"Finance\"]). When the user sells to any industry, pass an empty list (or [\"All industries\"]): Fundz then leaves no industry out."
        },
        "supply_choice": {
          "enum": [
            "keep"
          ],
          "type": "string",
          "description": "Pass \"keep\" ONLY after a Fundz result said LEAD SUPPLY with a low number, you told the user that number, and the user said to keep the filters as they are. It records that they chose to keep them knowing how many leads a day to expect. Send it alone, with no other fields. Never pass it without asking the user."
        },
        "buying_signals": {
          "type": "array",
          "items": {
            "enum": [
              "funding",
              "exec_hire",
              "product_launch",
              "contract",
              "acquisition",
              "sec_filing",
              "fund_raise",
              "hiring_surge",
              "exec_departure",
              "crowdfunding"
            ],
            "type": "string"
          },
          "description": "Events that make a company a lead: funding (recent funding), exec_hire (new leadership), product_launch, contract (new contracts), acquisition, sec_filing (SEC 8-K filings), fund_raise (fund formations), hiring_surge, exec_departure (open executive seats), crowdfunding. Leave out to keep what is saved; a new account tracks all of them."
        },
        "avoid_companies": {
          "type": "string",
          "description": "What is NOT a fit, in the user's words: kinds of companies, sectors or named companies to keep out of the list (e.g. \"no agencies or consultancies, no public companies, nothing in crypto\")."
        },
        "employee_ranges": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Employee size ranges: range1 (0-50), range2 (51-200), range3 (201-500), range4 (501-1000), range5 (1001-5000), range6 (5000+)"
        },
        "buyer_description": {
          "type": "string",
          "description": "Who buys from the user, in their own words: the kind of company, what is usually going on there when they buy, and what sets a real buyer apart from a look-alike (e.g. \"Series A to C software companies that just hired their first VP Sales and are building an outbound team\"). One to three sentences. Read by the lead scorer for every company."
        },
        "example_customers": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Three to five real customers (company names, or names with a website) the user would like more of. The scorer looks for companies like them. Up to 10."
        },
        "ideal_customer_profile": {
          "type": "string",
          "description": "Natural language description of your ideal customer (e.g., \"enterprise software companies in healthcare with 500+ employees\")"
        },
        "request_instant_scoring": {
          "type": "boolean",
          "description": "If true, returns instant AI-scored leads matching the new preferences"
        }
      }
    }
    arguments 89 lines
  • search_crowdfunding reads auth-required 6h ago

    Find crowdfunding campaigns. Search by offering amount, deadline, offered types (Common Stock, etc.), and portal.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Number of days to look back (e.g., 7, 30, 60)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only results Fundz added on or after this ISO date, e.g. \"2026-10-01\" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new."
        },
        "industry": {
          "type": "string",
          "description": "Industry title, e.g. \"Information Technology\""
        },
        "keywords": {
          "type": "string",
          "description": "Free-text keywords matched against title/description (comma-separated for several)"
        },
        "location": {
          "type": "string",
          "description": "City, state or country title, e.g. \"Texas\""
        },
        "company_name": {
          "type": "string",
          "description": "Company name (partial match)"
        },
        "offered_types": {
          "type": "string",
          "description": "Type of security offered (e.g., \"Common Stock\")"
        },
        "max_offering_amount": {
          "type": "number",
          "description": "Maximum offering amount (in dollars)"
        },
        "min_offering_amount": {
          "type": "number",
          "description": "Minimum offering amount (in dollars)"
        },
        "new_since_last_pull": {
          "type": "boolean",
          "description": "Only rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account."
        }
      }
    }
    arguments 54 lines
  • search_funding_rounds reads auth-required 3h ago

    Search funding rounds (the same feed as app.fundz.net/fundings). Filter by company name, industry, location (city/state/country), keywords, series, amount and date window, or run one of the user's saved filters by name. Page through every match with page, and get only new rounds with since. Filters are applied server-side, so the total_count is the filtered total.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Number of days to look back (default 7)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only results Fundz added on or after this ISO date, e.g. \"2026-10-01\" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new."
        },
        "series": {
          "type": "string",
          "description": "Funding series (e.g., \"Seed\", \"Series A\", \"Series B\", \"Series C\")"
        },
        "industry": {
          "type": "string",
          "description": "Industry title as used in Fundz, e.g. \"Information Technology\", \"Financial Services\", \"Health Care\""
        },
        "keywords": {
          "type": "string",
          "description": "Free-text keywords matched against the round's title and description, e.g. \"fintech\", \"artificial intelligence\""
        },
        "location": {
          "type": "string",
          "description": "City, state/region or country title, e.g. \"Colorado\", \"United States\", \"Denver\", \"United Kingdom\""
        },
        "company_name": {
          "type": "string",
          "description": "Company name (partial, case-insensitive), e.g. \"Voxel\""
        },
        "saved_filter": {
          "type": "string",
          "description": "Name of one of the user's saved filters (see get_saved_filters); its criteria are applied and any explicit filters above are added on top"
        },
        "still_raising": {
          "type": "boolean",
          "description": "Only companies whose latest SEC Form D shows they have sold less than they offered, so the round is still open (filings from the last year; pooled funds, property deals and \"Indefinite\" offerings are left out). Each row then shows how much was offered and how much was sold so far."
        },
        "max_money_raised": {
          "type": "number",
          "description": "Maximum amount raised (in dollars)"
        },
        "min_money_raised": {
          "type": "number",
          "description": "Minimum amount raised (in dollars, e.g., 1000000 for $1M)"
        },
        "min_remaining_usd": {
          "type": "number",
          "description": "With still_raising: only rounds with at least this many dollars left to raise (offered minus sold), e.g. 1000000 for $1M+"
        },
        "new_since_last_pull": {
          "type": "boolean",
          "description": "Only rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account."
        }
      }
    }
    arguments 66 lines
  • get_saved_filters reads auth-required 25h ago

    List the saved filters (saved searches) the user created in the Fundz web app: name and what it filters on (series, investors, locations, industries, amount, company size, keywords). Use a saved filter's name as the `saved_filter` argument of search_funding_rounds, search_executive_changes or search_acquisitions (matching its type) to run that exact search. Requires signing in (not available with a plain API key).

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_watchlist_changes reads auth-required 22h ago

    Get what changed at the companies on the user's watchlist: SEC filings (8-K, 10-K, 10-Q), office leases, WARN layoff notices, commercial building permits, funding, executive hires, acquisitions, partnerships and product launches. Covers the same companies and signals as the 9am watchlist email.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 90,
          "minimum": 1,
          "description": "How many days back to look for signals (default 14)."
        }
      }
    }
    arguments 12 lines
  • toggle_email_notifications changes data auth-required never probed

    Enable or disable daily email notifications for your leads and updates.

    mcp-tool

    {
      "type": "object",
      "required": [
        "enabled"
      ],
      "properties": {
        "enabled": {
          "type": "boolean",
          "description": "True to enable emails, false to disable"
        },
        "delivery_time": {
          "type": "string",
          "description": "Time to receive emails: 9am, 12pm, or 6pm"
        }
      }
    }
    arguments 16 lines
  • search_investors reads auth-required 5d ago

    Find investors by name across 37,000+ firms and angels that have actually written cheques in the Fundz deal data. Returns ids to pass to get_investor_profile.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Maximum results (default 10, max 25)"
        },
        "query": {
          "type": "string",
          "description": "Investor or firm name, partial is fine, e.g. \"sequoia\", \"a16z\""
        }
      }
    }
    arguments 16 lines
  • add_to_watchlist changes data auth-required never probed

    Save a company to the user's Fundz watchlist (favorites), so it shows up in their app and alerts. Reversible and free. Takes the company id or slug from any search result.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "Company id or slug to save"
        }
      }
    }
    arguments 12 lines
  • save_sender_profile auth-required never probed

    Save what the user tells you about themselves to their Fundz account, so they never have to open Fundz to finish setup: their own name, their job title, company name, website, phone, booking link, a one or two sentence description of what the company does, their role, and the job titles of the people they sell to. Use it during "Set up Fundz" whenever check_outreach_setup shows something MISSING, and any time the user says things like "my title is", "my booking link is", "we sell to CFOs". Ask in plain words, one question at a time, and save each answer as you get it. Only the fields you pass are changed; an empty field never erases what is on file. role can be set only when the account has no role yet, and must be one of the slugs check_outreach_setup lists. target_titles: the first time the user states their buyer titles, those replace any titles Fundz had guessed from the company description; after that, new titles are added to the ones they stated. Pass replace_target_titles true when the user says "only these" or corrects the list, false to add. Industries, locations and company sizes are not saved here: use update_targeting_preferences for those. When a first lead list is building, the result says when it will be ready. Read the result back to the user in one or two lines, including anything refused.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "name": {
          "type": "string",
          "description": "The user's own first and last name, as it should appear under their emails"
        },
        "role": {
          "type": "string",
          "description": "Role slug from the list check_outreach_setup returns (only when no role is set yet)"
        },
        "phone": {
          "type": "string",
          "description": "Phone number for the email signature (optional)"
        },
        "title": {
          "type": "string",
          "description": "The user's own job title, e.g. \"Managing Partner\""
        },
        "company": {
          "type": "string",
          "description": "The user's company name"
        },
        "website": {
          "type": "string",
          "description": "The company website or domain, e.g. \"acme.com\""
        },
        "description": {
          "type": "string",
          "description": "One or two sentences on what the company does and for whom, in the user's own words"
        },
        "booking_link": {
          "type": "string",
          "description": "Link where a prospect books a meeting, e.g. a Calendly link"
        },
        "target_titles": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Job titles of the people the user sells to or places, e.g. [\"CFO\", \"VP Finance\"] (10 per call). The first stated list replaces titles Fundz guessed; later ones are added."
        },
        "replace_target_titles": {
          "type": "boolean",
          "description": "true: these titles replace the whole list on file. false: add to it. Leave out to let Fundz decide (replace a guess, add to stated titles)."
        }
      }
    }
    arguments 49 lines
  • invite_seat auth-required never probed

    Invite the person who will work the user's leads (an assistant or a colleague) into the one seat included with Pro and Strategic at no extra cost. Use it when the user answers "Who will work your leads?" with someone else, or says things like "my assistant works my leads" or "give my colleague a login". Ask for the person's name and work email, read both back, and call this only after the user says yes: it sends that person an email with a link to set a password. They get their own login and work this account's leads with its targeting and network, so there is one list, and the account owner gets what was worked by email each week. It can never add a charge: when the included seat is already taken it sends nothing and the result says where further seats are added (Account, Team Management, where the price is shown first). Only the account owner can invite. Read the result back to the user in one or two lines.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "email"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "First and last name of the person who will work the leads"
        },
        "email": {
          "type": "string",
          "description": "Their work email address; the invite is sent here"
        }
      }
    }
    arguments 17 lines
  • search_benefit_plans auth-required 16h ago

    Benefit Plans in Play: recently funded companies with an employee benefit plan on record (from their Form 5500 filing), each with the next plan renewal date, the current carrier, the number of plans and participants, broker commission where filed, and the funding round that makes the timing right. For benefits brokers, insurance and 401(k) sellers, HR and payroll vendors asking "whose benefits renew soon", "who is the carrier at X", "funded companies in Texas with a plan renewal coming up". Filter by company name and US state; sort "date" puts the soonest renewal first, "newest" the rows added most recently, "score" (default) the strongest fit. The full list is part of the Strategic plan; on other plans the result is the first 5 rows and says so. Reads only.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (25 rows per page)"
        },
        "sort": {
          "enum": [
            "score",
            "date",
            "newest"
          ],
          "type": "string",
          "description": "score (default), date (soonest renewal first) or newest"
        },
        "states": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "US state codes, e.g. [\"TX\", \"FL\"]"
        },
        "new_only": {
          "type": "boolean",
          "description": "Only rows added in the last 7 days"
        },
        "company_name": {
          "type": "string",
          "description": "Company name (partial match)"
        }
      }
    }
    arguments 34 lines
  • get_smartsend_draft auth-required never probed

    The outreach sequence Fundz writes for one contact at one company: three short emails (first email, follow-up, last note) in the user's own sender profile, checked against Fundz events. Email one opens with what is moving in the recipient's market and names the company's own news. Also returns the user's signature and booking link, and every email this user already sent to that person or to others at the company, so nobody gets a second first email. Use this instead of composing outreach from scratch; the text is complete as returned and every fact in it is already checked, so no web search is needed to write the email. Nothing is sent. The first call for a contact can take 15 to 25 seconds; repeat calls are instant. Costs one call from the daily API quota.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company",
        "contact_email"
      ],
      "properties": {
        "event": {
          "type": "string",
          "description": "The dated event that made this company a lead, as Fundz returned it (e.g. \"Raised a $12M Series A on 2026-11-03\"). Email one names it."
        },
        "opener": {
          "type": "string",
          "description": "Optional first line the user wants email one to start with"
        },
        "company": {
          "type": "string",
          "description": "Company id, slug, domain or name of the RECIPIENT"
        },
        "redraft": {
          "type": "boolean",
          "description": "true to write a fresh version instead of returning the saved one"
        },
        "signal_type": {
          "type": "string",
          "description": "Kind of event: funding, executive, acquisition, hiring, contract, product, expansion (default funding)"
        },
        "contact_name": {
          "type": "string",
          "description": "The recipient's full name"
        },
        "contact_email": {
          "type": "string",
          "description": "The recipient's email address"
        },
        "contact_title": {
          "type": "string",
          "description": "The recipient's job title"
        }
      }
    }
    arguments 41 lines
  • log_outreach_sent auth-required never probed

    Record in Fundz that the user sent an outreach email from their own mailbox, so the lead shows as Contacted in the Fundz app and is flagged before anyone writes to that person again. Call it only after the user confirms the email was actually sent, never for a draft. It sends nothing itself. A setup test email sent to the user's own address is fine to pass here: Fundz recognises it, records no outreach, and tells you what to have the user check. Fundz allows three touches per contact; a fourth is refused with the reason. After it records, the result may tell you to ask the user whether to schedule the follow-ups: always finish your reply with that question when it does, even if the user only asked you to send and record.

    mcp-tool

    {
      "type": "object",
      "required": [
        "contact_email",
        "company"
      ],
      "properties": {
        "body": {
          "type": "string",
          "description": "Body of the email that was sent"
        },
        "event": {
          "type": "string",
          "description": "The event the email was built on"
        },
        "company": {
          "type": "string",
          "description": "Company id, slug, domain or name"
        },
        "subject": {
          "type": "string",
          "description": "Subject line of the email that was sent"
        },
        "signal_type": {
          "type": "string",
          "description": "Kind of event (default funding)"
        },
        "contact_name": {
          "type": "string",
          "description": "The recipient's full name"
        },
        "contact_email": {
          "type": "string",
          "description": "The recipient's email address"
        }
      }
    }
    arguments 37 lines
  • log_outreach_reply auth-required never probed

    Record in Fundz that a contact replied to the user's outreach, and stop every follow-up Fundz still has queued to that person (email and LinkedIn). Fundz cannot read a Gmail inbox, so call this as soon as the reply is seen in the user's mailbox or the user says the person answered. Do not ask the user for permission first: a reply always stops follow-ups. Tell them afterwards. Safe to call twice.

    mcp-tool

    {
      "type": "object",
      "required": [
        "contact_email"
      ],
      "properties": {
        "snippet": {
          "type": "string",
          "description": "A sentence or two of what they said"
        },
        "replied_at": {
          "type": "string",
          "description": "When they replied (ISO date or datetime); defaults to now"
        },
        "contact_email": {
          "type": "string",
          "description": "Email address of the person who replied"
        }
      }
    }
    arguments 20 lines
  • get_outreach_history auth-required 16h ago

    Everyone this user has already contacted, from the same record every Fundz outreach tool reads: emails logged from chat, emails sent from the Fundz app, and Fundz-run campaigns on the account. Per person: the company, last subject and date, number of touches, which lane it went out on, whether they replied or booked, and when the next follow-up is due. The result opens with the total per lane. The list shows at most 100 people, personal sends first, so to check ONE company always pass company (name, domain, id or slug): that answer is complete. Use it for "who have I not heard back from", to check a mailbox for replies from exactly these people, or before writing to a company. Costs one call from the daily API quota.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "number",
          "description": "How far back to look (default 30, max 180)"
        },
        "lane": {
          "enum": [
            "chat",
            "fundz_app",
            "campaign"
          ],
          "type": "string",
          "description": "Only one lane: chat (logged from an assistant), fundz_app (sent in the Fundz app) or campaign (Fundz-run campaigns)"
        },
        "company": {
          "type": "string",
          "description": "Limit to one company (id, slug, domain or name). Complete for that company."
        },
        "awaiting_reply": {
          "type": "boolean",
          "description": "true to list only people who have not replied or booked"
        }
      }
    }
    arguments 26 lines
  • get_market_gift reads auth-required 5d ago

    Recent activity among companies adjacent to the one given: who raised, hired, won a contract, filed or expanded in their market. Returns dated events with the shared market themes they were matched on, for opening outreach with a market update rather than a pitch. Costs one call from the daily API quota, and returns few or no rows when little has happened.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "Company id or slug of the RECIPIENT, i.e. who you are writing to"
        },
        "lookback_days": {
          "type": "number",
          "description": "How far back to look for market movement (default 90)"
        }
      }
    }
    arguments 16 lines
  • get_company_profile reads auth-required 13h ago

    Everything Fundz holds on one company in a single call: firmographics plus every signal fused together (funding rounds with investors, executive moves, acquisitions, partnerships, product launches, SEC filings) and, on Strategic, the alt-data layer of office expansions and USPTO trademarks. Takes the company id or slug from any search result. Use this when the user asks about a specific company rather than for a list.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "Company id or slug, e.g. \"overfuel\" (search results include this)"
        }
      }
    }
    arguments 12 lines
  • search_filing_text auth-required 20h ago

    Full-text search inside SEC filings: the words a company itself wrote in its 10-K and 10-Q (business, properties, risk factors, MD&A), 20-F, and 8-K filings with their press releases. Returns the matching passage, company, form, filing date, section and a link to the exact filing on EDGAR. Use it for questions like "which banks mention contact centers in their 10-K", "did Verizon talk about headcount this year", "who is opening a new facility", or to search only the user's watchlist. Plain phrases match as a whole phrase plus common synonyms (contact center also finds call center). Put words in quotes, use OR, or a leading minus for exact control. Public companies only; covers the last 12 months.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "days": {
          "type": "number",
          "description": "Days to look back (default 365, max 730)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` filings; the reply ends with the total and next_page when there are more."
        },
        "forms": {
          "type": "string",
          "description": "Comma-separated form types: 10-K, 10-Q, 20-F, 8-K (default all)"
        },
        "limit": {
          "type": "number",
          "description": "Filings per page (default 10, max 25)"
        },
        "query": {
          "type": "string",
          "description": "Words or phrase to find, e.g. \"contact center\", \"offshore\", \"new facility\", \"headcount\""
        },
        "section": {
          "type": "string",
          "description": "Optional 10-K item (\"1\" business, \"1A\" risk factors, \"2\" properties, \"7\" MD&A) or 10-Q item (\"I-2\" MD&A, \"II-1A\" risk factors)"
        },
        "watchlist": {
          "type": "boolean",
          "description": "Limit to companies on the signed-in user's Fundz watchlist"
        },
        "company_name": {
          "type": "string",
          "description": "Limit to companies whose SEC name contains this (partial, case-insensitive), e.g. \"verizon\""
        }
      }
    }
    arguments 40 lines
  • get_company_contacts reads auth-required 20h ago

    Get the people Fundz already holds for one company: name, role, department and email where we have it. Takes the company id or slug returned by search_funding_rounds and the other feeds. Each email carries its verification status and date where Fundz holds one, and the result shows which of your own LinkedIn connections work there. Reading these costs nothing. If a contact has no email yet, reveal_contacts can fetch one.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "Company id or slug, e.g. \"overfuel\" or \"181403\" (search results include this)"
        },
        "with_email_only": {
          "type": "boolean",
          "description": "Return only contacts that already have an email address"
        }
      }
    }
    arguments 16 lines
  • who_do_i_know auth-required 13h ago

    Which of the signed-in user's OWN LinkedIn connections work at a company, for a warm introduction instead of a cold email. Reads only the connections this user uploaded to Fundz (app.fundz.net/my-network); never anyone else's network. Free, costs no reveal. Takes the company id or slug from a search result. get_company_contacts also shows this and flags contacts you are already connected to.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "Company id or slug, e.g. \"overfuel\" or \"181403\" (search results include this)"
        }
      }
    }
    arguments 12 lines
  • reveal_contacts changes data auth-required never probed

    Spend one of the user's monthly contact reveals to find decision-maker emails at a company, matched to the titles they sell to. Each revealed email is checked with a live mailbox verification and returned with a status (verified, risky, unknown, invalid) and the date. Use this when get_company_contacts returns nobody, or nobody with an email. Charges the monthly allowance (Strategic 600, Pro 150); tells the user what is left and how to upgrade when it runs out.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "Company id or slug to reveal contacts at"
        },
        "include_mobile": {
          "type": "boolean",
          "description": "Also attempt a mobile number. Costs considerably more than an email, so only when the user asks for a phone number."
        }
      }
    }
    arguments 16 lines
  • search_hiring_intel auth-required 27h ago

    Hiring Intel, the same search as app.fundz.net/hiring-intel: companies hiring right now from their live job postings, each with open-role counts, sample roles, hiring signals (exec backfill, vacancy aging, role reposted, key role posted, department expansion, hiring surge, tech stack), a hiring score and why, recent funding and leadership change. view "companies" (default) returns one card per company; view "postings" returns individual open job postings with links. Filter by industry, location, country, company size, keyword, department, technology, remote, days open, signals, recent funding or leadership change. Page through every match with page; use since to get only postings Fundz first saw on or after a date. To find companies hiring a leadership role, USE title_family (for example title_family "sales_leadership" for "hiring a VP Sales, Head of Sales, Sales Director or CRO"), never a single keyword: titles vary ("VP Sales" returns nothing at a company that posts "Director of Sales"). keyword also takes several titles joined with " OR " or "|". department "Sales" also covers Go-to-market, GTM, Revenue and Business Development.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Only postings Fundz first saw in the last N days (default 45, max 120)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). The reply ends with the total and next_page when there are more."
        },
        "sort": {
          "enum": [
            "newest",
            "org",
            "title"
          ],
          "type": "string",
          "description": "Postings view sort (default newest)"
        },
        "tech": {
          "type": "string",
          "description": "Technology named in the postings, e.g. \"Salesforce\", \"Snowflake\""
        },
        "view": {
          "enum": [
            "companies",
            "postings"
          ],
          "type": "string",
          "description": "\"companies\" (default): one card per hiring company. \"postings\": individual open job postings."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (companies view default 10, postings default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only postings Fundz first saw on or after this ISO date, e.g. \"2026-10-01\". Overrides days; reaches back at most 120 days."
        },
        "country": {
          "type": "string",
          "description": "Companies view: country, e.g. \"United States\""
        },
        "keyword": {
          "type": "string",
          "description": "Matched against job titles, e.g. \"controller\". Several titles: \"Director of Sales OR Head of Sales\". For a role family prefer title_family."
        },
        "signals": {
          "type": "string",
          "description": "Companies view: only companies with one of these signals in the last 14 days, comma-separated: exec_backfill, vacancy_aging, role_reposted, key_role_posted, department_expansion, hiring_surge, tech_stack_signal"
        },
        "sort_by": {
          "enum": [
            "newest",
            "hiring_score",
            "name",
            "employees",
            "most_postings",
            "longest_aged",
            "most_signals",
            "recent_funding",
            "warm_intro"
          ],
          "type": "string",
          "description": "Companies view sort (default newest)"
        },
        "industry": {
          "type": "string",
          "description": "Companies view: industry title(s), comma-separated, e.g. \"Health Care, Financial Services\""
        },
        "location": {
          "type": "string",
          "description": "Companies view: city, state or region title(s), separated by semicolons, e.g. \"Texas; Austin, Texas\""
        },
        "department": {
          "type": "string",
          "description": "Department, e.g. \"Engineering\", \"Finance\". \"Sales\" also matches Go-to-market, GTM, Revenue, Commercial and Business Development."
        },
        "remote_only": {
          "type": "boolean",
          "description": "Only remote postings"
        },
        "my_territory": {
          "type": "boolean",
          "description": "Companies view: only companies inside the locations of the user's saved filters"
        },
        "title_family": {
          "type": "string",
          "description": "Title family: one OR set of roles, comma-separated for several. sales_leadership = VP / Vice President / Head of / Director of Sales, Revenue or GTM, plus CRO and Chief Revenue Officer. sales_manager = Sales Manager titles (add it when the user says \"sales leaders and managers\"). marketing_leadership, engineering_leadership, finance_leadership."
        },
        "employees_max": {
          "type": "number",
          "description": "Companies view: maximum employee count"
        },
        "employees_min": {
          "type": "number",
          "description": "Companies view: minimum employee count. Companies with no headcount on file are kept and marked \"headcount unknown\", ranked after the known in-range ones."
        },
        "min_days_open": {
          "type": "number",
          "description": "Only postings open at least this many days (hard-to-fill roles), e.g. 60"
        },
        "icp_match_only": {
          "type": "boolean",
          "description": "Companies view: only companies matching the user's targeting profile"
        },
        "has_first_degree": {
          "type": "boolean",
          "description": "Companies view: only companies where the user has 1st-degree LinkedIn connections (needs their network uploaded)"
        },
        "funded_within_days": {
          "type": "number",
          "description": "Companies view: only companies with a funding round in the last N days"
        },
        "has_hiring_manager": {
          "type": "boolean",
          "description": "Companies view: only companies with a named hiring manager on a posting (a narrow filter)"
        },
        "recent_exec_change": {
          "type": "boolean",
          "description": "Companies view: only companies with a leadership change in the last 30 days"
        },
        "new_since_last_pull": {
          "type": "boolean",
          "description": "Postings view: only postings this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account."
        }
      }
    }
    arguments 130 lines
  • search_office_expansions auth-required 22h ago

    Office expansions, the same feed as app.fundz.net/office-expansions: new office leases, expansions and relocations that public companies disclosed in SEC 8-K filings (the filer is always the tenant taking space; renewals of existing space are left out unless lease_type asks for them, and factory or warehouse sites unless facility_type asks for them), with address and country, facility type, square footage, exact lease term, annual and total base rent, landlord or sublandlord, start dates and a plain-English summary. A company taking more space is usually about to hire. Filter by state, city, company, lease type, minimum square feet and filing date. Page through every match with page; use since to get only filings on or after a date.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "city": {
          "type": "string",
          "description": "City of the leased space (partial match), e.g. \"Austin\""
        },
        "days": {
          "type": "number",
          "description": "Only filings in the last N days (default: all)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). The reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only filings on or after this ISO date, e.g. \"2026-10-01\". Overrides days."
        },
        "state": {
          "type": "string",
          "description": "US state 2-letter code(s) of the leased space, comma-separated, e.g. \"CA, NY\""
        },
        "lease_type": {
          "type": "string",
          "description": "One or more of: new, expansion, relocation, renewal (comma-separated), or all. Default: new, expansion and relocation (renewals excluded)."
        },
        "company_name": {
          "type": "string",
          "description": "Company name (partial, case-insensitive)"
        },
        "facility_type": {
          "type": "string",
          "description": "One or more of: office, lab, mixed, manufacturing, warehouse, retail (comma-separated), or all. Default: everything except pure manufacturing and warehouse sites."
        },
        "min_square_feet": {
          "type": "number",
          "description": "Minimum square footage, e.g. 20000"
        }
      }
    }
    arguments 46 lines
  • search_layoffs auth-required 27h ago

    Layoffs, plant closures and reductions in force from three sources, returned together by default: (1) layoffs announced or reported in the news (company, headcount and percent cut when stated, HQ, affected sites and teams, confirmed vs reported by sources, every article on the event), (2) SEC 8-K filings for restructuring or exit costs (Item 2.05) or a disclosed workforce reduction, and (3) state WARN Act notices employers must file before a mass layoff (the same feed as app.fundz.net/warn-notices). Use source to read one only. A news layoff and an 8-K for the same company are shown as one event. For WARN notices: company, worksite city and state, notice and effective dates, number of employees affected, layoff or closure type (permanent or temporary), industry and a link to the state source. Each row carries a 0-100 distress score that adds weight when the company also filed an SEC 8-K for restructuring (Item 2.05) or an executive or director departure (Item 5.02) within 90 days of the notice, the moment a company is most likely to replace leaders or reorganize. Filter by state, company, notice date, minimum employees affected and layoff type; sort by newest, effective date, size or distress. Use territory to match the states on this Fundz account.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Only the last N days (WARN default: all; news and filings default 30, max 180)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). The reply ends with the total and next_page when there are more."
        },
        "sort": {
          "type": "string",
          "description": "newest (default, by notice date), effective_date, employees (largest first) or distress (highest distress score on each page)"
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only notices on or after this ISO date, e.g. \"2026-10-01\". Overrides days."
        },
        "state": {
          "type": "string",
          "description": "US state 2-letter code(s), comma-separated, e.g. \"CA, NY\". WARN: the worksite. News: the company HQ or an affected site. Filings: the company HQ."
        },
        "source": {
          "type": "string",
          "description": "all (default: news, SEC filings and WARN notices), news, filings or warn; comma-separate to combine, e.g. \"news, filings\""
        },
        "territory": {
          "type": "boolean",
          "description": "true = only the states in this Fundz account's targeting. Ignored when state is given."
        },
        "layoff_type": {
          "type": "string",
          "description": "layoff or closure (each matches permanent, temporary and not-yet-known), or a fuller value such as \"Closure Permanent\""
        },
        "company_name": {
          "type": "string",
          "description": "Company name (partial, case-insensitive)"
        },
        "matched_only": {
          "type": "boolean",
          "description": "true = only notices linked to a Fundz company profile (needed to look up contacts and executives next)"
        },
        "min_employees": {
          "type": "number",
          "description": "Minimum employees affected, e.g. 100"
        }
      }
    }
    arguments 54 lines
  • search_products reads auth-required 6h ago

    Find product launches and updates. Search by launch type (New Product, Major Update, Feature Release), category (Software, Hardware, Service), and company.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Number of days to look back (e.g., 7, 30, 60)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only results Fundz added on or after this ISO date, e.g. \"2026-10-01\" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new."
        },
        "industry": {
          "type": "string",
          "description": "Industry title, e.g. \"Information Technology\""
        },
        "keywords": {
          "type": "string",
          "description": "Free-text keywords matched against title/description (comma-separated for several)"
        },
        "location": {
          "type": "string",
          "description": "City, state or country title, e.g. \"Texas\""
        },
        "launch_type": {
          "type": "string",
          "description": "Type of launch: \"New Product\", \"Major Update\", or \"Feature Release\""
        },
        "company_name": {
          "type": "string",
          "description": "Filter by company name"
        },
        "product_category": {
          "type": "string",
          "description": "Product category: \"Software\", \"Hardware\", or \"Service\""
        },
        "new_since_last_pull": {
          "type": "boolean",
          "description": "Only rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account."
        }
      }
    }
    arguments 50 lines
  • check_outreach_setup auth-required never probed

    Run this FIRST when the user says "Set up Fundz", "get me started", asks what you can do for them end to end, or before the first outreach email in a conversation. It returns the user's sender profile and what is missing from it, their plan and target titles, and a checklist of what each workflow needs (send email, see replies, see booked meetings, log to a CRM, run follow-ups on a schedule). You then compare that checklist with the tools you ACTUALLY have in this chat: a connector can be connected to the account and still be switched off in this chat, so trust your own tool list, not what the user remembers connecting. Tell the user plainly what they can and cannot do today and the exact fix for each gap. It also returns the rules for sending from the user's mailbox (no links in the email body, the mailbox signature carries links, the Gmail "--" line setting) and the one-prompt setup order: profile, ICP, test email to the user's own address, first small batch, follow-up task. When the account is new (profile or targeting mostly empty) the result gives a short interview to run in plain words, one question at a time, saving each answer with update_targeting_preferences and save_sender_profile, so the user is fully set up without opening Fundz. Reads only; sends nothing.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "client": {
          "type": "string",
          "description": "The app you are running in, e.g. \"claude\" or \"chatgpt\" (optional)"
        }
      }
    }
    arguments 10 lines
  • search_acquisitions reads auth-required 10h ago

    Search for acquisition events. Filter by deal value, acquirer name, target company, deal type, and date range.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "days": {
          "type": "number",
          "description": "Number of days to look back (e.g., 7, 30, 60)"
        },
        "page": {
          "type": "number",
          "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more."
        },
        "limit": {
          "type": "number",
          "description": "Results per page (default 20, max 50)"
        },
        "since": {
          "type": "string",
          "description": "Only results Fundz added on or after this ISO date, e.g. \"2026-10-01\" (whole day, so a daily run may repeat that day). Overrides days. Use the date of your last run to get only what is new."
        },
        "industry": {
          "type": "string",
          "description": "Industry title, e.g. \"Information Technology\""
        },
        "keywords": {
          "type": "string",
          "description": "Free-text keywords matched against title/description (comma-separated for several)"
        },
        "location": {
          "type": "string",
          "description": "City, state or country title, e.g. \"Texas\""
        },
        "target_name": {
          "type": "string",
          "description": "Filter by target company name"
        },
        "company_name": {
          "type": "string",
          "description": "Company name (partial match)"
        },
        "saved_filter": {
          "type": "string",
          "description": "Name of one of the user's saved acquisitions filters (see get_saved_filters); its criteria are applied and any explicit filters above are added on top"
        },
        "acquirer_name": {
          "type": "string",
          "description": "Filter by acquiring company name"
        },
        "max_deal_value": {
          "type": "number",
          "description": "Maximum deal value (in dollars)"
        },
        "min_deal_value": {
          "type": "number",
          "description": "Minimum deal value (in dollars, e.g., 50000000 for $50M)"
        },
        "new_since_last_pull": {
          "type": "boolean",
          "description": "Only rows this account has not already been shown by an earlier new_since_last_pull call with the same filters. Fundz remembers per account and filter set, so a daily agent run gets just what is new, with no dates to track. The first call returns the normal window (days or since) and starts the marker. Ignores page: if more new rows are waiting the reply says so; call again the same way for the next batch. Needs a signed-in account."
        }
      }
    }
    arguments 62 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 94ed543b48f2f39f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/94ed543b48f2f39f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/94ed543b48f2f39f/badge.svg)](https://brick.blue/agent/94ed543b48f2f39f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on fundz.net 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.