# Myriade MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.myriade%2Fmyriade
Registry id: `mcp-registry/ai.myriade/myriade`
Status: auth-required (checked 2026-10-26T23:36:45.573Z)

## Verdict

Myriade MCP server answered 99.81% of Glimind's liveness checks over 30 days, better than 24% of MCP servers, with 2214 ms median handshake and 13 outages in 90 days. Its agent-readiness grade is A (98/100) across 28 tools, costing an agent about 7,919 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.81% | 24% of MCP servers |
| Median handshake latency | 2214 ms | 4% of MCP servers |
| p95 handshake latency | 4196 ms | — |
| Checks in 30 days | 2,156 | — |
| Outages, 90 days | 13 | — |
| Median recovery | 4 min | — |
| Agent-readiness score | 98/100 (A) | 92% of MCP servers |
| Tools | 28 | — |
| Tool-list size for an agent | ~7,919 tokens | 33% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "myriade-mcp-server": {
      "type": "http",
      "url": "https://app.myriade.ai/mcp/"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http myriade-mcp-server https://app.myriade.ai/mcp/
```

## Tools (28)

- `myriade_ask`: Ask a natural language question about a database using Myriade's data analyst agent. The agent will explore the database schema, search the catalog, run SQL que
- `myriade_audit_list_map`: The organisation's audit value map: every domain (key, name, its document, zone count), every active zone (slug, name, domain, verdict, gain, star, last verifie
- `myriade_audit_read_levers`: Levers as their page shows them: every field, the class, the human follow-up (status, assignee, note) and the dated figures behind each. An id that is no lever 
- `myriade_audit_read_zones`: Zones as their page shows them: the record from the ```zone block, the dated figures recorded on the zone, its levers in short (id, name, stage, class, follow-u
- `myriade_audit_record_evidence`: Record a dated figure backing a zone (or one of its levers), linked to the query that computed it, on a connection you may read. Recording the same label again 
- `myriade_audit_record_lever`: Create a lever in a zone of the audit map, or update one by its id (an argument you omit keeps its value). Cite the returned id as <LEVER:id> in the zone docume
- `myriade_create_report`: Create a report owned by the caller, private until shared. Share it with myriade_set_report_access(visibility="everyone"): an audit zone or domain document join
- `myriade_edit_report`: Replace text in a report, as the caller (a version is recorded). Read it first with myriade_read_report. A published report is editable only by its owner or an 
- `myriade_get_answer`: Retrieve the result of a myriade_ask run. Returns ``{"status": "completed", "answer": ...}`` once the analyst agent has answered, or ``{"status": "running"}`` w
- `myriade_get_check`: Get a monitoring check (name, SQL, severity, cadence, status) and its most recent run results, newest first. On governed databases the SQL and evidence rows are
- `myriade_get_database_info`: Get detailed information about a specific database connection. Returns information about the database including its name, engine type, description, write mode, 
- `myriade_get_query_results`: Re-execute a saved Myriade query and return fresh results. The query's SQL always re-runs under the caller's governance policies (table permissions, column mask
- `myriade_get_table_schema`: Get the column-level schema for a specific table. Returns column names, data types, and descriptions for the table, plus the SQL `dialect` to use with myriade_q
- `myriade_list_databases`: List databases configured in Myriade (paginated, sorted by name). Returns paginated database connections with their IDs, names, engines, and descriptions. Use t
- `myriade_list_reports`: List or search reports (documents) written in Myriade. Without ``query`` returns the most recently updated reports first; with ``query`` returns the best matche
- `myriade_list_tables`: List tables in a database (paginated, sorted by database/schema/name). Returns a flat, paginated list of tables. Each item has database_name, schema, and name f
- `myriade_monitoring_overview`: Snapshot of a database's monitoring board: check count, standing alerts (open / acknowledged / known) with their headlines, recent notifications and triage note
- `myriade_propose_check`: Propose a monitoring check for the user to review in Myriade. This creates a PROPOSAL, never an active check: nothing runs until a database owner or org admin a
- `myriade_query`: Execute a read-only SQL query against a database. Write the SQL in the dialect of the target database's engine — see the `dialect` field returned by myriade_lis
- `myriade_read_asset`: Get detailed information about a catalog object (table, column, schema, or glossary term — assets and terms share one id space). Returns the asset's description
- `myriade_read_report`: Read a report's full markdown content. Applies the same visibility rule as the web app; a report the caller may not see returns a "not found" error. Edit it wit
- `myriade_request_catalog_change`: Propose a catalog change for the data team to review (no edit rights needed). Creates a reviewable suggestion routed to the asset's reviewers. Does NOT change t
- `myriade_sample_data`: Get sample rows from a table to understand the data. Returns a random sample of up to ``limit`` rows (max 20). 
- `myriade_search_catalog`: Search the data catalog for tables, columns, or terms by name/description. Uses fuzzy matching and full-text search. Keep queries short (1-2 words) for best res
- `myriade_set_report_access`: Change who can read a report: visibility (its owner only) and web publication (its owner or an org admin).
- `myriade_triage_alert`: Triage an alert (requires manage access: database owner or org admin). - ``resolve``: the underlying problem is handled or gone. - ``acknowledge``: keep it stan
- `myriade_update_asset`: Update a catalog asset's documentation (requires edit rights). - ``description`` replaces the existing description (auto-sets status to "draft" if status is nul
- `myriade_update_report_title`: Rename a report (an audit zone takes its document's title).

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.