Argentina Data

io.github.abenassiPublished by GitHub account abenassiv0.5.1Updated Oct 24, 2026

Real-time Argentine open data: dollar rates, BCRA, INDEC, AFIP, INFOLEG, SEPA prices. 24+ tools.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Remote MCP server giving assistants real-time Argentine open data: dollar rates, BCRA, INDEC, AFIP, INFOLEG and SEPA prices.

What you can do
  • Retrieve Argentine dollar exchange rates and central bank (BCRA) data
  • Look up national statistics from INDEC and tax information from AFIP
  • Query legislation from INFOLEG and SEPA food price data
  • Access a set of 24+ tools covering these public data sources
When to use it
Useful when an assistant needs current Argentine economic, statistical, tax, legal or price data rather than general web search, for example for research, reporting or analysis on Argentina.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. OAuth authentication is required, so the user must sign in with the provider's OAuth flow. Network access to the hosted endpoint.
Before you install
Access requires OAuth sign-in, so the assistant acts under the user's authenticated session. Data comes from third-party public sources and may be delayed or revised; verify figures before relying on them. No tool list is published, so confirm the available tools after connecting.

Installation

In SourceWeft

  1. Open Argentina Data in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.abenassi%2Fargentina-data/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "argentina-data": {
      "type": "http",
      "url": "https://argentinadata.mymcps.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.5.1LatestSep 16, 2026

Score

67% 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 listed15 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.

  • 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.