Skip to main content
Glama
nexusfeed-mcp

nexusfeed-mcp

by NexusFeed

nexusfeed-mcp

PyPI version Python 3.12+ License: MIT

Tasas de recargo por combustible de carga LTL en tiempo real y registros de cumplimiento de licencias de licor ABC estatales de EE. UU., servidos como JSON normalizado y verificable para agentes de IA a través del Protocolo de Contexto de Modelo (MCP).

Los datos se extraen de las páginas de tarifas de los transportistas y de los portales ABC estatales (renderizados con JS, CAPTCHAs, estado de sesión) que son estructuralmente inaccesibles para la navegación directa de LLM. Cada respuesta incluye un bloque _verifiability (marca de tiempo de extracción, puntuación de confianza y URL de origen) para que los agentes puedan evaluar la calidad de los datos antes de actuar.

Herramientas

Herramienta

Descripción

ltl_get_fuel_surcharge

% de recargo por combustible semanal para ODFL, Saia, Estes, ABF, R+L, TForce, XPO, SEFL, Averitt — precio del diésel del DOE y hasta 5 años de historial

ltl_list_carriers

Metadatos de cobertura del transportista (códigos SCAC, calendario de actualización, método de extracción)

abc_search_licenses

Buscar en bases de datos de licencias de CA, TX, NY, FL por nombre comercial, propietario o dirección

abc_lookup_license

Estado de la licencia en un momento dado mediante el número de licencia emitido por el estado

abc_list_states

Cobertura estatal, latencia y requisitos de CAPTCHA

Related MCP server: us-legal-mcp

Prompts de flujo de trabajo

Prompt

Descripción

freight_audit_workflow

Auditoría de facturas LTL de varios pasos frente a las tarifas publicadas de los transportistas

license_compliance_check

Verificación de cumplimiento antes de pedidos de distribuidores, vinculación de seguros o incorporación de comerciantes

Obtener acceso a la API

Suscríbase a través de RapidAPI para recibir su X-API-Key. Planes Freemium disponibles (10 solicitudes/día gratis).

Producto

Listado en RapidAPI

LTL Fuel Surcharge

rapidapi.com/ladourv/api/ltl-fuel-surcharge-api

ABC License Compliance

rapidapi.com/ladourv/api/abc-license-compliance-api

Instalación

pip install nexusfeed-mcp
# or with uv/uvx (no install needed):
uvx nexusfeed-mcp

Configuración

export MCP_API_BASE_URL=https://api.nexusfeed.dev
export MCP_API_KEY=sk_live_your_key_here

Ejecución (stdio)

# LTL tools only — 3 tools, 1 prompt
nexusfeed-ltl

# ABC tools only — 3 tools, 1 prompt
nexusfeed-abc

# All tools — 5 tools, 2 prompts
nexusfeed-mcp

Configuración de Claude Desktop

Solo recargo por combustible LTL:

{
  "mcpServers": {
    "nexusfeed-ltl": {
      "command": "uvx",
      "args": ["--from", "nexusfeed-mcp", "nexusfeed-ltl"],
      "env": {
        "MCP_API_BASE_URL": "https://api.nexusfeed.dev",
        "MCP_API_KEY": "sk_live_your_key_here"
      }
    }
  }
}

Solo cumplimiento de licencias ABC:

{
  "mcpServers": {
    "nexusfeed-abc": {
      "command": "uvx",
      "args": ["--from", "nexusfeed-mcp", "nexusfeed-abc"],
      "env": {
        "MCP_API_BASE_URL": "https://api.nexusfeed.dev",
        "MCP_API_KEY": "sk_live_your_key_here"
      }
    }
  }
}

Todas las herramientas:

{
  "mcpServers": {
    "nexusfeed-mcp": {
      "command": "uvx",
      "args": ["nexusfeed-mcp"],
      "env": {
        "MCP_API_BASE_URL": "https://api.nexusfeed.dev",
        "MCP_API_KEY": "sk_live_your_key_here"
      }
    }
  }
}

Configuración de Cline (VS Code)

Abra la configuración de Cline → Servidores MCP → Agregar servidor manualmente:

Solo LTL:

{
  "nexusfeed-ltl": {
    "command": "uvx",
    "args": ["--from", "nexusfeed-mcp", "nexusfeed-ltl"],
    "env": {
      "MCP_API_BASE_URL": "https://api.nexusfeed.dev",
      "MCP_API_KEY": "sk_live_your_key_here"
    }
  }
}

Solo ABC:

{
  "nexusfeed-abc": {
    "command": "uvx",
    "args": ["--from", "nexusfeed-mcp", "nexusfeed-abc"],
    "env": {
      "MCP_API_BASE_URL": "https://api.nexusfeed.dev",
      "MCP_API_KEY": "sk_live_your_key_here"
    }
  }
}

HTTP transmitible (Smithery / clientes remotos)

Servidor

URL

Herramientas LTL

https://api.nexusfeed.dev/mcp-ltl/

Herramientas ABC

https://api.nexusfeed.dev/mcp-abc/

Envíe su encabezado X-API-Key en cada solicitud. Metadatos del servidor (sin autenticación):

https://api.nexusfeed.dev/.well-known/mcp/server-card-ltl.json
https://api.nexusfeed.dev/.well-known/mcp/server-card-abc.json

Verificabilidad

Cada respuesta de herramienta incluye:

"_verifiability": {
  "source_timestamp": "2026-04-05T09:00:00Z",
  "extraction_confidence": 0.97,
  "raw_data_evidence_url": "https://odfl.com/...",
  "extraction_method": "api_mirror",
  "data_freshness_ttl_seconds": 604800
}
  • extraction_confidence >= 0.90 es necesario antes de utilizar datos en decisiones críticas de cumplimiento

  • source_timestamp dentro de data_freshness_ttl_seconds significa que los datos están actualizados desde la caché

  • raw_data_evidence_url es la fuente canónica: los agentes pueden verificar de forma independiente

Ejemplo de uso

Auditar una factura de carga LTL:

Use the freight_audit_workflow prompt with carrier="ODFL", invoice_date="2026-04-01",
invoiced_fuel_surcharge_pct="23.5" to check whether the billed rate matches the
published tariff.

Verificar una licencia de licor antes de una transacción de distribuidor:

Use abc_search_licenses with state="CA" and trade_name="Total Wine" to check
current license status, then abc_lookup_license for the full record with suspension history.

Solución de problemas

Síntoma

Solución

401 en cada llamada

MCP_API_KEY no está configurado o no es válido

"Could not reach API server"

MCP_API_BASE_URL no configurado: debería ser https://api.nexusfeed.dev

Los endpoints de TX devuelven 503

TX TABC requiere 2Captcha configurado en el lado del servidor; use CA, NY o FL en su lugar

extraction_confidence < 0.90

Calidad de datos degradada: verifique de forma independiente a través de raw_data_evidence_url

Licencia

Código de cliente (este repositorio): MIT. Consulte LICENSE.

Servicio backend de NexusFeed (https://api.nexusfeed.dev): comercial. La licencia MIT anterior cubre solo el contenedor del cliente de Python en este repositorio. No otorga derechos sobre el servicio de datos, que requiere una clave API de pago y se rige por Términos de Servicio separados. Póngase en contacto con ops@nexusfeed.dev para obtener SLA empresarial y licencias.

Available Tools

6 tools
abc_list_statesA

Returns metadata for all US states currently supported by the ABC License API, including the agency name, data freshness SLA, extraction method, and whether CAPTCHA is present. Use this first when building a multi-state compliance workflow to understand coverage.

Inputs: no named parameters. Returns: result

abc_lookup_licenseA

Looks up a specific liquor license by its state-issued license number and returns the full current record including status, expiration, address, conditions, and suspension history. Faster and more precise than abc_search_licenses when you already have the license number. Use this for point-in-time verification (e.g., 'Is license CA-20-621547 currently ACTIVE?'). The _verifiability block contains the exact source URL — agents can independently verify the result by fetching that URL.

Inputs: license_number (required), state (required). Returns: result

abc_search_licensesA

Searches a US state ABC (Alcoholic Beverage Control) board database for liquor licenses matching a business name, owner name, or address. Returns license type, current status (ACTIVE / SUSPENDED / EXPIRED / REVOKED), expiration date, and any suspension history. Use this before approving a distributor order, binding an insurance policy, or onboarding a merchant to verify they hold a valid liquor license. Supports CA, TX, NY, and FL (TX requires TWOCAPTCHA_API_KEY configured server-side; NY uses NY Open Data API — active licenses only; FL searches the DBPR licensing portal across all board types). Always check the _verifiability block: extraction_confidence >= 0.90 and source_timestamp within data_freshness_ttl_seconds are required for compliance decisions. Note: city, county, zip, and license_status filters are accepted but not yet applied server-side — results may need post-filtering.

Inputs: state (required), trade_name, owner_name, address, +5 more. Returns: result

ltl_get_accessorialsB

[COMING SOON] Returns the current accessorial fee schedule for LTL carriers — liftgate, residential delivery, re-delivery, inside delivery, limited access, notification, appointment fees, and more. This tool is not yet available and will return an unavailability message. Use ltl_get_fuel_surcharge for current carrier data.

Inputs: carriers, fee_types. Returns: result

ltl_get_fuel_surchargeA

Returns current LTL carrier fuel surcharge percentages and the DOE diesel price that triggered each rate. Data is extracted weekly from carrier tariff pages and cached — response time <500ms. Use this instead of browsing carrier websites: those pages are JS-rendered, PDFs, or require session state that makes raw browsing unreliable. Covers ODFL and SAIA (Sprint 1-2); Estes, ABF, R+L, TForce arriving in Sprint 4. Each response includes a _verifiability block with extraction timestamp and confidence score — check this before using the data in a freight cost calculation or invoice audit.

Inputs: carriers, weeks, include_doe_price. Returns: result

ltl_list_carriersA

Returns metadata for all LTL carriers supported by this API, including their SCAC code, which data products are available, fuel surcharge update day, and extraction method. Use this to discover coverage before building a carrier comparison workflow.

Inputs: no named parameters. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct domain and action: ABC tools handle license verification (list states, search by business, lookup by license number), while LTL tools cover carrier information (list carriers, fuel surcharge, accessorials). Clear descriptions prevent confusion.

    Naming Consistency5/5

    All tool names follow a consistent 'domain_verb_noun' pattern in snake_case (abc_list_states, ltl_get_fuel_surcharge). The naming is predictable and uniform across both domains.

    Tool Count4/5

    Six tools is a reasonable count for the two domains. However, one tool (ltl_get_accessorials) is non-functional (returns 'coming soon'), slightly reducing its value. Still, the count is appropriate for the scope.

    Completeness3/5

    The ABC domain is well-covered with list, search, and lookup operations. The LTL domain has a gap: accessorial fees are not yet available. Additionally, abc_search_licenses notes that some filters are not applied server-side, limiting its completeness.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers