B+

gateway.pipeworx.io

Item: gateway.pipeworx.io
Rating: 89
Author: wmcp.sh

https://gateway.pipeworx.io/zenquotes/mcp

89/100 · MCP Trust Grade · checked 7h ago · MCP 2025-03-26

⚠ Rug-pull watch: this server's tool surface has changed 22× since baseline — last 7h ago. Continuously watched by wmcp.sh for drift & rug-pulls.

What it offers — 23 tools · Developer Tools

ask_pipeworx

PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, U

discover_tools

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, re

resolve_entity

Resolve a user-spoken name to the canonical/official identifiers other tools require as input. Use FIRST when you have a name but need an ID. SUPPORTE

compare_entities

Compare 2-5 companies (or drugs) side by side in one call. Use for "compare X and Y", "X vs Y", "which is bigger", or rank-by-metric questions. type="

entity_profile

Get everything about a US public company in one call. Use when a user asks "tell me about X", "research Acme", "brief me on Tesla", or you'd otherwise

recent_changes

What's new with a company in the last N days/months? Use for "what's happening with X", "updates on Y", "news on Apple this month", or change-monitori

validate_claim

Fact-check, verify, validate, or confirm/refute a natural-language factual claim or statement against authoritative sources. Use when an agent needs t

scan_dependency

Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bund

bet_research

Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-bitcoin-hit-150k-by-june-30-2026"), a po

polymarket_arbitrage

Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. TWO MODES: (1) `event` — pass a single Polymarket event

polymarket_edges

Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents

polymarket_kalshi_spread

Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because

pipeworx_trending

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d)

generate_llms_txt

Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extra

ai_visibility_check

Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers

scan_competitor_ai_presence

Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score,

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed i

remember

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a

+5 more tools

Spec conformance20%100

✓ initialize → protocolVersion 2025-03-26
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 23 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

23 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%70

single-probe latency 2656ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%75

87% of tools have typed inputSchema
3/23 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%90

HTTPS ✓
RFC 9728 oauth-protected-resource metadata ✓
advertises protocol 2025-03-26

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade gateway.pipeworx.io on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — gateway.pipeworx.io grade B+

Share on X Open card image

https://wmcp.sh/mcp/grade/gateway.pipeworx.io

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B+](https://wmcp.sh/mcp/grade/gateway.pipeworx.io/badge.svg)](https://wmcp.sh/mcp/grade/gateway.pipeworx.io)

HTML

<a href="https://wmcp.sh/mcp/grade/gateway.pipeworx.io"><img src="https://wmcp.sh/mcp/grade/gateway.pipeworx.io/badge.svg" alt="MCP Trust Grade B+ · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.