A
licenseNot graded
qualityD
maintenanceOcean container shipping intelligence for AI agents — D\&D tariffs, freight rates, vessel schedules, port congestion, inland haulage across 6 major carriers. 24 MCP tools.
MIT
freight-pulse
Server Details
Ocean & multimodal freight intelligence: rates, landed cost, transit, customs, risk, ship decisions
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Baneado98/freight-pulse
- GitHub Stars
- 0
- Server Listing
- freight-pulse
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
46 tool updates
- Added
appointment_plan - Added
booking_strategy - Added
build_tender - Added
carbon_footprint - Added
carrier_recommendation - Added
check_lc_documents - Added
check_watches - Added
cold_chain - Added
compare_modes - Added
contingency_plan - Added
create_watch - Added
customs_optimization - Added
customs_valuation - Added
decarbonization_roadmap - Added
dnd_strategy - Added
door_to_door - Added
equipment_availability - Added
evaluate_bids - Added
export_compliance - Added
fx_exposure - Added
get_all_in_rate - Added
get_landed_cost - Changed
get_lane_trend2 fields changed- added
Input schema / properties / forecast_weeksAdded value: +{ + "description": "How many weeks ahead to forecast the rate (1–26, default 6). Prediction intervals widen with the horizon.", + "type": "number" +} - added
Input schema / properties / ship_dateAdded value: +{ + "description": "The intended shipment date (ISO 'YYYY-MM-DD' or any parseable date). The seasonality calendar (CNY, peak season, GRIs, blank sailings) is evaluated for THIS date. Optional; defaults to today.", + "type": "string" +}
- Added
get_port_intel - Added
get_scorecard - Added
incoterm_responsibility - Added
insurance_recommendation - Added
inventory_optimization - Added
lane_risk_index - Added
load_plan - Added
market_report - Added
optimize_network - Added
pallet_plan - Added
payment_terms - Added
procurement_strategy - Added
qualify_fta_origin - Added
rate_benchmark - Added
record_performance - Added
required_documents - Added
reverse_logistics - Added
select_provider - Added
ship_decision - Added
simulate_scenario - Added
sourcing_analysis - Added
special_cargo - Added
total_cost_ownership
2 tool updates
- First observed
get_lane_trend - First observed
get_spot_rate
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
WMS & logistics intelligence: live freight & shipping rates, port data, inventory, fleet, KPIs
Ocean shipping intelligence: D&D, freight rates, vessel schedules, port data. 24 tools, 6 carriers.
Shipping intelligence — D&D charges, local charges, inland haulage. x402 USDC payments.
Real-time supply chain risk intelligence — 24 tools, proprietary indices, predictive signals
Related MCP Servers
- FlicenseAqualityCmaintenanceReal-time supply chain risk intelligence with 25 tools: Global Disruption Index, Manufacturing Index, commodity prices, port congestion, border delays, chokepoints, air cargo, trade policy, energy, rail, freight, economic indicators, predictive signals, and AI intelligence briefs.6341-
- AlicenseNot gradedqualityCmaintenanceTrack ocean containers across 200+ shipping lines by container, bill of lading, or booking number — live milestones, vessel positions, ETAs, and demurrage & detention free time.17MIT
- AlicenseNot gradedqualityCmaintenanceEnables comparing ocean carrier sailing schedules, transit times, and on-time reliability via AI clients like Claude, Cursor, and Windsurf.9MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.1/5.0
Disambiguation4/5
Most tools have distinct purposes, e.g., get_spot_rate vs get_all_in_rate vs get_landed_cost clearly differ. Some overlap exists (booking_strategy vs procurement_strategy, equipment_availability vs load_plan), but detailed descriptions help differentiate. Overall, an agent can usually select the correct tool.
Naming Consistency3/5
Tool names are lowercase with underscores, but patterns vary: some are verb_noun (build_tender, check_lc_documents), others are noun phrases (booking_strategy, carbon_footprint). While readable, there is no strict convention, making it less predictable.
Tool Count2/5
With 47 tools, the set is very large. While each tool addresses a specific aspect of freight management, many could be combined (e.g., multiple watch-related tools). This volume risks overwhelming users and agents, suggesting a need for consolidation.
Completeness5/5
The tool set covers an impressively broad range: spot rates, all-in costs, port intel, equipment, mode comparison, carrier recommendation, procurement, D&D, customs, trade finance, inventory, sourcing, etc. There are no obvious gaps for the stated domain of freight decision support.