Skip to main content
Glama
510,487 tools. Updated 2026-09-04 03:24

"Software or solutions for managing a fleet of computers" matching MCP tools:

  • Who am I? Returns the signed-in account: email, @handle, plan + limits, counts of sites/domains/drives, and connected DNS providers. Call this first to orient before managing sites or domains.
    Connector
  • Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — `autonomous` (Munimji does it on its own, e.g. OCR extraction, running reports), `approval` (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), `assist` (co-pilot, e.g. guided onboarding, voice), or `manual` (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in `businessDescription`; optionally filter by `area` or `autonomy`. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans.
    Connector
  • Count vehicles registered in Texas from the Texas DMV (TxDMV) registration series: total vehicles registered statewide in a fiscal year, split into passenger cars, pickup trucks of one ton or less, and motorcycles, each with its share of the fleet. Answers "how many vehicles are registered in Texas", "how many motorcycles are registered in Texas", "how many pickup trucks are registered in Texas", and growth questions across years such as how the Texas fleet changed from 2001 to 2021. TxDMV publishes this series as one statewide row per fiscal year, covering fiscal years 2001 through 2021, so every response reports its fiscal year and vintage. For a ZIP-code or county breakdown of a registered fleet, ca_dmv_vehicle_registrations covers California at ZIP × make × model-year × fuel grain.
    Connector
  • Count vehicles registered in Delaware by fuel type from the Delaware DMV's own statewide snapshot: petrol, diesel, battery-electric, plug-in hybrid, propane, compressed natural gas, ethanol and the residual "Other (Or None)" category, with a statewide total of every registered vehicle. Answers "how many vehicles are registered in Delaware", "how many diesel vehicles are registered in Delaware", and "how many electric cars are in Delaware". Delaware publishes this as one statewide row per fuel type, refreshed monthly, so the returned total is the whole Delaware fleet. Delaware writes plug-in hybrids as "Electric+Gas". For EV share of the fleet use de_dmv_ev_adoption; for Delaware rebate awards use de_dmv_ev_rebates.
    Connector
  • Get the public dashboard summary The free marketing-dashboard rollup: the network-wide host rollup (fleet count + mean uptime/latency), the hourly fleet-average p50 latency trend over the last 24h, and the top-10 providers by market share (0..1 fraction). No host list, full registry or arbitrary per-host uptime is exposed.
    Connector
  • Generate an audit-ready agent-governance policy for a fleet. PREMIUM (license). Covers inventory cadence, ownership rules, least-privilege approval gates, injection defense, logging/retention, and decommissioning triggers. Typical input {"fleet_context": "20 agents, 3 with shell access, one finance bot"} returns {"policy": ..., "sections": {...}, "context_note": ..., "audit_checklist": ["...", ...]}. Use when a fleet needs a written policy document. Not for assessing what the fleet currently does (inventory_report, audit_mcp_config). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Generate an audit-ready agent-governance policy for a fleet. PREMIUM (license). Covers inventory cadence, ownership rules, least-privilege approval gates, injection defense, logging/retention, and decommissioning triggers. Typical input {"fleet_context": "20 agents, 3 with shell access, one finance bot"} returns {"policy": ..., "sections": {...}, "context_note": ..., "audit_checklist": ["...", ...]}. Use when a fleet needs a written policy document. Not for assessing what the fleet currently does (inventory_report, audit_mcp_config). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    Connector
  • Find every company a person runs or represents - across BOTH registers in one call (cross-border person search). Read-only. Parameters: - name (required): person name substring, case-insensitive, e.g. "Mustermann". - country (optional, default "all"): "AT" | "DE" | "all". - page_size (optional, default 25): results per country. - status (optional, default "all"): "active" | "inactive" | "all". Returns the merged search_companies envelope ({countries, results, per_country, notices}) plus ``person_query``; every result card carries ``country``, ``company_id`` and the matched manager. AT matches the primary managing director, DE matches all managing directors AND registered signatories. IMPORTANT: matching is by name and the registers publish birth YEAR only - a shared name across companies or countries does not prove the same person (the notice says so; use birth years and context to corroborate). For general company search use search_companies with other filters; manager_name can be combined there too.
    Connector
  • Fleet-wide membership-eligibility coverage: how many US credit unions RateAPI holds live, verbatim-evidenced membership rules for (and what share of the active fleet that is), how the rules split by kind, how many counties, states and employers they name, verification status, and freshness. The `authority` object distinguishes exact immutable active publications from older graph and flat compatibility records; `evidence_sources` reports the public source mix. Returns a dated `headline` sentence that can be quoted verbatim. Use this BEFORE find_eligible_credit_unions or check_membership_eligibility when the user asks how complete, authoritative, or fresh the eligibility data is. Aggregate only — no institution-level rows; those come from the eligibility tools. No API key required. Never reports credit data: the rule schema has no condition kind for credit score, income or debt. An institution absent from the graph is undecided, never ineligible.
    Connector
  • Get a Stripe billing portal URL for managing payment methods and invoices. Returns a URL (not a redirect) that the human can open in a browser. Requires: API key with read scope. Args: flow: Optional. Set to "payment_method_update" to go directly to the payment method update page. Returns: {"url": "https://billing.stripe.com/p/session/..."}
    Connector
  • Free discovery: corpus-backed SELLER reputation for a merchant/provider wallet. Answers "is this provider organic, narrow, or a wash fleet?" from the merchant's inbound payment graph over the last 90 days: unique payers, repeat-payer %, heavy-fleet revenue concentration, captive-payer % (onboarding-sink proxy), and a scripted-fleet uniformity signal, and top_payer_tx_pct (captive concentration). Returns wash_label + reputation tier + wash_flagged (tri-state: true | false | null; null = never evaluated, not clean). Complements score_wallet_for_intel (payer side) with the seller side. Fail-open: a DB gap returns wash_label/tier "unknown" AND wash_flagged=null (plus wash_confidence) - an unevaluated verdict, never a clean one. This is the free seller signal; the paid per-wallet renorm model + signed v6 receipt remain at GET /v1/intel/trust/{wallet} (0.05 USDC).
    Connector
  • Free preview of breaking changes / new releases for a software dependency. Pass an npm/PyPI `package` (resolved and fetched live if not already tracked) or a GitHub `repo` (owner/repo). Returns up to 5 recent changes plus the package's current version. Full history, significance filtering, and the LLM brief are paid via x402.
    Connector
  • REQUIRED onboarding entrypoint for A-Team MCP. MUST be called when user greets, says hi, asks what this is, asks for help, explores capabilities, or when MCP is first connected. Returns platform explanation, example solutions, and assistant behavior instructions. Do NOT improvise an introduction — call this tool instead.
    Connector
  • Fleet action-conditioned signal effectiveness (free read). Filters: source_type (e.g. youtube/rss/api/on_chain), signal_type, window (24h|7d|30d|90d|all). Returns, per matching signal_effectiveness collective insight, the fleet action taken, effect_size, confidence interval, contributing-agent count n, crowding_index, and staleness. Historical collective performance data aggregated across the fleet -- descriptive only, never a recommendation or a promise of results. Workflow: INTELLIGENCE step -- weigh a signal by how the FLEET's actions on it have historically resolved, alongside your own get_source_accuracy / get_my_performance track record.
    Connector
  • Get full detail for a Tuki solution: description, who it is for, capabilities, status and contact / CTA. Use after `list_solutions` or when the user asks about a specific Tuki product (WhatsApp Booking OS, boutique ticketing, rental inventory software, event post-sale, tailor-made tourism software).
    Connector
  • Get G2 software reviews. Returns ratings, pros, cons, use cases. Args: product: Software product name (e.g. 'Salesforce') max_results: Max reviews (default 20)
    Connector
  • Get public housing buildings and developments in a state. Queries HUD's open ArcGIS data for public housing inventory. No API key required. Returns building names, addresses, unit counts, and managing Public Housing Agency information. Args: state: Two-letter US state abbreviation (e.g. 'WA', 'TX'). city: Optional city name to filter results. limit: Maximum number of records to return (default 50, max 500).
    Connector
  • Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — `autonomous` (Munimji does it on its own, e.g. OCR extraction, running reports), `approval` (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), `assist` (co-pilot, e.g. guided onboarding, voice), or `manual` (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in `businessDescription`; optionally filter by `area` or `autonomy`. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans.
    Connector
  • Searches across ALL Fluentive content — features, pricing, FAQ, comparisons, and live blog posts — for topics relevant to a query. Use for generic questions like 'does Fluentive support X?', 'is it good for Y type of business?', or 'I need software that does Z'. Returns the top 5 most relevant content excerpts.
    Connector
  • List the project's store categories (the source side of category mapping and of a feed's category filter). Returns {categories:[{id, name, path}], returned, total, hasMore, nextOffset}; `path` is the full breadcrumb (e.g. "Electronics > Computers > Laptops"). Use the ids with set_category_mapping (map store categories to a marketplace category) or set_feed_filter (category_ids). project_id is OPTIONAL (inferred for a single-project customer; project_id_required otherwise — then call list_projects). Paginated: default limit 200, max 1000. When hasMore is true, call again with offset = nextOffset and keep paging until hasMore is false to see every category.
    Connector