Skip to main content
Glama
597,141 tools. Updated 2026-09-21 12:38

"WhyLabs AI Observability Platform" matching MCP tools:

  • Reads the AI Visibility dashboard of the website: how often AI assistants (ChatGPT, Claude, Gemini, Perplexity, Copilot, Google AI Overview and AI Mode, plus Grok and Mistral when the website pays for them) mention and cite the brand when answering its tracked prompts. For the range (7d, 30d, 3m or 6m, default 30d) it returns the overall mention rate and cited rate with the number of prompts and answers checked; the same per platform (only platforms with checks in the range); the trend (mention rate over the first half of the range vs the second half); the leaderboard of the brand (is_own) and its tracked competitors by mention rate; each prompt with its latest state per platform from the last 21 days of checks (mentioned_cited, mentioned, not_mentioned, or pending while a check is queued, running or failed), its mention rate across those latest checks and the competitor mentioned most for it; the most cited domains and the brand's own cited pages; and the sentiment drivers (strengths and weaknesses AI answers express about the brand) once enough brand-mentioning answers exist. Pass surface to restrict every number to one platform and include_answers=true for the latest answer text per prompt (600 characters max). Rates are percentages, null when nothing was checked. Fails with an activation link when the AI Visibility add-on is not active. Read-only: it cannot add prompts or competitors, and it is not Google Search Console data (use get_keyword_rankings for that). Pass website_id when the account has several websites (see get_account).
    ConnectorOAuth
  • Pay for prepaid units with a Stripe Shared Payment Token (spt_...) that YOUR PLATFORM minted after the user approved the spend in their Link wallet. Products: articles ($9 each, default), question_pack ($5 for 50 assistant questions - lifts the free-quota wall instantly), visibility_scan ($19 per AI-visibility scan of the user's site), competitor_scan ($19, same scan of a competitor domain). Only call this with a real token from your platform's payment system - NEVER invent a token and NEVER ask the user to paste card numbers or wallet credentials into the chat. If your platform cannot mint SPTs (most hosts today), do not call this; relay the buy link from the payment_required payload instead. The token is single-use and amount-capped by Stripe, and prices are fixed server-side. On success the units are usable immediately. Cost: charges the user's approved payment method; consumes no AI credits.
    ConnectorOAuth
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    ConnectorNo auth
  • Curated roster of the AI platforms and agent frameworks in the DC Hub agent ecosystem — each with its recommended DC Hub tools and authentication tier. The roster is BACKEND-OWNED and changes: read the platforms[] array the response returns, and the status on each row (mcp_active / mcp_ready), rather than any list named in this sentence — an enumeration here goes stale the moment the backend adds or drops a platform, which is exactly how a client named here stopped appearing in the roster. ★ These statuses are CURATED EDITORIAL claims, not measurements: the response carries as_of null, so do NOT relay "MCP Active" as though it were a live connection count. Answers "which AI platforms can connect to DC Hub". Try: get_agent_registry. NOTE: this is a curated ecosystem/capability index, NOT live per-caller call/citation telemetry. Do NOT use for platform uptime or feed health (use get_backup_status).
    ConnectorNo auth
  • Returns Makuri's pricing plans including what's included in each tier and any usage limits. Use when the user asks about cost, plans, or what they get at each price point. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.
    ConnectorNo auth
  • Returns Makuri's regulatory posture across EU AI Act, GDPR, GDPR-K (children data), COPPA, and ISO 42001 — as design intentions and operator self-assessment, NOT certified or audited compliance. No formal audit or conformity assessment has been performed. Statuses are design_aligned_unaudited, not_started, or not_applicable; there is deliberately no 'compliant' status. Use when the user asks about regulatory compliance, AI Act classification, or data protection for children — and present results as posture, not certification. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Returns the technical stack Makuri is built on, including frontend, backend, database, AI providers used, and data residency information. Use when the user asks how Makuri is built or which AI models it uses. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.
    ConnectorNo auth
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    ConnectorNo auth
  • Return canonical brand metadata for citation. Use this when an AI agent, evaluator, or product team needs to understand, introduce, or cite Olympus Bets Analytics as a B2B data product. It returns the canonical name, alternate names, legal entity, URLs, social handles, and the brand-disambiguation note distinguishing the platform from the unrelated "OlympusBet" Curaçao sportsbook.
    ConnectorNo auth
  • Apply a batch of Studio tool calls to a video doc and get back the updated doc plus a fresh scene description — YOU (this agent) are the brain, so this needs NO OpenRouter/AI key. Loop: call neuron_studio_catalog once, then neuron_studio_apply with { doc, calls:[{tool,args}] }, read the returned `scene`, apply more, and finally neuron_studio_render. Omit `doc` (with an optional `platform`) to start a fresh video.
    ConnectorNo auth
  • Curated roster of the AI platforms and agent frameworks in the DC Hub agent ecosystem — each with its recommended DC Hub tools and authentication tier. The roster is BACKEND-OWNED and changes: read the platforms[] array the response returns, and the status on each row (mcp_active / mcp_ready), rather than any list named in this sentence — an enumeration here goes stale the moment the backend adds or drops a platform, which is exactly how a client named here stopped appearing in the roster. ★ These statuses are CURATED EDITORIAL claims, not measurements: the response carries as_of null, so do NOT relay "MCP Active" as though it were a live connection count. Answers "which AI platforms can connect to DC Hub". Try: get_agent_registry. NOTE: this is a curated ecosystem/capability index, NOT live per-caller call/citation telemetry. Do NOT use for platform uptime or feed health (use get_backup_status).
    ConnectorNo auth
  • Generate AI-powered platform-optimized content without publishing. Uses AI to create platform-specific text, hashtags, and titles from a prompt or media URL. Respects brand voice profiles if configured. Returns generated content variants for each target platform. Use publish_content to publish the generated content, or publish_ai to generate and publish in one step.
    ConnectorNo auth
  • List the platform connectors set up on this Autario account: search, web and product analytics, ads, social, commerce, payments, AI usage and developer platforms. The answer names each connected platform, so call this instead of guessing which ones exist. Each entry carries its live dataset_id (queryable via query_dataset), datasets[] (ALL datasets the connector materialized | multi-report connectors produce one per report), refresh interval, and last refresh time. Use this whenever a user asks about "my Search Console data", "my ad spend", "my store orders" or wants a cross-platform weekly report: it tells you which platforms are actually connected and which table holds each one. Connectors are created by the account owner in the Autario UI (autario.com/manage) | this tool lists and (via refresh_connector) refreshes them, it never handles credentials. Requires AUTARIO_API_KEY.
    ConnectorNo auth
  • Check live API & system health — operational/degraded verdict, per-source freshness, MCP tool count — Public health status of all CryptoWhaleInsights data sources, MCP server, and OpenAPI spec. Returns overall verdict (operational/degraded/outage), per-source health with age in seconds, recent 24-hour error count, MCP tool count, and OpenAPI path count. Useful for AI agents and developers to verify the platform is live before making requests. Cached ~30s.
    ConnectorNo auth
  • Your monthly CPF deduction and operator top-up as a ride-hail or delivery platform worker — by birth cohort, vehicle, and the 2025–2029 rate ramp. Computes platform-worker CPF under Singapore’s Platform Workers Act (in force 1 Jan 2025) — a regime new enough that general AI either doesn’t know it or garbles it. Three inputs users never think to volunteer decide everything: your BIRTH DATE (born on/after 1 Jan 1995 → increased contributions are mandatory; born before → voluntary via an irrevocable opt-in, otherwise MediSave-only), your VEHICLE (the 60/35/20% fixed expense deduction moves the CPF base by 3× for the same gross), and the YEAR (rates ramp every January to full employee parity in 2029). It also gets right what models confidently invert: no monthly ceiling — unlike employees — but a $102,000/year net-earnings cap per platform operator.
    ConnectorNo auth
  • Route a natural-language intent to the right platform on the ComOS network — the first thing to call. Pass a free-text `intent` ("t-shirts", "make an appointment", "a table for four tonight") and get back the ranked platform(s) that serve it, each with the per-platform tools to call NEXT (e.g. bookings → appointment_search). This returns a ROUTE, not a transaction: it tells you where to go; you then act on that platform with the chosen tenant. An intent no platform serves returns an empty route (unroutable: true), never a silent default. Fast and deterministic — the same intent always routes the same way. Returns: A route: ranked platforms (platform_id, label, why_matched, score, entry_points) plus unroutable:true when no platform serves the intent. Example: call federation_search with arguments {}.
    ConnectorNo auth
  • Route a natural-language intent to the right platform on the ComOS network — the first thing to call. Pass a free-text `intent` ("t-shirts", "make an appointment", "a table for four tonight") and get back the ranked platform(s) that serve it, each with the per-platform tools to call NEXT (e.g. bookings → appointment_search). This returns a ROUTE, not a transaction: it tells you where to go; you then act on that platform with the chosen tenant. An intent no platform serves returns an empty route (unroutable: true), never a silent default. Fast and deterministic — the same intent always routes the same way. Returns: A route: ranked platforms (platform_id, label, why_matched, score, entry_points) plus unroutable:true when no platform serves the intent. Example: call federation_search with arguments {}.
    ConnectorNo auth
  • Route a natural-language intent to the right platform on the ComOS network — the first thing to call. Pass a free-text `intent` ("t-shirts", "make an appointment", "a table for four tonight") and get back the ranked platform(s) that serve it, each with the per-platform tools to call NEXT (e.g. bookings → appointment_search). This returns a ROUTE, not a transaction: it tells you where to go; you then act on that platform with the chosen tenant. An intent no platform serves returns an empty route (unroutable: true), never a silent default. Fast and deterministic — the same intent always routes the same way. Returns: A route: ranked platforms (platform_id, label, why_matched, score, entry_points) plus unroutable:true when no platform serves the intent. Example: call federation_search with arguments {}.
    ConnectorNo auth
  • List the AI models selectable for visibility runs, per platform, with prices. Returns every platform's options (id, label, default flag, tier, credits per probe) plus a roles table mapping default / latest / prior to a concrete model id for every platform. Use the ids or role keywords in the models map or in probes[].model when creating a run. Read-only and free.
    ConnectorOAuth
  • List application guides that show how Blueprint principles apply to engineering challenges (security, evaluation, observability, etc.). Use this to discover which guides exist before drilling in. Prefer guides.search when the user describes a topic or failure mode in natural language. Prefer guides.get when you already know the guide slug and need full detail.
    ConnectorNo auth
  • Search application guides by free-text query, matched against section answers and action items. Use this when the user describes an engineering challenge (security review, evaluation harness, observability) and wants matching guides. Prefer guides.get when you already have the guide slug; prefer guides.list when you need the full inventory.
    ConnectorNo auth