Skip to main content
Glama
606,818 tools. Updated 2026-09-24 11:50

"Expert database architecture design services for financial industry" matching MCP tools:

  • Returns a paginated list of corporate entities in the TunnelMind surveillance database. Includes data categories, estimated data value, and industry classification. Useful for enumerating the surveillance ecosystem by sector. Use this tool when: - You want to enumerate all entities in a specific industry (e.g., all ad-tech companies). - You need a dataset of surveillance entities for analysis or reporting. - You are building a comprehensive surveillance landscape map. Do NOT use this tool when: - You need the full profile of a specific entity — use `get_entity` instead. - You are searching by entity name — use `search` instead. - You need domain-level data — use `list_domains` instead. Inputs: - `industry` (query, optional): Filter by industry classification. Examples: `ad_tech`, `analytics`, `data_broker`, `social`, `crm`. - `limit` (query, optional): Results per page. Max 100 (paid), 20 (free). Default 50. - `cursor` (query, optional): Pagination cursor from previous response's `next_cursor`. Returns: - Array of entity list items (slug, name, parent_company, industry, data_categories, data_cost_usd). - `meta.has_more` and `meta.next_cursor` for pagination. Cost: - Free tier: up to 20 results/page, 50 req/day. Pro/enterprise: up to 100 results/page. Latency: - Typical: <150ms, p99: <400ms.
    ConnectorNo auth
  • Call this ONLY when the user explicitly asks to contact, reach out to, or request a quote/appointment from a Payotte-listed professional. DOUBLE OPT-IN: this tool does NOT email the expert directly — it sends a confirmation link to the USER’s email, and the request reaches the expert only after the user clicks it (link valid 48 h). Tell the user to check their inbox. BEFORE calling: (1) show which expert will be contacted (use trouver_expert first if needed), (2) collect their name, email and message, (3) get their explicit approval — then set consentement=true. Never invent contact details. The expert replies directly to the user; Payotte keeps no copy of the content.
    ConnectorNo auth
  • Lenders ranked on the comparable facilities they CURRENTLY HOLD on BDC schedules: same lien, a borrower industry containing the term (as the filer wrote it: health, software, industrial, business services), a facility size lower bound inside the band, entered since the window. Score = comparables 35%, recency 20%, size fit 15%, mark on the comparable book 15%, sponsors named 15%. Refuses one stale comparable, a book marked under 0.85 and passive holds under $2M. Sizes are lower bounds (BDC pieces), never the commitment. `states` filters on borrower headquarters where DFX holds one (GLEIF, about one comparable in six today); the answer reports geo_coverage, so say how many comparables carried a state. This is the answer to 'find lenders for a $60M unitranche for a sponsor-backed healthcare services business': use it before search_private_credit, whose industry filter lists borrowers.
    ConnectorNo auth
  • Request an expert callback for a Bangalore real estate project. Use this when the user wants to speak to an expert but is not ready to visit yet. Lower commitment than a site visit — just captures name, phone, and preferred call time. Call this when the user says: - "I want to know more", "can someone call me", "I'd like a callback" - "talk to an expert", "get more information", "not ready to visit yet" - "call me back", "have someone reach out" Required: rera_number, user_name, user_phone Optional: preferred_time (e.g. 'Morning', 'Afternoon', 'Evening') conversation_summary: Summarise in 2-3 bullet points what the buyer is looking for and any questions they raised — this goes to the expert who calls them back. Returns confirmation with callback reference ID.
    ConnectorNo auth
  • Deploy several connected services in one go (e.g. a frontend + an API). Call this when the user's project is split across multiple repos that must talk to each other; for a single repo use deploy_app. Each service is a public GitHub repo that gets its own URL. Wire them by setting an env var to the exact token ${services.<otherServiceName>.url} — Dockhold injects that service's live URL once it deploys. Give the backend its own database with "db":"enable" (DATABASE_URL is injected; a pure frontend doesn't need one). Builds run in parallel; poll get_app_status with each returned app_id.
    ConnectorNo auth
  • Returns currently-available expert taglines (pseudonymous descriptions of the kinds of expertise on hand) plus the real-time count of online expert seats and estimated wait. Use this as a cheap pre-flight check before calling a paid tool. Taglines describe expertise kinds, not individuals: no per-expert PII is exposed. Free.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Pricing/details for Edge Thirteen's current industry primer, sourced to each firm's own 10-K.

  • Guide user-led frontend design decisions from project brief through implementation review.

  • List the taxonomy domains the company has indexed — with document counts, expert counts, and coverage levels — so an agent can decide whether to query before spending a Knowledge Token. Returns one row per domain with the canonical `taxonomy_domain` slug, document/chunk counts, expert count, coverage level (expert | partial | none), the single_expert risk flag, and the top contributor by authority. Use the slug as the `domain` filter on a follow-up `query_knowledge` call. Zero Knowledge Tokens consumed.
    ConnectorNo auth
  • Returns currently-available expert taglines (pseudonymous descriptions of the kinds of expertise on hand) plus the real-time count of online expert seats and estimated wait. Use this as a cheap pre-flight check before calling a paid tool. Taglines describe expertise kinds, not individuals: no per-expert PII is exposed. Free.
    ConnectorNo auth
  • Delete one NACE industry-monitoring subscription by its id (from list_my_subscriptions); Firmaradar then stops delivering webhooks for that industry. The subscription must belong to the authenticated user. Idempotent — deleting an id that is already gone returns already_absent=true rather than an error. Reversible only by re-subscribing. Call only when the user has asked to stop monitoring an industry.
    Connector
    Destructive
    No auth
  • Read a company's own public website and extract structured company intelligence: name, description, services, market, industry, team size, tech stack and positioning. Call this when the user asks to research a company from its site before a campaign or a draft. Cached 7 days per domain; a repeat call reads the cache. Charges website_intel credits per call; campaignstack_estimate_cost gives the number before you commit.
    ConnectorAPI key
  • [Taxonomy X.174 — baseline response (public data only)] Optimize out-of-pocket spend across a sequence of planned services. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).
    ConnectorNo auth
  • The industry values `post_dataforseo_keywords_bing_audience_live` accepts. Free: upstream cost is 0. Read it before composing an audience request - an unrecognised industry is rejected, not ignored. The job-function list is `get_dataforseo_keywords_bing_audience_job_functions`.
    ConnectorOAuth
  • Returns all industry categories and their business types with IDs. Use the business type IDs in search_businesses (businessTypeIds) to filter listings by category. Call this first when you need to discover which IDs to use for a given industry or business type.
    ConnectorOAuth
  • Returns all industry categories and their business types with IDs. Use the business type IDs in search_businesses (businessTypeIds) to filter listings by category. Call this first when you need to discover which IDs to use for a given industry or business type.
    ConnectorOAuth
  • Returns AdCritter design guidance for an entity at a caller-chosen guidance level - screen experiences, API integration patterns, and design philosophy. The default ('full') returns step-by-step prescription (exact layouts, colors, copy text, column orders). Request 'patterns' for balanced hints including common design patterns with softened vocabulary. Request 'facts' if you have strong visual-design instincts and just want API integration bindings (or call adcritter_get_api_reference and adcritter_get_usage_guide directly and skip this tool). Guidance is format-agnostic - it describes outcomes and integration, never prescribes frameworks or architecture. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, geo, media-asset, plan, report, settings.
    ConnectorNo auth
  • One industry: metadata + a top sample of its member providers (ranked, with the total). Use find_providers?industry=slug for the full list, or view=full here. Results carry `next`: the sub-resources that exist for this entity and the exact tool call that retrieves each, computed from this record. Pass include_next=false to omit it.
    ConnectorNo auth
  • The front door for one AI investment decision. CALL THIS FIRST when the user describes an AI idea in ordinary language or asks whether it should proceed. It resolves industry, revenue, business function, AI tier and organisational readiness, then returns one clarification covering every unresolved input or an Accelerate, Fix or Stop verdict. Ask that clarification once and call this tool again with the answers in the explicit fields. Use work_architecture to test whether the end-to-end workflow, affected roles, human decision rights and performance measures have been redesigned. A stated gap or missing work architecture evidence blocks Accelerate and stays visible in the audit trail. Pillar scores and work architecture evidence remain optional inputs, but unresolved values are never guessed and cannot unlock Accelerate. Use score_initiative when the canonical fields are already known, score_portfolio for several initiatives, and diagnose_process for measured waste in a running process. Pure deterministic calculation, no network, auth or side effects.
    ConnectorNo auth
  • Search Sponsorable's podcast-sponsorship database for brands that sponsor podcasts — the deep-research/Responses-API compatibility interface, paired with fetch. Matches sponsor names and domains and returns citable documents; pass a result's id to fetch for the full profile. For filtered or paginated search (category, industry, recency), use search_sponsors instead.
    ConnectorNo auth
  • List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
    ConnectorNo auth
  • One-call identity + industry-financial-ties transparency profile for a US healthcare prescriber. Joins two keyless federal sources: the NPPES NPI Registry (identity - NPI, specialty, city/state, active status) and CMS Open Payments / Sunshine Act (industry payments disclosed to that prescriber - total dollars, payment count, top paying manufacturers, and associated drugs/products for the most recent program year with data). Provide a last_name (ideally with first_name + state) or an exact 10-digit npi. The name resolver picks the NPPES record that genuinely matches the requested name (never a blind top hit), and payments are pinned to that exact NPI across recent program years. This is a TRANSPARENCY profile drawn from public records, NOT a judgment: industry payments to physicians are lawful and publicly disclosed, and their presence is not evidence of wrongdoing. A source that fails is noted, not fatal. Premium cross-source synthesis; verify against the primary sources.
    ConnectorNo auth
  • Returns a 0-100 Clinical Trial Complexity Index (weighted shares of late-phase, large-enrollment, industry-sponsored, RCT, and blinded trials in ClinicalTrials.gov active/recruiting snapshots; 50=baseline, monthly since 2010) with score, trend, top_drivers, and methodology_version. Call when the user asks about clinical-trial landscape complexity, trial design trends, or CRO capacity pressure, or when timing site-selection bids, site fees, or recruitment strategy. Updates: monthly.
    ConnectorNo auth