Is the Pipeworx Io Powo MCP server down?

mcp-registry/io.github.pipeworx-io/powo · v0.1.0

Verdict. Pipeworx Io Powo MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 101 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (94/100) across 43 tools, costing an agent about 16,361 tokens to load. Checked every few minutes; no tool is ever called.

Data as of .

30-day measurements and how they compare with other MCP servers
MetricValueBetter than
Uptime, 30 days100%42% of MCP servers
Median handshake latency101 ms85% of MCP servers
p95 handshake latency1094 ms—
Checks in 30 days11—
Outages, 90 days0—
Median recovery——
Agent-readiness score94/100 (A)78% of MCP servers
Tools43—
Tool-list size for an agent~16,361 tokens12% of MCP servers
Days observed27—
healthy
Last checked 2026-10-24 18:32 UTC · handshake 99ms

As of 2026-10-24 18:32 UTC, the Pipeworx Io Powo MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
11
outages (90d)
0
tools
43

POWO (Plants of the World Online, by the Royal Botanic Gardens, Kew) MCP.

Install Pipeworx Io Powo MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http pipeworx-io-powo-mcp-server https://gateway.pipeworx.io/powo/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "pipeworx-io-powo-mcp-server": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/powo/mcp"
    }
  }
}

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

Agent-readiness: A (94/100)

A (94/100): 0 error(s), 1 warning(s) across 43 tool(s); ~16,361 tokens of tool definitions.
Scores higher than 79% of 15,760 MCP servers Glimind has audited.
Its tool list costs an agent ~16,361 tokens per session — more than 85% of servers.
88 → 94 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost75
Client compatibility100
Protocol100
Reliability100
Stability52

What to fix (2)

43 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

In the last 30 days: 0 tool(s) removed and 12 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

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/io.github.pipeworx-io/powo"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.pipeworx-io/powo"}) over MCP.

Passed

Largest tool definitions

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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fpowo.svg)](https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fpowo?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fpowo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fpowo.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fpowo.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fpowo?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:69ecb0645b6ee18f…, first seen 2026-10-17, included at leaf 16235 of 75,338. Version history · verify what your client received.

Tools (43)

Compare: most reliable ml servers · most reliable web servers · most reliable retrieval servers · most reliable other servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Pipeworx Io Powo MCP server down right now?

As of 2026-10-24 18:32 UTC, the Pipeworx Io Powo MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Pipeworx Io Powo MCP server provide?

Pipeworx Io Powo MCP server advertises 43 tools, including ai_visibility_check, archive_compare, archive_evidence, ask_pipeworx, ask_pipeworx_beta.

How do I install Pipeworx Io Powo MCP server?

Point your MCP client at this streamable-http endpoint: https://gateway.pipeworx.io/powo/mcp

Is the Pipeworx Io Powo 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 Pipeworx Io Powo 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.

Feedback
Help us improve