ELD Hub
REMOTE · GOELDHUB.COM
FMCSA-registered ELD for small fleets: pricing, ELD comparisons, Highway check and signup.
Available components
Last scanned (11 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1621 tokens (~108/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://goeldhub.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=goeldhub.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 14ff781786b99e2513f78ef228ca34f2 |
| SANs: goeldhub.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of goeldhub.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| goeldhub.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://goeldhub.com/mcp | Verified | 200 | |
| http (plaintext) | http://goeldhub.com/mcp | HTTPS enforced | 301 | https://goeldhub.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_broker_integration Check broker / vetting platform ELD integration ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string|null | yes | Platform or broker name, e.g. 'Highway', 'Trucker Tools', 'RMIS', or a broker's name. Null for a general answer. |
No output schema declared.
No examples provided.
check_eld_requirement Check whether an ELD is required ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| airMileRadius | number|null | yes | Typical operating radius from the home terminal in air miles. Null if unknown. |
| 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. |
| vehicle | string | yes | Vehicle type, e.g. 'sprinter van', 'cargo van', 'box truck', 'pickup truck / hotshot', 'semi truck'. |
No output schema declared.
No examples provided.
check_hardware_compatibility Check ELD hardware compatibility ~119
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).
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | Device or provider name, e.g. 'PT-30', 'IOSiX ELD-BT', 'Samsara VG34'. |
No output schema declared.
No examples provided.
compare_eld_providers Compare ELD providers ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
estimate_switch_savings Estimate ELD switch savings ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currentProvider | string|null | yes | Current ELD provider name, e.g. 'Motive'. Null uses a mid-tier average. |
| trucks | integer | yes | Number of trucks in the fleet. |
No output schema declared.
No examples provided.
find_loads_for_vehicle Where to find loads for a vehicle type ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vehicle | string | yes | Vehicle type, e.g. 'box truck', 'cargo van', 'sprinter van', 'hotshot', 'dry van'. |
No output schema declared.
No examples provided.
get_blog_post Get blog post ~65
Fetch a single published ELD Hub blog post by slug. Returns full body (markdown or HTML), title, excerpt, cover image, category, and publish date.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Post slug, e.g. 'pt-30-eld-how-it-works'. |
No output schema declared.
No examples provided.
get_contact_info Get contact info ~31
Return ELD Hub contact details: phone, email, working hours, book-a-call link, and website.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_eld_pricing Get ELD Hub pricing ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_hos_rules Get FMCSA hours-of-service rules ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| driverType | – | yes | Type of CMV driver. Null defaults to property-carrying (freight). |
No output schema declared.
No examples provided.
list_blog_posts List blog posts ~87
List published ELD Hub blog posts (trucking, ELD, factoring, fuel cards, insurance, compliance). Returns slug, title, excerpt, category, cover image, and publish date.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (e.g. 'compliance', 'factoring', 'fuel'). |
| limit | integer | – | Max posts to return (default 20). |
No output schema declared.
No examples provided.
list_services List ELD Hub services ~38
Return the list of ELD Hub services (ELD compliance, fuel cards, factoring, working capital, freight) with descriptions and sign-up URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend_eld Recommend an ELD for a fleet ~79
Give a short ELD recommendation and cost for a trucking fleet, using ELD Hub's verified offer, Highway integration and hardware reuse.
| Name | Type | Req | Description |
|---|---|---|---|
| needsHighway | boolean | – | Whether the carrier needs Highway integration. |
| ownsHardware | string | – | ELD hardware the carrier already owns. |
| trucks | integer | yes | Number of trucks in the fleet. |
No output schema declared.
No examples provided.
start_signup Start an ELD Hub signup for a customer ~42
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_trucking_business How to start a trucking business ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vehicle | string|null | yes | Vehicle type: 'box truck', 'cargo van', 'sprinter van', 'hotshot pickup', or 'semi truck'. Null returns the general new-authority path. |
No output schema declared.
No examples provided.
How do I install the ELD Hub MCP server?
ELD Hub is a hosted endpoint at https://goeldhub.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · goeldhub.com
claude mcp add --transport http com-goeldhub-eldhub 'https://goeldhub.com/mcp'
What is the ELD Hub MCP server?
ELD Hub is an MCP server listed in the public MCP registry as com.goeldhub/eldhub. FMCSA-registered ELD for small fleets: pricing, ELD comparisons, Highway check and signup. This page covers its hosted endpoint (https://goeldhub.com/mcp).
Is the ELD Hub MCP server safe to use?
ELD Hub scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ELD Hub MCP server expose?
ELD Hub exposes 15 tools: recommend_eld, start_signup, check_eld_requirement, get_hos_rules, check_broker_integration, and 10 more. Their descriptions and schemas cost roughly 1,317 tokens of context every time the server is loaded.
Does the ELD Hub MCP server require authentication?
No. We connected to ELD Hub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ELD Hub MCP server still maintained?
ELD Hub is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ELD Hub MCP server?
VerifyMCP ran 13 checks on ELD Hub, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.