Agent Data Api

io.sslip.195.82.231.168Published by 168.231.82.195.sslip.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Pay-per-call (x402/USDC-Base) web + crypto data tools for AI agents: audit, extract, crypto, DeFi.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

A remote MCP endpoint offering pay-per-call web and crypto data tools for AI agents, covering audit, extraction, crypto and DeFi tasks.

What you can do
Access web and crypto data tools for AI agents, grouped by the provider as audit, extraction, crypto and DeFi functions. Calls are billed individually through an x402 payment flow settled in USDC on Base. No tool list is published, so the exact operations must be confirmed with the provider before relying on it.
When to use it
Consider it when an assistant needs on-demand web or crypto/DeFi data and you are willing to pay per call in USDC on Base rather than use a subscription API.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, environment variables or headers are declared. Because calls are pay-per-call via x402/USDC-Base, a compatible paying client and a funded USDC wallet on Base are implied. Network access to the endpoint is required.
Before you install
Every call spends money in USDC on Base, so costs can accumulate and a funded wallet is exposed to the service. The tool list is not published, so what each call does and returns is unverified. The endpoint is an IP-address-based host with no stated operator identity, authentication or privacy terms; data sent to it goes to a third party.

Installation

In SourceWeft

  1. Open Agent Data Api 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/io.sslip.195.82.231.168%2Fagent-data-api/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": {
    "agent-data-api": {
      "type": "http",
      "url": "https://168.231.82.195.sslip.io/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.