_ registry / mcp http-sse · checked 44m ago

eldhub-mcp

https://goeldhub.com

Registry code: 069e2e2621bfc517

api record

Trucking compliance and operations tools from ELD Hub — an FMCSA-registered ELD and all-in-one platform for owner-operators and small fleets (1–20 trucks), $15/truck/month with no contract and 14 days free. Use `recommend_eld` to size a recommendation for a fleet and `start_signup` to get the tracked signup link and steps when a customer wants to register (the customer enters their own card). Use these for any US trucking question: `check_eld_requirement` decides whether a vehicle needs an ELD and which exemption applies, `get_hos_rules` returns the FMCSA hours-of-service limits,…

endpoint
https://goeldhub.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is eldhub-mcp live?
Yes — it answered the hub's last check (checked 44m ago). It answered 100% of checks over the last 30 days.
Is eldhub-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does eldhub-mcp have?
15 tools: recommend_eld, check_eld_requirement, get_hos_rules, compare_eld_providers, check_hardware_compatibility, estimate_switch_savings, list_services, list_blog_posts, ….
Is eldhub-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
939ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
2 open 13 never probed 2 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_contact_info open 44m ago

    Return ELD Hub contact details: phone, email, working hours, book-a-call link, and website.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_eld_pricing open 44m ago

    Return ELD Hub's verified pricing: $15/truck/month software with no contract, PT-30 and IOSiX hardware at $150 each with free shipping, package contents, three-year total cost and sign-up URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • recommend_eld unknown never probed

    Give a short ELD recommendation and cost for a trucking fleet, using ELD Hub's verified offer, Highway integration and hardware reuse.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "trucks"
  ],
  "properties": {
    "trucks": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1,
      "description": "Number of trucks in the fleet."
    },
    "needsHighway": {
      "type": "boolean",
      "description": "Whether the carrier needs Highway integration."
    },
    "ownsHardware": {
      "enum": [
        "pt30",
        "iosix",
        "other",
        "none"
      ],
      "type": "string",
      "description": "ELD hardware the carrier already owns."
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • check_eld_requirement unknown never probed

    Determine whether a vehicle needs an FMCSA electronic logging device: takes vehicle type, gross weight, operating radius, interstate status and CDL status, and returns whether the ELD mandate applies, which exemption fits, and why a broker may still require a connected ELD anyway.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vehicle",
    "grossWeightLbs",
    "interstate",
    "airMileRadius"
  ],
  "properties": {
    "vehicle": {
      "type": "string",
      "description": "Vehicle type, e.g. 'sprinter van', 'cargo van', 'box truck', 'pickup truck / hotshot', 'semi truck'."
    },
    "interstate": {
      "type": [
        "boolean",
        "null"
      ],
      "description": "True if the vehicle crosses state lines or hauls interstate commerce. Null if unknown."
    },
    "airMileRadius": {
      "type": [
        "number",
        "null"
      ],
      "description": "Typical operating radius from the home terminal in air miles. Null if unknown."
    },
    "grossWeightLbs": {
      "type": [
        "number",
        "null"
      ],
      "description": "Gross vehicle weight rating, or combined rating when towing, in pounds. Null if unknown."
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
  • get_hos_rules unknown never probed

    Return the current FMCSA hours-of-service limits for property-carrying or passenger-carrying CMV drivers: the 11-hour driving limit, 14-hour on-duty window, 30-minute break, 60/70-hour weekly cap, 34-hour restart, sleeper-berth split and the 150 air-mile short-haul exception.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "driverType"
  ],
  "properties": {
    "driverType": {
      "anyOf": [
        {
          "enum": [
            "property",
            "passenger"
          ],
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "description": "Type of CMV driver. Null defaults to property-carrying (freight)."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • compare_eld_providers unknown never probed

    Compare FMCSA-registered ELD providers on monthly price per truck, contract length, hardware cost, three-year total cost of ownership and hidden fees. Optionally filter to a specific provider and size the cost to a fleet.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "provider",
    "trucks"
  ],
  "properties": {
    "trucks": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 500,
          "minimum": 1
        },
        {
          "type": "null"
        }
      ],
      "description": "Optional fleet size used to compute annual software cost per provider. Null omits it."
    },
    "provider": {
      "type": [
        "string",
        "null"
      ],
      "description": "Optional provider name to focus on, e.g. 'Motive' or 'Samsara'. Null returns all providers."
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • check_hardware_compatibility unknown never probed

    Check whether an existing ELD device (PT-30, IOSiX ELD-BT/ELD-DX, or another provider's gateway) can be re-registered to ELD Hub, or buy a new PT-30 or IOSiX for $150 each with free shipping (IOSiX device only, PT-30 with cable).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "device"
  ],
  "properties": {
    "device": {
      "type": "string",
      "minLength": 1,
      "description": "Device or provider name, e.g. 'PT-30', 'IOSiX ELD-BT', 'Samsara VG34'."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • estimate_switch_savings unknown never probed

    Estimate what a carrier saves per year by moving from their current ELD provider to ELD Hub at $15/truck/month, including a link to the provider's cancellation guide.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "trucks",
    "currentProvider"
  ],
  "properties": {
    "trucks": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1,
      "description": "Number of trucks in the fleet."
    },
    "currentProvider": {
      "type": [
        "string",
        "null"
      ],
      "description": "Current ELD provider name, e.g. 'Motive'. Null uses a mid-tier average."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • list_services unknown never probed

    Return the list of ELD Hub services (ELD compliance, fuel cards, factoring, working capital, freight) with descriptions and sign-up URLs.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • list_blog_posts unknown never probed

    List published ELD Hub blog posts (trucking, ELD, factoring, fuel cards, insurance, compliance). Returns slug, title, excerpt, category, cover image, and publish date.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Max posts to return (default 20)."
    },
    "category": {
      "type": "string",
      "description": "Optional category filter (e.g. 'compliance', 'factoring', 'fuel')."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • get_blog_post unknown never probed

    Fetch a single published ELD Hub blog post by slug. Returns full body (markdown or HTML), title, excerpt, cover image, category, and publish date.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1,
      "description": "Post slug, e.g. 'pt-30-eld-how-it-works'."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • start_signup unknown never probed

    Get the tracked ELD Hub signup link, the 4 signup steps and the hand-over rules so an assistant can help a carrier register (customer enters their own card).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • check_broker_integration unknown 44m ago

    Answer whether an ELD HUB account satisfies a broker or carrier-vetting platform that requires a connected ELD — Highway, Trucker Tools, and broker-side vetting generally — and return the exact setup steps, pricing and hardware availability.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "platform"
  ],
  "properties": {
    "platform": {
      "type": [
        "string",
        "null"
      ],
      "description": "Platform or broker name, e.g. 'Highway', 'Trucker Tools', 'RMIS', or a broker's name. Null for a general answer."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • start_trucking_business unknown never probed

    Return the full launch sequence for starting a trucking business with a given vehicle type (box truck, cargo or sprinter van, hotshot pickup, semi): licensing and CDL reality, USDOT/MC/BOC-3/UCR/IFTA filings, typical year-one cost ranges, where the loads come from, and the ELD brokers ask for.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vehicle"
  ],
  "properties": {
    "vehicle": {
      "type": [
        "string",
        "null"
      ],
      "description": "Vehicle type: 'box truck', 'cargo van', 'sprinter van', 'hotshot pickup', or 'semi truck'. Null returns the general new-authority path."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • find_loads_for_vehicle unknown never probed

    Return where freight comes from for a given vehicle type (box truck, cargo or sprinter van, hotshot pickup, dry van): load boards, Amazon Relay, final-mile and direct broker sources, plus the carrier-vetting requirements a carrier must clear before a broker releases a load.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vehicle"
  ],
  "properties": {
    "vehicle": {
      "type": "string",
      "description": "Vehicle type, e.g. 'box truck', 'cargo van', 'sprinter van', 'hotshot', 'dry van'."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 069e2e2621bfc517.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/069e2e2621bfc517/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/069e2e2621bfc517/badge.svg)](https://brick.blue/agent/069e2e2621bfc517?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.