Is the Seaweb MCP server down?

mcp-registry/tech.seaweb/seaweb · v1.28.1

As of 2026-10-25 20:39 UTC, the Seaweb MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 47 minutes.

Read-only web search for AI agents; does not book, reserve or take payment. Stores your preferences.

Point your MCP client at this streamable-http endpoint: https://api.seaweb.tech/mcp

Agent-readiness: C (72/100)

What to fix (4)

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/tech.seaweb/seaweb"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/tech.seaweb/seaweb"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.66% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• register_standing_query ~381 tokens
• search_destination_sentiment ~350 tokens
• search_restaurants ~336 tokens
• search_salons ~335 tokens
• search ~318 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Ftech.seaweb%2Fseaweb.svg)](https://glimind.com/server/mcp-registry%2Ftech.seaweb%2Fseaweb?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Ftech.seaweb%2Fseaweb?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Ftech.seaweb%2Fseaweb.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Ftech.seaweb%2Fseaweb.svg
   :target: https://glimind.com/server/mcp-registry%2Ftech.seaweb%2Fseaweb?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:99c52c0ac4a8d4da…, first seen 2026-10-17, included at leaf 373 of 76,589. Version history · verify what your client received.

Working alternatives

• agents_status ai.rokha/rokha
• agentseo_job_status dev.agentseo.www/agentseo-mcp
• agentid_verify pro.aemb/agent-embassy
• agentid_verify io.github.tacticalnoot/agent-embassy

Tools (43)

• agent_job_status
• build_dataset
• cancel_agent_job
• compare_search
• delete_disruption_webhook
• delete_standing_query
• extract_url
• filter_restaurants
• filter_salons
• get_camera_visibility
• get_details
• get_disruption_event
• get_disruptions
• get_entity
• get_hours
• get_menu
• get_restaurant
• get_salon
• get_services
• get_site_skill
• get_spot_conditions
• list_disruption_events
• list_disruption_webhooks
• list_sources
• list_standing_queries
• list_verticals
• log_outcome
• recall
• register_disruption_webhook
• register_standing_query
• remember
• research
• research_status
• resolve_geo
• search
• search_destination_sentiment
• search_restaurants
• search_salons
• search_web
• submit_feedback
• teamwork_preview
• travel_health
• vote_comparison

Compare: most reliable devops servers · most reliable data servers · most reliable search servers · most reliable communication servers · most reliable other servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Seaweb MCP server down right now?

As of 2026-10-25 20:39 UTC, the Seaweb MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 47 minutes.

How many tools does Seaweb MCP server provide?

Seaweb MCP server advertises 43 tools, including agent_job_status, build_dataset, cancel_agent_job, compare_search, delete_disruption_webhook.

How do I install Seaweb MCP server?

Point your MCP client at this streamable-http endpoint: https://api.seaweb.tech/mcp

Is the Seaweb MCP server safe to connect to an AI agent?

Glimind scanned all 43 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Seaweb MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.