
OVRSEA Shipments
com.ovrsea.mcpPublished by mcp.ovrsea.comOfficial publisherv0.0.1Updated Oct 24, 2026
Query your OVRSEA freight: shipments, quotations, documents, tasks, and reporting analytics.
Overview
Lets an assistant query OVRSEA freight data such as shipments, quotations, documents, tasks, and reporting analytics.
- What you can do
- This remote MCP server connects an assistant to an OVRSEA freight account. According to its registry description, it covers shipments, quotations, documents, tasks, and reporting analytics, so an assistant can look up freight records and related operational items through conversation. The manifest does not list individual tools, so the exact operations available are not documented here.
- When to use it
- Worth adding when you work with OVRSEA for freight forwarding and want an assistant to pull shipment, quotation, document, or task information without switching to the web interface. Less useful if you do not use OVRSEA as your freight platform.
- Requirements
- A remote streamable HTTP endpoint at mcp.ovrsea.com, reachable over the network. Authentication is OAuth and is required; no environment variables or headers are declared. You need an OVRSEA account with access to the relevant freight data.
Installation
In SourceWeft
- Open OVRSEA Shipments in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.ovrsea.mcp%2Fcustomer-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"ovrsea-shipments": {
"type": "http",
"url": "https://mcp.ovrsea.com/"
}
}
}Tools
0Version history
1- v0.0.1LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.