Data Vending MCP

com.869biz.data-vendingPublished by data-vending.869biz.comOfficial publisherv1.0.0Updated Oct 24, 2026

x402 dataset vending for AI agents: list, preview, quote, purchase, needs intake, and consultation.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for x402 dataset vending, letting an assistant list, preview, quote, purchase datasets, submit needs and request consultation.

What you can do
  • List and preview available datasets
  • Request quotes and purchase datasets through x402 payment
  • Submit a needs intake describing required data
  • Request consultation about datasets
When to use it
Use when an assistant needs to find, evaluate or buy datasets from this vendor, or to hand over a data requirement for follow-up. The tool list is not published, so confirm the exact capabilities before relying on it.
Requirements
A remote streamable HTTP endpoint at mcp.data-vending.869biz.com; no authentication, environment variables or headers are declared. Purchases presumably require an x402-capable payment setup, though the input does not specify one.
Before you install
The server is described as handling purchases, so assistant actions may spend money; treat any purchase step as a paid transaction and confirm before proceeding. No authentication is declared, so check how access and payment are actually secured. Submitting a needs intake or consultation request sends your data requirements to the vendor.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.869biz.data-vending%2Fdata-vending-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "data-vending": {
      "type": "http",
      "url": "https://mcp.data-vending.869biz.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

17% 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 daysRequired25 pts

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

  • Auth declaredRequired10 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.