Skip to main content
Glama

Server Details

performance-review MCP — wraps StupidAPIs (keyless — no credential needed)

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-performance-review
GitHub Stars
0
Server Listing
mcp-performance-review
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 45 tools

Disambiguation2/5

Several clusters of tools have unclear boundaries: ask_pipeworx, ask_pipeworx_beta (admitted to be currently identical to ask_pipeworx), ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions are all 'entry points' that an agent must choose between, and the prediction-market family (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, resolution_audit, resolution_diff) overlaps heavily. Very long descriptions mitigate but the selection decision remains hard, especially beta vs stable and edges vs arbitrage vs bet_research.

Naming Consistency3/5

Everything is snake_case, which is a real consistency win, but the verb/noun ordering is mixed: verb_noun (resolve_entity, compare_entities, validate_claim, research_row) sits alongside noun_verb (performance_review_generate) and plain noun phrases (company_facts, entity_profile, bet_research, recent_changes, prediction_calibration). Namespace prefixes (polymarket_*, updown_*, archive_*) are applied inconsistently, so some tools read as family members and others as orphans.

Tool Count2/5

45 tools is far past the useful ceiling for any single server, and the count is inflated by near-duplicate router variants (ask_pipeworx, _beta, _grounded) and by six-plus overlapping prediction-market tools. The stated server purpose needs roughly one tool, so 45 is a severe mismatch on either reading.

Completeness2/5

Judged against the stated domain (performance reviews), the surface is almost entirely absent: no list, get, update, delete, or employee/manager records — just one generate tool, with 44 tools about SEC filings, Polymarket and web archives bolted on. Judged as a data-router platform the coverage is broader, but there is still no CRUD around stored objects (memories/subscriptions have forget/unsubscribe, but there is no update path anywhere).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Zero-dependency stdio bridge to Moltline Studio's fleet of 14 hosted MCP servers covering code review, time operations, data transforms, business ops, education, research, outreach and more. Free tier requires no registration; premium tools unlock with a license. Independently audited, MCPize Verified A.
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets MCP clients search a catalog of 391 web scraping endpoints, inspect their parameters, and call them to retrieve structured JSON from 300+ sites such as Amazon, LinkedIn, Google, and Zillow, plus check API usage and credits. Runs over stdio or Streamable HTTP, returning text, inline images, and embedded files.
      4
      438 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.