Is the Wingmanprotocol Agent Gateway MCP server down?

mcp-registry/com.wingmanprotocol.agent/gateway · v1.7.0

Also listed as glama/riproductions/wingmanprotocol-agent-gateway

As of 2026-10-21 02:55 UTC, the Wingmanprotocol Agent Gateway MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 7 minutes.

Durable self for AI agents: one-call resume, memory, real browser, free chat + hire real humans.

claude mcp add --transport http wingmanprotocol-agent-gateway-mcp-server https://agent.wingmanprotocol.com/mcp

{
  "mcpServers": {
    "wingmanprotocol-agent-gateway-mcp-server": {
      "type": "http",
      "url": "https://agent.wingmanprotocol.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (80/100)

What to fix (5)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 27 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.wingmanprotocol.agent%2Fgateway/fixes

{
  "name": "store_memory",
  "description": "[stores] Persist a value across your instances: PUT /memory/{ns}/{key}. Required: namespace + key + value. Shortcut: pass text alone and we default namespace='notes' and auto-key the entry. Optionally set ttl (seconds, min 60, max 30 days) for auto-eviction.",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "key": {
        "type": "string",
        "description": "entry name; auto-generated when using text shortcut"
      },
      "ttl": {
        "type": "integer",
        "description": "seconds until auto-eviction (60–2_592_000, omit=permanent)"
      },
      "text": {
        "type": "string",
        "description": "shortcut: store this string as value under notes/<auto-key>"
      },
      "value": {
        "description": "any JSON value",
        "type": "string"
      },
      "handle": {
        "type": "string"
      },
      "secret": {
        "type": "string"
      },
      "namespace": {
        "type": "string",
        "description": "logical grouping (e.g. 'projects'); default 'notes' when using text shortcut"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

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/com.wingmanprotocol.agent/gateway"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.wingmanprotocol.agent/gateway"}) over MCP.

Passed

• 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.61% uptime over 30 days.

Largest tool definitions

• human_task_post ~359 tokens
• human_profile_set ~324 tokens
• browse_open ~314 tokens
• register_agent ~304 tokens
• memory_retain ~292 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%2Fcom.wingmanprotocol.agent%2Fgateway.svg)](https://glimind.com/server/mcp-registry%2Fcom.wingmanprotocol.agent%2Fgateway?ref=badge)

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

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.wingmanprotocol.agent%2Fgateway.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.wingmanprotocol.agent%2Fgateway?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:21119df2b39f21ab…, first seen 2026-10-20, included at leaf 35338 of 36,718. Version history · verify what your client received.

Tools (61)

• archive_message
• browse
• browse_back
• browse_click
• browse_close
• browse_discover
• browse_evaluate
• browse_extract
• browse_fill
• browse_links
• browse_navigate
• browse_open
• browse_read
• browse_screenshot
• browse_select
• browse_snapshot
• browse_solve_challenge
• browse_type
• browse_wait_for
• cancel_watch
• capabilities
• check_errand
• check_inbox
• confirm_delivery
• create_watch
• discover_tools
• forget_memories
• get_tool_schema
• human_browse
• human_profile_set
• human_task_list
• human_task_post
• identity
• list_memory
• list_watches
• mark_message
• memory_recall
• memory_reflect
• memory_retain
• memory_stats
• read_memory_changes
• read_message
• recall_memories
• register_agent
• request_handoff
• research
• resolve_focus
• resume
• search
• search_memory
• search_memory_facts
• send_message
• set_focus
• share_memory
• store_artifact
• store_memory
• submit_errand
• summarize_memory
• web_discover
• web_read
• web_search

Compare: most reliable communication servers · most reliable web servers · most reliable browser servers · most reliable other servers · most reliable knowledge servers

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

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

FAQ

Is the Wingmanprotocol Agent Gateway MCP server down right now?

As of 2026-10-21 02:55 UTC, the Wingmanprotocol Agent Gateway MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Wingmanprotocol Agent Gateway MCP server provide?

Wingmanprotocol Agent Gateway MCP server advertises 61 tools, including archive_message, browse, browse_back, browse_click, browse_close.

How do I install Wingmanprotocol Agent Gateway MCP server?

Point your MCP client at this streamable-http endpoint: https://agent.wingmanprotocol.com/mcp

Is the Wingmanprotocol Agent Gateway MCP server safe to connect to an AI agent?

Glimind scanned all 61 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 Wingmanprotocol Agent Gateway 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.