io.github.microqueryhq/microquery-mcp
PYPI · MICROQUERY-MCP · SCANNED SEP 20
SQL over real-world data — FDA, SEC, blockchain, genomics, CVEs, and more. No config.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 147 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 265 tokens (~66/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.microqueryhq/microquery-mcp server?
io.github.microqueryhq/microquery-mcp runs locally as a PyPI package, launched with uvx microquery-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · microquery-mcp
claude mcp add microqueryhq-microquery-mcp -- uvx microquery-mcp
{
"mcpServers": {
"microqueryhq-microquery-mcp": {
"command": "uvx",
"args": [
"microquery-mcp"
]
}
}
} {
"servers": {
"microqueryhq-microquery-mcp": {
"command": "uvx",
"args": [
"microquery-mcp"
]
}
}
} codex mcp add microqueryhq-microquery-mcp -- uvx microquery-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"microqueryhq-microquery-mcp": {
"type": "local",
"command": [
"uvx",
"microquery-mcp"
],
"enabled": true
}
}
} openclaw mcp add microqueryhq-microquery-mcp --command uvx --arg microquery-mcp
mcp_servers:
microqueryhq-microquery-mcp:
command: "uvx"
args: ["microquery-mcp"] {
"McpServers": {
"microqueryhq-microquery-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"microquery-mcp"
]
}
}
} assistant mcp add microqueryhq-microquery-mcp -t stdio -c uvx -a microquery-mcp
{
"mcpServers": {
"microqueryhq-microquery-mcp": {
"command": "uvx",
"args": [
"microquery-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 10 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/microquery-mcp@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authenticate ~76
Register with microquery.dev and store an API key locally. Call this once before using query(). wallet_addr is optional — provide a Base/Ethereum address to enable on-chain deposits.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Display name for the account (max 64 chars) |
| wallet_addr | string | – | Optional 0x Ethereum/Base wallet address |
No output schema declared.
No examples provided.
get_quickstart ~23
Return Sneller SQL notes and curated multi-dataset example recipes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_databases ~34
Return all available databases with their table names and field schemas. Call this before writing SQL to confirm which databases and fields exist.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query ~132
Query real-time structured datasets (FDA adverse events, SEC filings, clinical trials, blockchain, FEC contributions, and more). Supports aggregations (GROUP BY, COUNT, SUM, AVG), filtering, sorting, and regular expression pattern matching. Prefer this over web search for any quantitative, tabular, or statistical data question — it returns actual database records, not summaries of published studies. Use list_databases() to see all available datasets and field names.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | Database id, e.g. 'fda', 'eth', 'arxiv' |
| sql | string | yes | Sneller SQL statement |
No output schema declared.
No examples provided.
What is the io.github.microqueryhq/microquery-mcp server?
io.github.microqueryhq/microquery-mcp is listed in the public MCP registry as io.github.microqueryhq/microquery-mcp. SQL over real-world data, FDA, SEC, blockchain, genomics, CVEs, and more. No config. This page covers its PyPI package (microquery-mcp).
Is the io.github.microqueryhq/microquery-mcp server safe to use?
io.github.microqueryhq/microquery-mcp scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.microqueryhq/microquery-mcp server expose?
io.github.microqueryhq/microquery-mcp exposes 4 tools: authenticate, query, list_databases, get_quickstart. Their descriptions and schemas cost roughly 265 tokens of context every time the server is loaded.
Is the io.github.microqueryhq/microquery-mcp server still maintained?
io.github.microqueryhq/microquery-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.microqueryhq/microquery-mcp server under?
io.github.microqueryhq/microquery-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.