myriade

{
  "id": "aix_814f950f56",
  "name": "myriade",
  "operator": "(unclaimed - source: registry-official · publisher: ai.myriade)",
  "description": "Explore and query your data warehouse through Myriade's AI data analyst agent.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "media-catalog",
    "sql-database"
  ],
  "protocols": {
    "mcp": "https://app.myriade.ai/mcp/",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 886,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 60,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T20:01:25.296Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://www.myriade.ai/"
    }
  ],
  "profile": {
    "mcp_server": "myriade_mcp",
    "mcp_version": "1.21.0",
    "tool_count": 19,
    "tools": [
      {
        "name": "myriade_list_databases",
        "description": "List databases configured in Myriade (paginated, sorted by name).\n\nReturns paginated database connections with their IDs, names, engines,\nand descriptions. Use the database ID with other tools.\n"
      },
      {
        "name": "myriade_get_database_info",
        "description": "Get detailed information about a specific database connection.\n\nReturns information about the database including its name, engine type,\ndescription, write mode, and any AI memory notes.\n"
      },
      {
        "name": "myriade_list_tables",
        "description": "List tables in a database (paginated, sorted by database/schema/name).\n\nReturns a flat, paginated list of tables. Each item has database_name,\nschema, and name fields. The response's `dialect` is the SQL dialect\nto use with myriade_query on this database.\n"
      },
      {
        "name": "myriade_get_table_schema",
        "description": "Get the column-level schema for a specific table.\n\nReturns column names, data types, and descriptions for the table,\nplus the SQL `dialect` to use with myriade_query on this database.\nWhen the name is ambiguous across schemas, the candidates are returned\nunder `matches` instead — pass `schema_name` to pick one.\nRaises if the user has no access to the table under governance.\n"
      },
      {
        "name": "myriade_query",
        "description": "Execute a read-only SQL query against a database.\n\nWrite the SQL in the dialect of the target database's engine — see the\n`dialect` field returned by myriade_list_tables and\nmyriade_get_table_schema, or the engine in myriade_list_databases.\nWrite operations (INSERT, UPDATE, DELETE, DROP, etc.) are blocked.\nReturns up to 50 rows of results with column metadata. Successful\nqueries are saved in Myriade; the response's `query_id` can be\nreplayed later with myriade_get_query_results without resending SQL.\n"
      },
      {
        "name": "myriade_get_query_results",
        "description": "Re-execute a saved Myriade query and return fresh results.\n\nThe query's SQL always re-runs under the caller's governance policies\n(table permissions, column masking) — results are never served from\nMyriade's cached snapshot.\n\nPrefer this over myriade_query for recurring metrics (dashboards,\ncockpits): the SQL stays governed in Myriade instead of travelling\nthrough prompts. Write statements are blocked. Returns up to 50 rows\nwith column metadata, same shape as myriade_query.\n"
      },
      {
        "name": "myriade_sample_data",
        "description": "Get sample rows from a table to understand the data.\n\nReturns a random sample of up to ``limit`` rows (max 20).\n"
      },
      {
        "name": "myriade_search_catalog",
        "description": "Search the data catalog for tables, columns, or terms by name/description.\n\nUses fuzzy matching and full-text search. Keep queries short\n(1-2 words) for best results.\n"
      },
      {
        "name": "myriade_read_asset",
        "description": "Get detailed information about a catalog object (table, column, schema,\nor glossary term — assets and terms share one id space).\n\nReturns the asset's description, tags, status, columns (for tables),\nsample data, parent hierarchy, and activity feed; for a glossary term,\nits definition, synonyms, related terms, and activity feed.\n"
      },
      {
        "name": "myriade_update_asset",
        "description": "Update a catalog asset's documentation (requires edit rights).\n\n- ``description`` replaces the existing description (auto-sets status to\n  \"draft\" if status is null).\n- ``tag_ids`` replaces all tags (accepts names or UUIDs; auto-creates\n  missing tags).\n- ``status`` is \"draft\" (needs review) or \"published\". Only use\n  \"published\" with high confidence.\n\nUse ``myriade_request_catalog_change`` instead when you lack edit rights\nor are not confident enough to write directly.\n"
      },
      {
        "name": "myriade_request_catalog_change",
        "description": "Propose a catalog change for the data team to review (no edit rights needed).\n\nCreates a reviewable suggestion routed to the asset's reviewers. Does NOT\nchange the published catalog until approved.\n\nUse this instead of ``myriade_update_asset`` when you lack edit rights or\nare not confident enough to write directly.\n"
      },
      {
        "name": "myriade_list_reports",
        "description": "List or search reports (documents) written in Myriade.\n\nWithout ``query`` returns the most recently updated reports first; with\n``query`` returns the best matches first. Only reports the caller may see\nare returned. Read one with myriade_read_report.\n"
      },
      {
        "name": "myriade_read_report",
        "description": "Read a report's full markdown content.\n\nApplies the same visibility rule as the web app; a report the caller may\nnot see returns a \"not found\" error. To create or edit a report, use\nmyriade_ask — the analyst agent knows how reports are structured.\n"
      },
      {
        "name": "myriade_ask",
        "description": "Ask a natural language question about a database using Myriade's\ndata analyst agent.\n\nThe agent will explore the database schema, search the catalog, run SQL\nqueries, and analyze the results to answer your question. Use this for\ncomplex analytical questions that require multiple steps; for simple\nschema lookups or direct SQL, prefer the other tools.\n\nThe run executes in the background as a regular Myriade conversation\n(visible in the web UI). If it finishes quickly the answer is returned\ndirectly; otherwise the tool returns ``{\"status\": \"running\",\n\"conversation_id\": ...}`` — poll myriade_get_a"
      },
      {
        "name": "myriade_get_answer",
        "description": "Retrieve the result of a myriade_ask run.\n\nReturns ``{\"status\": \"completed\", \"answer\": ...}`` once the analyst\nagent has answered, or ``{\"status\": \"running\"}`` while it is still\nworking — keep polling in that case. ``{\"status\": \"failed\"}`` /\n``{\"status\": \"quota_exceeded\"}`` carry the run's error. ``{\"status\":\n\"no_answer\"}`` means the run is gone without a recorded answer (agent\nstopped silently, or the server restarted): start a new myriade_ask run.\n"
      },
      {
        "name": "myriade_monitoring_overview",
        "description": "Snapshot of a database's monitoring board: check count, standing alerts\n(open / acknowledged / known) with their headlines, recent notifications\nand triage notes, followed by the open alerts as JSON — each with its\ninvestigation and evidence while they fit, then as listing lines, with\n``shown`` / ``total`` / ``detailed`` saying which.\n\nAlert ids feed myriade_triage_alert; check ids feed myriade_get_check.\nInvestigation details are redacted unless you manage the database.\n"
      },
      {
        "name": "myriade_get_check",
        "description": "Get a monitoring check (name, SQL, severity, cadence, status) and its\nmost recent run results, newest first.\n\nOn governed databases the SQL and evidence rows are redacted unless you\nmanage the database or authored the proposal.\n"
      },
      {
        "name": "myriade_propose_check",
        "description": "Propose a monitoring check for the user to review in Myriade.\n\nThis creates a PROPOSAL, never an active check: nothing runs until a\ndatabase owner or org admin accepts it in the app. The SQL is test-run\nonce under your governance context to validate it.\n\nContract for ``check_sql``: it MUST return rows ONLY when something is\nwrong (zero rows = healthy) and use relative time (``now() - interval``),\nnever absolute dates. Minimum cadence is 5 minutes. Names are unique per\ndatabase — read myriade_monitoring_overview before proposing a\nnear-duplicate.\n"
      },
      {
        "name": "myriade_triage_alert",
        "description": "Triage an alert (requires manage access: database owner or org admin).\n\n- ``resolve``: the underlying problem is handled or gone.\n- ``acknowledge``: keep it standing with a ``statement`` of what is\n  happening — only for a situation that may worsen.\n- ``dismiss``: false positive / expected; refused while the check still\n  trips (it would just respawn).\n- ``snooze``: silence for ``hours`` with a ``statement``; reopens by itself\n  if the check still trips afterwards.\n- ``reopen``: send a parked alert back to \"needs action\" with a\n  ``statement`` of what is no longer covered.\n"
      }
    ],
    "profiled_at": "2026-09-24T20:01:25.296Z"
  },
  "unreachable": false,
  "payment_method": "oauth"
}