io.github.shagarwal/databazaar
REMOTE · API.DATABAZAAR.IO · 3 COMPONENTS
Search and preview datasets publicly. Account-required full data via MCP.
Available components
Last scanned (3 hours ago)
Scores higher than 89% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.80 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://api.databazaar.io/mcp/public
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.databazaar.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| databazaar.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.databazaar.io/mcp/public | Unreachable | ||
| http (plaintext) | http://api.databazaar.io/mcp/public | HTTPS enforced |
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 →
get_dataset ~66
Get full metadata for a specific dataset — schema, column counts, quality score, price anchoring, and a forwardable purchase pitch. Includes a checkout_url for one-click human purchase and a human_pitch field for operator messaging.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | The dataset ID to retrieve |
No output schema declared.
No examples provided.
preview_sample ~130
Preview sample rows of a dataset to verify it contains the expected columns, format, and quality. Returns a signed download URL for ~50 rows plus the schema. Pass an optional question to get a synthesized answer from the sample (e.g. "average price in 2024") — no purchase required.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | The dataset ID to preview |
| question | string | – | Optional natural-language question to answer from the sample (e.g. "average rent in SF", "count of records per state"). Returns a synthesized_answer field with deterministic aggregates if the questio… |
No output schema declared.
No examples provided.
search_datasets ~188
Search the DataBazaar marketplace for datasets matching a natural-language query, with optional filters for category, price, quality score, and pricing type. Returns ranked listings with prices, quality scores, and checkout URLs. When results are empty, log_data_gap can post a bounty to signal demand to sellers.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category: geographic, pricing, sensor, images, text, financial, scientific, social, retail, other |
| limit | integer | – | – |
| max_price | number | – | Maximum price in USD — omit to include all prices |
| min_quality_score | number | – | Minimum assessed sample structure score (0-100); unassessed listings are excluded. See https://databazaar.io/quality for the rubric and limitations. |
| pricing_type | string | – | – |
| query | string | yes | Natural language search query describing the data needed |
No output schema declared.
No examples provided.
How do I install the io.github.shagarwal/databazaar MCP server?
io.github.shagarwal/databazaar is a hosted endpoint at https://api.databazaar.io/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.databazaar.io
claude mcp add --transport http shagarwal-databazaar 'https://api.databazaar.io/mcp/public'
What is the io.github.shagarwal/databazaar MCP server?
io.github.shagarwal/databazaar is an MCP server listed in the public MCP registry as io.github.shagarwal/databazaar. Search and preview datasets publicly. Account-required full data via MCP. This page covers its hosted endpoint (https://api.databazaar.io/mcp/public).
Is the io.github.shagarwal/databazaar MCP server safe to use?
io.github.shagarwal/databazaar scores 84 out of 100 on VerifyMCP. 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.shagarwal/databazaar MCP server expose?
io.github.shagarwal/databazaar exposes 3 tools: search_datasets, get_dataset, preview_sample. Their descriptions and schemas cost roughly 384 tokens of context every time the server is loaded.
Does the io.github.shagarwal/databazaar MCP server require authentication?
Its publisher declares no required credentials for io.github.shagarwal/databazaar. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.shagarwal/databazaar MCP server still maintained?
io.github.shagarwal/databazaar is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.