Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Direcciones AR

REMOTE · DIRECCIONES-AR-API-103907796853.US-EAST1.RUN.APP

Normaliza y geocodifica direcciones de Argentina con el callejero oficial (georef).

+5 this week 80 Trust /100

Last scanned (19 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security92
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1570 tokens (~196/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 72% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

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

  • 19 Nov 26 +1
    • Tool “buscar_calle” rewrote its description, which is the text the model reads security
    • Tool “buscar_division” rewrote its description, which is the text the model reads security
    • Tool “buscar_localidad” rewrote its description, which is the text the model reads security
    • Tool “ejecutar” rewrote its description, which is the text the model reads security
    • Tool “normalizar_direccion” rewrote its description, which is the text the model reads security
    • Tool “ubicacion” rewrote its description, which is the text the model reads security
  • 17 Nov 26 +2
    • Authorization: partial → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “comprar_creditos” rewrote its description, which is the text the model reads security
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • New tool “consultar_saldo” functional
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +14
    • Authorization: unverified → pass ▲ security
    • First check of Authorization: partial security
  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 61

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://direcciones-ar-api-103907796853.us-east1.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WE2,O=Google Trust Services,C=US 3 Nov 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 f668c9036838957b095b05d18ab2228d
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WE2,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff32d6b409d15d5965b05873a7c72e0
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of direcciones-ar-api-103907796853.us-east1.run.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
run.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Esta tool requiere autorizacion.", resource_metadata="https://direcciones-ar-api-103907796853.us-east1.run.app/.well-known/oauth-protected-resource/mcp", scope="mcp"

Bearer error="invalid_token", error_description="Esta tool requiere autorizacion.", resource_metadata="https://direcciones-ar-api-103907796853.us-east1.run.app/.well-known/oauth-protected-resource/mcp", scope="mcp"

Protected resource metadata

Document https://direcciones-ar-api-103907796853.us-east1.run.app/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://direcciones-ar-api-103907796853.us-east1.run.app/mcp
Authorisation server https://direcciones-ar-api-103907796853.us-east1.run.app

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://direcciones-ar-api-103907796853.us-east1.run.app/mcp Verified 200
http (plaintext) http://direcciones-ar-api-103907796853.us-east1.run.app/mcp HTTPS enforced 302 https://direcciones-ar-api-103907796853.us-east1.run.app/mcp
MCP tools · 8 exposed · ~1,420 tokens

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 →

Tool Tokens
buscar_calle ~168

Busca calles por nombre aproximado y devuelve nombre oficial, categoría (CALLE, AV, PJE, RUTA...), rango de alturas y a qué localidad/departamento/provincia pertenece cada tramo. Sirve para validar que una calle existe y que una altura está dentro del rango antes de normalizar, o para autocompletar. Para geocodificar una dirección con altura usá normalizar_direccion. Costo: 1 crédito(s).

NameTypeReqDescription
categoriastring–Filtrar por tipo: CALLE, AV, PJE, RUTA, DIAG, etc.
departamentostring––
localidadstring–Localidad censal
maxinteger––
nombrestringyes–
provinciastring––

No output schema declared.

No examples provided.

buscar_division ~171

Busca divisiones administrativas oficiales por nombre aproximado: provincias (24), departamentos/partidos/comunas o municipios. Devuelve id INDEC, nombre oficial, provincia a la que pertenece y centroide. Usala para resolver 'Bs As' → 'Buenos Aires' (id 06) vs 'CABA' (id 02), listar los partidos de una provincia, o conseguir el id que piden otros sistemas. Para saber en qué división cae un punto (lat/lon) usá ubicacion. Costo: gratis.

NameTypeReqDescription
maxinteger––
nombrestring–Nombre aproximado; omitilo para listar (ej. todas las provincias)
provinciastring–Restringir a una provincia (para departamentos y municipios)
tipostringyes–

No output schema declared.

No examples provided.

buscar_localidad ~149

Busca localidades (ciudades, pueblos, barrios censales) por nombre aproximado y devuelve provincia, departamento/partido, municipio, categoría y coordenadas del centroide, con ids oficiales INDEC. Útil para desambiguar ('¿qué Rosario?'), completar formularios o resolver la ubicación de un cliente. Filtrá por provincia cuando la conozcas. Para una dirección completa con calle y altura usá normalizar_direccion. Costo: gratis.

NameTypeReqDescription
departamentostring–Departamento o partido
maxinteger––
nombrestringyesNombre (tolera tildes y errores leves)
provinciastring–Nombre o id de provincia

No output schema declared.

No examples provided.

comprar_creditos ~107

Para cuando el usuario pide comprar o recargar créditos: devuelve los packs disponibles y una checkout_url (Polar, tarjeta) para la key actual, que la persona abre para pagar; al pagar, los créditos se acreditan solos. No cobra ni mueve dinero por sí misma. Sin costo.

NameTypeReqDescription
creditsinteger–Cantidad deseada; se elige el pack más chico que la cubre
product_idstring–Elegir un pack puntual (de la lista)

No output schema declared.

No examples provided.

consultar_saldo ~63

Devuelve los créditos que le quedan a la API key actual, sus últimos movimientos (con la API de la suite donde ocurrieron) y una URL para recargar. El saldo es el mismo en AR Tools, Índices AR y Direcciones AR. Sin costo.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ejecutar ~359

Corre JavaScript en un sandbox con un objeto `api` ya autenticado: una función async por tool, mismos parámetros y mismo resultado que llamarla directo. Ideal para lotes (validar 50 CBUs, armar 20 cronogramas) o para encadenar llamadas sin volver al modelo. El código puede usar await, console.log y return; el valor retornado vuelve en `resultado`. Costo: 1 crédito por ejecución + la suma de las llamadas internas. Máximo 100 llamadas y 15 s. Sin acceso a red, archivos ni módulos. Funciones disponibles: api.normalizarDireccion({"direccion":"Av. Corrientes 1234","provincia":"CABA"}) → 2 crédito(s): Normalizar y geocodificar una dirección argentina api.ubicacion({"lat":-34.6037,"lon":-58.3816}) → 0 crédito(s): Geocodificación inversa: lat/lon → provincia, departamento y municipio api.buscarLocalidad({"nombre":"Rosario","provincia":"Santa Fe"}) → 0 crédito(s): Buscar localidades argentinas api.buscarCalle({"nombre":"Santa Fe","provincia":"CABA","categoria":"AV"}) → 1 crédito(s): Buscar calles en el callejero oficial api.buscarDivision({"tipo":"provincia","nombre":"cordoba"}) → 0 crédito(s): Buscar provincias, departamentos o municipios Costo: 1 crédito(s).

NameTypeReqDescription
codigostringyesJavaScript. Ej: const r = await api.validarCuit({cuit:'20-12345678-6'}); return r.valido;
timeout_msinteger–Tiempo máximo total en milisegundos

No output schema declared.

No examples provided.

normalizar_direccion ~267

Interpreta una dirección escrita a mano ('Av. Corrientes 1234, CABA', 'corrientes y callao', 'San Martín 450 piso 3 Rosario'), la normaliza según el callejero oficial (INDEC/IGN vía georef) y devuelve candidatos con calle, altura, localidad, departamento, provincia y coordenadas lat/lon. Pasá provincia o localidad si las conocés: reduce ambigüedad. Si `cantidad` es 0 la dirección no existe en el callejero oficial; si hay varios candidatos, elegí por localidad o pedí precisión al usuario. Solo direcciones de Argentina; no confirma que el número de puerta exista físicamente. Costo: 2 crédito(s).

NameTypeReqDescription
departamentostring–Partido, departamento o comuna ('Tigre', 'Comuna 1')
direccionstringyesDirección en texto libre: 'calle altura' o 'calle y calle', opcionalmente con piso/depto
localidadstring–Localidad censal ('Rosario', 'Mar del Plata')
maxinteger–Cantidad máxima de candidatos
provinciastring–Nombre o id de provincia ('Buenos Aires', 'CABA', 'Córdoba', '02')

No output schema declared.

No examples provided.

ubicacion ~136

Dado un punto (latitud, longitud) devuelve en qué provincia, departamento/partido y municipio de Argentina cae, con ids oficiales INDEC. Si el punto está fuera del país, `en_argentina` es false y los campos vienen null. No devuelve calle ni altura. Para pasar una dirección escrita a coordenadas usá normalizar_direccion. Costo: gratis.

NameTypeReqDescription
latnumberyesLatitud en grados decimales (Argentina: aprox. -22 a -55)
lonnumberyesLongitud en grados decimales (Argentina: aprox. -53 a -74)

No output schema declared.

No examples provided.

Install

How do I install the Direcciones AR MCP server?

Direcciones AR is a hosted endpoint at https://direcciones-ar-api-103907796853.us-east1.run.app/mcp, 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 · direcciones-ar-api-103907796853.us-east1.run.app

# add to Claude Code
claude mcp add --transport http torlettijoaquin-direcciones-ar 'https://direcciones-ar-api-103907796853.us-east1.run.app/mcp'
Common questions

What is the Direcciones AR MCP server?

Direcciones AR is an MCP server listed in the public MCP registry as io.github.TorlettiJoaquin/direcciones-ar. Normaliza y geocodifica direcciones de Argentina con el callejero oficial (georef). This page covers its hosted endpoint (https://direcciones-ar-api-103907796853.us-east1.run.app/mcp).

Is the Direcciones AR MCP server safe to use?

Direcciones AR scores 80 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 Direcciones AR MCP server expose?

Direcciones AR exposes 8 tools: normalizar_direccion, ubicacion, buscar_localidad, buscar_calle, buscar_division, and 3 more. Their descriptions and schemas cost roughly 1,420 tokens of context every time the server is loaded.

Does the Direcciones AR MCP server require authentication?

Yes. Direcciones AR asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Direcciones AR MCP server still maintained?

Direcciones AR is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Direcciones AR MCP server?

VerifyMCP ran 13 checks on Direcciones AR, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.