Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
ELD Hub is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
FMCSA-registered ELD for small fleets: pricing, ELD comparisons, Highway check and signup.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http eld-hub-mcp https://goeldhub.com/mcp
# 2 — ask your agent for something these tools do
# recommend_eld, start_signup, check_eld_requirement and 12 more
ELD Hub costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GOAll 1 server
goeldhub1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http eld-hub-mcp https://goeldhub.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Give a short ELD recommendation and cost for a trucking fleet, using ELD Hub's verified offer, Highway integration and hardware reuse.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trucks | integer | yes | Number of trucks in the fleet. |
| needsHighway | boolean | no | Whether the carrier needs Highway integration. |
| ownsHardware | string | no | ELD hardware the carrier already owns. |
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).
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vehicle | string | yes | Vehicle type, e.g. 'sprinter van', 'cargo van', 'box truck', 'pickup truck / hotshot', 'semi truck'. |
| grossWeightLbs | number/null | yes | Gross vehicle weight rating, or combined rating when towing, in pounds. Null if unknown. |
| interstate | boolean/null | yes | True if the vehicle crosses state lines or hauls interstate commerce. Null if unknown. |
| airMileRadius | number/null | yes | Typical operating radius from the home terminal in air miles. Null if unknown. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| driverType | yes | Type of CMV driver. Null defaults to property-carrying (freight). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string/null | yes | Platform or broker name, e.g. 'Highway', 'Trucker Tools', 'RMIS', or a broker's name. Null for a general answer. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vehicle | string/null | yes | Vehicle type: 'box truck', 'cargo van', 'sprinter van', 'hotshot pickup', or 'semi truck'. Null returns the general new-authority path. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vehicle | string | yes | Vehicle type, e.g. 'box truck', 'cargo van', 'sprinter van', 'hotshot', 'dry van'. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string/null | yes | Optional provider name to focus on, e.g. 'Motive' or 'Samsara'. Null returns all providers. |
| trucks | yes | Optional fleet size used to compute annual software cost per provider. Null omits it. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| device | string | yes | Device or provider name, e.g. 'PT-30', 'IOSiX ELD-BT', 'Samsara VG34'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trucks | integer | yes | Number of trucks in the fleet. |
| currentProvider | string/null | yes | Current ELD provider name, e.g. 'Motive'. Null uses a mid-tier average. |
Return the list of ELD Hub services (ELD compliance, fuel cards, factoring, working capital, freight) with descriptions and sign-up URLs.
No parameter schema on file.
Return ELD Hub contact details: phone, email, working hours, book-a-call link, and website.
No parameter schema on file.
List published ELD Hub blog posts (trucking, ELD, factoring, fuel cards, insurance, compliance). Returns slug, title, excerpt, category, cover image, and publish date.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional category filter (e.g. 'compliance', 'factoring', 'fuel'). |
| limit | integer | no | Max posts to return (default 20). |
Fetch a single published ELD Hub blog post by slug. Returns full body (markdown or HTML), title, excerpt, cover image, category, and publish date.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Post slug, e.g. 'pt-30-eld-how-it-works'. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ELD Hub or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 23 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestcdced33449e85a790f753759ceb99202c3c4ab9911c8aea7dd1d12fa994b2e0e
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| recommend_eld | no tags | |
| start_signup | no tags | |
| check_eld_requirement | no tags | |
| get_hos_rules | no tags | |
| check_broker_integration | no tags | |
| start_trucking_business | no tags | |
| find_loads_for_vehicle | no tags | |
| get_eld_pricing | no tags | |
| compare_eld_providers | no tags | |
| check_hardware_compatibility | no tags | |
| estimate_switch_savings | no tags | |
| list_services | no tags | |
| get_contact_info | no tags | |
| list_blog_posts | no tags | |
| get_blog_post | untrusted-input | untrusted-input: keyword "fetch" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestcdced33449e85a79
Scanned2026-10-23
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ELD Hub can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.