Home / MCP registry index / md.mostlyright/datasets

Mostly Right

md.mostlyright/datasets in the official MCP registry. Endpoint https://mostlyright.md/api/mcp.

The registry describes it as: Search, sample and query open reproducible datasets published as immutable Parquet with schemas.

We read its 81 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http datasets https://mostlyright.md/api/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "datasets": {
      "url": "https://mostlyright.md/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"datasets","type":"http","url":"https://mostlyright.md/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

search_datasets get_dataset list_tables get_table_schema sample_rows get_download_instructions get_access_instructions search fetch query_table search_table catalog_search list_connected_datasets connect_dataset create_dataset configure_table_view update_dataset generate_cover set_dataset_visibility archive_dataset list_my_datasets get_my_dataset list_dataset_events list_recipes get_recipe register_recipe explain_recipe forecast_recipe test_recipe propose_revision replay_run start_run confirm_run approve_full_run cancel_run get_run run_events list_runs compare_runs query_run sample_table list_column_values preview_table_search run_artifacts get_artifact_download write_note list_notes list_table_parts verify_run promote_table reschedule_table demote_table refresh_table resync_table archive_table rename_table get_table diagnose_table list_source_credentials list_models and 21 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): 167dfa9ec0f7f74a. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/md-mostlyright-datasets/badge.svg)](https://lazaretto.dev/mcp-registry/md-mostlyright-datasets)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.