mcpbeat Sign in

OVRSEA Shipments MCP Server

by ovrsea-mcp Your server? Claim it
answering

OVRSEA Shipments is answering right now. Last checked 6 min ago.

Query your OVRSEA freight: shipments, quotations, documents, tasks, and reporting analytics.

Uptime history 91 days of history · worst day 97%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
444 ms
Response time
average over 24h
OAuth sign-in
Access
sse

Nothing serious here today

Today is the operative word: we check OVRSEA Shipments every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add customer-mcp --transport sse https://mcp.ovrsea.com
Settings → Connectors → Add custom connector, then paste this address
https://mcp.ovrsea.com
~/.codex/config.toml
[mcp_servers.customer-mcp]
url = "https://mcp.ovrsea.com"
.cursor/mcp.json
{
  "mcpServers": {
    "customer-mcp": {
      "url": "https://mcp.ovrsea.com"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "customer-mcp": {
      "type": "sse",
      "url": "https://mcp.ovrsea.com"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.ovrsea.com sse sign-in 347 ms 6 min ago

Alternatives to OVRSEA Shipments

same job, measured the same way
Maven
by metricmaven

Ask questions of your marketing data and build live reports.

answering
MCP Analytics
by mcpanalytics

A statistical analyst in your AI chat: bring data and a question, get a citable, re-runnable report.

27 tools answering
Toffu
by toffu

AI marketing platform your agent runs end to end: ads, analytics, content, and reports.

answering
QueryAtlas
by queryatlas

Query selected Google and Bing analytics, search, and advertising reports through MCP.

answering
Nexly Analytics
by nexly

Read-only access to your Nexly web analytics: traffic, pages, acquisition, events, and reports.

answering
Advanced Zebrunner MCP Server
by maksimsarychau

Advanced analytics, reporting, and safe mutations for Zebrunner. 64 tools, 14 resources, 17 prompts.

106 installs/wk local only
DocsBot
by uglyrobot

Manage DocsBot agents, knowledge sources, conversations, reporting, and teams with OAuth.

answering
LLM Pulse
by llm-pulse

AI visibility analytics for brand mentions, citations, sentiment, and GEO reports

answering

OVRSEA Shipments — questions

Answers built from our own checks of this server.

Why is there no tool list for OVRSEA Shipments?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is OVRSEA Shipments working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 444 ms. The bar chart above shows every period we have measured.
How do I connect OVRSEA Shipments?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to OVRSEA Shipments?
No API key is involved. OVRSEA Shipments answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is OVRSEA Shipments?
It answers our handshake in 444 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.