VeraData

io.github.teodorofodocrispin-cmykPublished by GitHub account teodorofodocrispin-cmykv1.0.0Updated Oct 24, 2026

Verified LATAM data for AI agents: sanctions, entity, rates, KYB. Pay via x402.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Gives an assistant verified Latin American data on sanctions, entities, rates, and KYB checks through a remote endpoint.

What you can do
VeraData is a remote MCP server that supplies verified Latin American data to AI agents. According to its registry description, it covers sanctions screening, entity information, rates, and KYB (know-your-business) checks. No tool list is published, so the exact operations available are not documented here.
When to use it
Consider it when an assistant needs Latin American compliance or business data, such as sanctions screening, entity lookups, rate information, or KYB checks during research or onboarding workflows.
Requirements
A remote streamable HTTP endpoint at the provider's address; no packages, environment variables, or headers are declared. The description mentions paying via x402, so a payment-capable client or wallet may be needed.
Before you install
The description states payment is made via x402, so using it may spend money; confirm pricing and limits before connecting. No authentication is declared, and no tool list is published, so verify what data is sent and returned.

Installation

In SourceWeft

  1. Open VeraData 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.github.teodorofodocrispin-cmyk%2Fveradata/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": {
    "veradata": {
      "type": "http",
      "url": "https://api.veradata.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.