Is the Baneado98 Freight Pulse MCP server down?

• Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name). (verify)

{
  "name": "booking_strategy",
  "description": "When and how to RESERVE space so your box isn't rolled and your cargo isn't stranded on the dock. Give the lane + ship date + criticality, and it reads the demand PRESSURE (composing the seasonality calendar — CNY / Golden Week / transpacific peak — with the equipment-crunch signal) into a band (slack → acute), then returns: the optimal BOOKING WINDOW (lead days, plus a criticality buffer, and the date to book by), the SPOT vs CONTRACT rollover probability and roll-delay days, and the GUARANTEED",
  "inputSchema": {
    "type": "object",
    "required": [
      "origin_port",
      "dest_port"
    ],
    "properties": {
      "dest_port": {
        "type": "string",
        "description": "Destination port."
      },
      "ship_date": {
        "type": "string",
        "description": "Ship date (YYYY-MM-DD) — selects the seasonal/equipment pressure. Optional; default today."
      },
      "criticality": {
        "type": "string",
        "description": "'low' / 'normal' / 'high' / 'critical' — how badly a rollover delay hurts. Optional; default normal."
      },
      "origin_port": {
        "type": "string",
        "description": "Origin port (city name, UN/LOCODE, or 'City, Country')."
      },
      "container_type": {
        "type": "string",
        "description": "Container '20ft'/'40ft'/'40HC'. Optional; default '40ft'."
      },
      "annual_containers": {
        "type": "number",
        "description": "Annual committed volume on this lane (containers/yr) — triggers the named-account allocation call. Optional."
      },
      "base_freight_per_container_usd": {
        "type": "number",
        "description": "Base ocean freight per container (USD) to price the premium & delay cost. Optional — derived if omitted."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "check_lc_documents",
  "description": "Will your letter-of-credit documents GET PAID? Banks reject roughly 60-70% of first-presentation documentary-credit submissions over DOCUMENTARY DISCREPANCIES. Give the fields of the credit + the presented documents (commercial invoice, bill of lading, insurance, packing list) and it applies the UCP 600 rules a trade-finance checker uses, returning the DISCREPANCIES that would make an examining bank reject the presentation — each tied to its UCP article with a remedy: invoice amount over the cre",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "blClean": {
        "type": "boolean",
        "description": "Is the B/L clean (no defect clause)?"
      },
      "incoterm": {
        "type": "string",
        "description": "Credit incoterm (CIF/CIP trigger the insurance check)."
      },
      "expiryDate": {
        "type": "string",
        "description": "Credit expiry date (YYYY-MM-DD)."
      },
      "beneficiary": {
        "type": "string",
        "description": "Credit beneficiary (the seller)."
      },
      "creditAmount": {
        "type": "number",
        "description": "The credit (LC) amount."
      },
      "shipmentDate": {
        "type": "string",
        "description": "On-board / shipment date on the B/L (YYYY-MM-DD)."
      },
      "insuranceDate": {
        "type": "string",
        "description": "Insurance document date (YYYY-MM-DD)."
      },
      "insuredAmount": {
        "type": "number",
        "description": "Insured amount on the insurance document."
      },
      "invoiceAmount": {
        "type": "number",
        "description": "Commercial invoice amount."
      },
      "portOfLoading": {
        "type": "string",
        "description": "Credit's required port of loading."
      },
      "creditCurrency": {
        "type": "string",
        "description": "Credit currency (e.g. USD)."
      },
      "amountTolerance": {
        "type": "number",
        "description": "Amount tolerance fraction (e.g. 0.05 = ±5%). Default 0."
      },
      "blPortOfLoading": {
        "type": "string",
        "description": "Port of loading on the B/L."
      },
      "insuredCurrency": {
        "type": "string",
        "description": "Insurance currency."
      },
      "invoiceCurrency": {
        "type": "string",
        "description": "Invoice currency."
      },
      "portOfDischarge": {
        "type": "string",
        "description": "Credit's required port of discharge."
      },
      "presentationDate": {
        "type": "string",
        "description": "Date documents are presented to the bank (YYYY-MM-DD)."
      },
      "blPortOfDischarge": {
        "type": "string",
        "description": "Port of discharge on the B/L."
      },
      "insuranceRequired": {
        "type": "boolean",
        "description": "Does the credit require an insurance document?"
      },
      "invoiceBeneficiary": {
        "type": "string",
        "description": "Who issued the invoice."
      },
      "latestShipmentDate": {
        "type": "string",
        "description": "Latest shipment date (YYYY-MM-DD)."
      },
      "creditGoodsDescription": {
        "type": "string",
        "description": "Goods description as written in the credit."
      },
      "presentationPeriodDays": {
        "type": "number",
        "description": "Presentation period in days (UCP default 21)."
      },
      "invoiceGoodsDescription": {
        "type": "string",
        "description": "Goods description on the invoice."
      },
      "packingListGoodsDescription": {
        "type": "string",
        "description": "Goods description on the packing list."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "check_watches",
  "description": "Evaluate the lane watches you registered with create_watch against the LIVE modeled market and return the alerts that FIRED. For each watch it gathers the current cross-validated spot + direction, the modeled lane reliability, any active disruptions, and (when a watch needs it) the forecast/timing book call + expected move, then checks every threshold and reports which ones tripped — with the observed value, the reason and a severity. Pass a watch_id to check just one, or omit it to evaluate the",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "watch_id": {
        "type": "string",
        "description": "Evaluate only this watch id. Optional — omit to evaluate all your watches."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}