Microquery Mcp

io.github.microqueryhqPublished by GitHub account microqueryhqv1.0.3Updated Oct 24, 2026

SQL over real-world data — FDA, SEC, blockchain, genomics, CVEs, and more. No config.

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

Lets an assistant run SQL against hosted real-world datasets such as FDA, SEC, blockchain, genomics and CVE data, with no configuration.

What you can do
  • Run SQL queries against hosted public datasets and get actual records back
  • List available datasets and their field schemas
  • Get Sneller SQL notes and multi-dataset example recipes
  • Register an account or link a wallet address manually
When to use it
Useful when you want an assistant to answer research questions over public datasets — drug safety, filings, clinical trials, genomics, crypto, vulnerabilities — without setting up your own database or writing SQL yourself.
Requirements
Runs locally as a Python package (Python 3.9+, stdlib only) launched via uvx, which requires uv installed separately, or by pointing the host at the script. Works in Claude Desktop, Cursor or other MCP hosts; desktop only. No API key or config needed: an account is auto-registered on the first query and the key is stored in a local token file.
Before you install
On first query the server registers an account using your OS username and stores an API key on disk. Queries start on a $0.10 trial credit, and the server automatically tops up the account up to 10 times at $2 each, so real money can be spent without an explicit prompt; once the allowance is exhausted a checkout URL is returned for adding USDC. Queries and account activity go to the Microquery service.

Installation

In SourceWeft

  1. Open Microquery Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

microquery-mcp

MCP server for Microquery — ask research questions about real-world data and get actual database records back. Works in Claude Desktop, Cursor, or any MCP-compatible AI host. Claude handles the SQL; you just ask the question.

No wallet required. Auto-registers on first query and runs on $0.10 trial credit (~1,600 typical queries).

See also

microquery-agent — autonomous agent for pipelines and cron jobs: register → deposit USDC → query → auto top-up. Use this if you want to run microquery unattended without an AI host.

Prerequisites

  • Python 3.9+
  • No third-party packages — stdlib only

Installation

Claude Desktop (recommended)

The easiest paths, in order of friction:

1. Registry install Find microquery in the Claude Desktop MCP marketplace or on smithery.ai and click Install. No config editing needed.

2. uvx install Add one entry to ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "microquery": {      "command": "uvx",      "args": ["microquery-mcp"]    }  }}

uvx requires uv to be installed separately (astral.sh/uv). Once installed, Claude Desktop will pick it up automatically.

3. Manual install (developers) Download microquery_mcp.py from this repo and point your host at it:

json
{  "mcpServers": {    "microquery": {      "command": "python3",      "args": ["/path/to/microquery_mcp.py"]    }  }}

Restart Claude Desktop after editing. The server appears in Settings → Developer with a green dot when connected.

Other MCP hosts (Cursor, etc.)

Use the same command / args pattern above. Consult your host's MCP documentation for the exact config format.

Tools

ToolDescription
query(database, sql)Run SQL against a microquery dataset. Auto-registers on first call.
authenticate(name, wallet_addr?)Manually register or link a wallet address.
list_databases()Show all available datasets and field schemas.
get_quickstart()Sneller SQL notes and multi-dataset example recipes.

How it works

  1. On the first query() call the server registers an account using your OS username (getpass.getuser()) via POST /v1/register and stores the API key in ~/.microquery/token.
  2. Subsequent calls use the stored key — no configuration needed.
  3. The new account starts with 100,000 µUSDC ($0.10) trial credit, covering roughly 1,600 typical queries.
  4. When trial credit runs low the server automatically tops up the account (up to 10 times, $2 each). Once the free allowance is exhausted a checkout URL is returned — visit it to add USDC and continue querying.

Available datasets

FDA adverse events · SEC EDGAR · clinical trials · ClinVar · arXiv · PubMed · Ethereum · Bitcoin · Base · DeFi TVL · FEC contributions · FRED economic series · NVD/CVE · OSV advisories · sanctions · FHFA house prices · GWAS · ClinPGx · malware samples · open food facts · world bank commodities · and more — call list_databases() for the full live schema.

Example

User:    What were the top adverse events reported for metformin last year?         And how does that compare to 2022 and 2023?Claude:  [queries fda.faers for each year, builds trend table]         GI events (diarrhoea, nausea, vomiting) were flat 2022→2024,         then spiked sharply in 2025 — consistent with the longevity/         obesity wave hitting FAERS with a lag. Lactic acidosis stayed         nearly flat across all four years despite overall volume growth.
User:    Can you cross-reference that with genomic profiles?Claude:  [queries clinpgx, clinvar, gwas — no SQL needed from user]         SLC22A1 rs628031 has a direct ClinPGx annotation for GI toxicity —         the strongest known genomic explanation for why diarrhoea and nausea         dominate the FAERS signal for metformin.

Source: README.md at commit aab3b7d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts