Skip to main content
Glama

Server Details

take-the-meeting 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-take-the-meeting
GitHub Stars
0
Server Listing
mcp-take-the-meeting
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 43 tools

Disambiguation2/5

Several clusters have genuinely unclear boundaries: ask_pipeworx, ask_pipeworx_beta (which the description admits 'currently matches ask_pipeworx exactly'), ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions are six overlapping entry points into the same catalog. The Polymarket family (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research, polymarket_kalshi_spread) also requires reading long prose to know which to call. Descriptions work hard to differentiate, but an agent choosing blind will misselect.

Naming Consistency3/5

Snake_case is used throughout, which helps, but the grammatical convention is mixed: noun_noun (company_facts, entity_profile, prediction_calibration), verb_noun (resolve_entity, compare_entities, validate_claim, scan_dependency), and bare verbs (remember, recall, forget, subscribe). Variant suffixes (_beta, _grounded) and near-synonym stems (ai_visibility_check vs scan_competitor_ai_presence) break predictability.

Tool Count1/5

43 tools is heavy on its own, and the mismatch with the stated server purpose is extreme: exactly one tool (take_the_meeting_evaluate) concerns meetings, while the other 42 are a general-purpose data/research/prediction-market gateway. An agent connecting for meeting evaluation must wade through a 7,136-tool router and eleven prediction-market tools to find the one relevant call.

Completeness2/5

For the server's apparent domain (deciding whether to attend a meeting) the surface is nearly a dead end — evaluate exists, but there is no calendar lookup, attendee/agenda fetch, scheduling, rescheduling, or follow-up tool. The broader gateway surface is wide but leaves real gaps (subscriptions can be created and listed but only cancelled, no update; memory has no search/across-key listing beyond recall).

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
      Not graded
      quality
      A
      maintenance
      Enables AI clients such as Claude, Cursor, VS Code, and Windsurf to list and manage workspaces, projects, tasks, AI agents, and automations through a hosted OAuth-secured endpoint or a local stdio package. Also generates MCP tools from any OpenAPI spec.
      2,530 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      AI-powered meeting intelligence MCP server. Researches attendees from Google Calendar or Outlook, generates executive briefing cards, enriches with HubSpot CRM context, and records outcomes to persistent local meeting memory.
      13
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients such as Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language, using a hosted OAuth-authenticated endpoint or a local stdio package. It also ships an OpenAPI codegen tool for generating MCP tools from any OpenAPI spec.
      2,530 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.