Skip to main content
Glama
nexusfeed-mcp

nexusfeed-mcp

by NexusFeed

nexusfeed-mcp

PyPI version Python 3.12+ License: MIT

Echtzeit-Treibstoffzuschlagsraten für LTL-Fracht und Compliance-Datensätze für ABC-Alkohol-Lizenzen in US-Bundesstaaten — bereitgestellt als normalisiertes, verifizierbares JSON für KI-Agenten über das Model Context Protocol.

Die Daten werden von Tarifseiten der Speditionen und ABC-Portalen der Bundesstaaten extrahiert (JS-gerendert, CAPTCHAs, Sitzungsstatus), die für das reine LLM-Browsing strukturell unzugänglich sind. Jede Antwort enthält einen _verifiability-Block — Extraktionszeitstempel, Konfidenzwert und Quell-URL —, damit Agenten die Datenqualität beurteilen können, bevor sie handeln.

Tools

Tool

Beschreibung

ltl_get_fuel_surcharge

Wöchentlicher Treibstoffzuschlag in % für ODFL, Saia, Estes, ABF, R+L, TForce, XPO, SEFL, Averitt — DOE-Dieselpreis und bis zu 5 Jahre Historie

ltl_list_carriers

Metadaten zur Speditionsabdeckung (SCAC-Codes, Aktualisierungsplan, Extraktionsmethode)

abc_search_licenses

Durchsuchen der Lizenzdatenbanken von CA, TX, NY, FL nach Handelsname, Eigentümer oder Adresse

abc_lookup_license

Lizenzstatus zu einem bestimmten Zeitpunkt anhand der vom Bundesstaat ausgestellten Lizenznummer

abc_list_states

Abdeckung der Bundesstaaten, Latenz und CAPTCHA-Anforderungen

Related MCP server: us-legal-mcp

Workflow-Prompts

Prompt

Beschreibung

freight_audit_workflow

Mehrstufige LTL-Rechnungsprüfung anhand veröffentlichter Speditionstarife

license_compliance_check

Compliance-Überprüfung vor Händlerbestellungen, Versicherungsabschlüssen oder dem Onboarding von Kaufleuten

API-Zugang erhalten

Abonnieren Sie über RapidAPI, um Ihren X-API-Key zu erhalten. Freemium-Pläne verfügbar (10 Anfragen/Tag kostenlos).

Produkt

RapidAPI-Eintrag

LTL Treibstoffzuschlag

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

ABC Lizenz-Compliance

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

Installation

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

Konfiguration

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

Ausführen (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

Claude Desktop-Konfiguration

Nur LTL-Treibstoffzuschlag:

{
  "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"
      }
    }
  }
}

Nur ABC-Lizenz-Compliance:

{
  "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"
      }
    }
  }
}

Alle Tools:

{
  "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"
      }
    }
  }
}

Cline (VS Code) Konfiguration

Öffnen Sie die Cline-Einstellungen → MCP Servers → Add Server manually:

Nur 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"
    }
  }
}

Nur 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"
    }
  }
}

Streamable HTTP (Smithery / Remote-Clients)

Server

URL

LTL-Tools

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

ABC-Tools

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

Übergeben Sie Ihren X-API-Key-Header bei jeder Anfrage. Server-Metadaten (keine Authentifizierung):

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

Verifizierbarkeit

Jede Tool-Antwort enthält:

"_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 ist erforderlich, bevor Daten für Compliance-kritische Entscheidungen verwendet werden

  • source_timestamp innerhalb von data_freshness_ttl_seconds bedeutet, dass die Daten frisch aus dem Cache stammen

  • raw_data_evidence_url ist die kanonische Quelle — Agenten können diese unabhängig verifizieren

Anwendungsbeispiel

Prüfung einer LTL-Frachtrechnung:

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.

Überprüfung einer Alkohollizenz vor einer Händlertransaktion:

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.

Fehlerbehebung

Symptom

Lösung

401 bei jedem Aufruf

MCP_API_KEY ist nicht gesetzt oder ungültig

"Could not reach API server"

MCP_API_BASE_URL nicht gesetzt — sollte https://api.nexusfeed.dev sein

TX-Endpunkte geben 503 zurück

TX TABC erfordert serverseitig konfiguriertes 2Captcha; verwenden Sie stattdessen CA, NY oder FL

extraction_confidence < 0.90

Datenqualität verschlechtert — unabhängig über raw_data_evidence_url verifizieren

Lizenz

Client-Code (dieses Repository): MIT. Siehe LICENSE.

NexusFeed-Backend-Service (https://api.nexusfeed.dev): kommerziell. Die oben genannte MIT-Lizenz deckt nur den Python-Client-Wrapper in diesem Repository ab. Sie gewährt keine Rechte am Datendienst, der einen kostenpflichtigen API-Schlüssel erfordert und separaten Nutzungsbedingungen unterliegt. Kontaktieren Sie ops@nexusfeed.dev für Enterprise-SLAs und Lizenzierung.

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