Skip to main content
Glama
804,330 tools. Updated 2026-11-19 09:23

"MCP servers to enhance agent-based medical project performance" matching MCP tools:

  • Return plans, pricing, checkout links, and partner-pilot interest details. Use this when an agent or product team evaluates Olympus as B2B sports-intelligence infrastructure, asks how to integrate, or needs plan and pricing details. The agent product is MCP Pro. Website Premium plans in this payload are a different product (human board) and are not a substitute for Pro. Every ``checkout_url`` is a hosted Stripe Payment Link: if the operator has authorized you to complete hosted checkout, open the Pro URL and finish it; otherwise show them that URL. This tool does not charge a card itself. Performance numbers are intentionally omitted here; call ``get_performance_summary`` (or see ``subscribe_page``) for current tier-segmented track record. If YOU are the assistant driving the purchase, pass ``agent_ref`` with a short, stable identifier for this session (for example ``claude_<conversation_id>`` or ``cursor_<thread>``). It is stamped onto every returned ``checkout_url`` via the first-party checkout hop, so a resulting sale can be attributed back to the agent that produced it. The value is reduced to ``[A-Za-z0-9_-]`` (max 64 chars); anything else is dropped, and an empty/invalid value falls back to the normal surface ref.
    ConnectorNo auth
  • Project cognitive performance across the next 7 to 30 days from a single night of sleep the user describes to you. Returns one curve, peak, dip and score per day, plus the best and worst projected days. This repeats one self-reported baseline forward with decaying confidence, so treat it as the shape of a typical day rather than a prediction for each individual day. A behavioural forecast that learns weekday against weekend patterns needs connected sleep history in the WhenPeak app. Choose this tool for a span of days. Use whenpeak_quick_predict for one specific day, and call it once rather than looping it per day. Public and keyless: no API key is required. Read-only, with no side effects. Nothing is stored. Args: wake_time: this morning's wake time, "HH:MM" sleep_time: last night's sleep time, "HH:MM" sleep_quality: "good" | "fair" | "poor" days: horizon, 7-30 (default 7)
    ConnectorNo auth
  • Checks source you already generated against the secureFlows integration rules. Needs no secureFlows token; safe at scaffolding time. Pass every auth/session-related file in one call — some checks are evaluated across the whole set. Two kinds of findings: • scope "file" — a forbidden construct is present (localStorage token, legacy /app/login, fetch-based logout, client-side JWT decode, empty catch, restore non-auth errors clearing session UI, Continue CTA gated on null session, ...), reported at an exact file:line. • scope "project" — REQUIRED handling is missing everywhere you passed in: detecting 401/410 but never clearing the token, never handling 403, or handling 403 without the BILLING_GRACE_LOCK carve-out. These are the defects that actually dominate real generated apps, and no "forbidden pattern" check can see them, because the bug is an absence. Heuristic text analysis, not a parser or a type checker. It can miss things it has no rule for, and a project check can be satisfied by the right keyword in the wrong place. It is a fast first pass — not a substitute for the Agent implementation checklist in SKILL.md, and specifically not for the checks that need a running app (auth-guard mount races, the fresh-reload check). Fix every "error" before calling an integration done; treat "needs_review" as a lead.
    ConnectorNo auth
  • Checks source you already generated against the secureFlows integration rules. Needs no secureFlows token; safe at scaffolding time. Pass every auth/session-related file in one call — some checks are evaluated across the whole set. Two kinds of findings: • scope "file" — a forbidden construct is present (localStorage token, legacy /app/login, fetch-based logout, client-side JWT decode, empty catch, restore non-auth errors clearing session UI, Continue CTA gated on null session, ...), reported at an exact file:line. • scope "project" — REQUIRED handling is missing everywhere you passed in: detecting 401/410 but never clearing the token, never handling 403, or handling 403 without the BILLING_GRACE_LOCK carve-out. These are the defects that actually dominate real generated apps, and no "forbidden pattern" check can see them, because the bug is an absence. Heuristic text analysis, not a parser or a type checker. It can miss things it has no rule for, and a project check can be satisfied by the right keyword in the wrong place. It is a fast first pass — not a substitute for the Agent implementation checklist in SKILL.md, and specifically not for the checks that need a running app (auth-guard mount races, the fresh-reload check). Fix every "error" before calling an integration done; treat "needs_review" as a lead.
    ConnectorNo auth
  • List all API specifications in the active project. Set scope to 'org' to list the published APIs across every project in the organization instead — each entry carries the projectId and specId to pass to set_context. Use this to browse specs or find a spec id; for one spec by id use get_spec. Requires project context for scope 'project'.
    ConnectorAPI key
  • Enumerate every ACC and BIM 360 project the authenticated APS app can see by walking all accessible hubs and their project lists. When to use: The agent needs to discover project IDs before calling any other tool (e.g. the user says 'show me my projects' or 'find issues in the Tower project' and no project_id is known yet). Also useful to confirm hub membership for a project. When NOT to use: Do not call this repeatedly in a loop — cache the result; if the user already supplied a project_id starting with 'b.', skip discovery. APS scopes: data:read account:read. No write scope needed. Rate limits: APS default ~50 req/min per app per endpoint; BIM 360 hubs endpoints are pageable (limit 200). This tool fans out 1 hubs call + N project calls (one per hub) so call it sparingly on tenants with many hubs. Errors: 401 (APS token expired — refresh and retry once); 403 (app not provisioned in the BIM 360/ACC account — ask user to have an account admin add the APS client_id); 404 (rare, indicates hub deleted mid-call); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: None. Read-only and idempotent.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

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

  • EnhanceOAuth

    Shared canvas for AI-assisted product design, visual feedback and interactive prototypes. Browser sign-in (OAuth) required. Website: https://enhancelabs.ai. Docs: https://app.enhancelabs.ai/docs.

  • Return a filtered slice of the resolved-pick ledger by tier, league, and result. Premium-tier picks are returned with line/odds/edge details masked (matchup + outcome + units only) — sufficient to demonstrate performance, insufficient to reverse-engineer the premium-only signal generator. Args: league: Optional league filter. tier: ``free`` for fully-public picks, ``premium`` for masked subscriber picks. result: WIN, LOSS, or PUSH. limit: Maximum rows (capped at 200). cursor: Zero-based result offset. Prefer get_track_record for new clients. verbose: When True, return all ledger fields (writeup, key_factors, CLV beat-close, engine version, etc.). Default False returns the essentials only — ~70% smaller payload, kinder to agent token budgets when surveying many rows.
    ConnectorNo auth
  • Return the persisted markers + AI analysis (Summary, KeyFindings, Recommendations, DetailedExplanation) for a specific medical-test the authenticated patient owns. Use after mediora__get_patient_history surfaces a test id the user wants to discuss. Bearer token must be a Mediora patient-scope JWT. Proxies https://api.mediora.ai/api/medical-tests/{id} with the user's token forwarded as Authorization: Bearer.
    ConnectorNo auth
  • Archive a project (reversible shelve) — frees a project slot in-tool. Stops any in-flight machine, then flips the project to `archived`: it drops out of the per-tier project cap (freeing a slot for a new project) and the loop stops dispatching it, but the project + its history are kept and can be restored from the dashboard project page. Stopping a machine DESTROYS the running process state — restoring the project later cannot bring that execution back, so this is destructive despite being reversible. A replay on an already-archived project changes no row, but is not idempotent end to end. This is preferable to `delete_project` unless the project must be gone. Owner-scoped (an MCP key is owner-only); a project not in the workspace 404s.
    Connector
    Destructive
    No auth
  • Search 51 book-based agent skills and 14 guided journeys by keyword or phrase. Each skill is matched against its own trigger text, so plain task language works ("my UI looks amateur", "pricing", "dark mode"). Returns compact hits, each quoting the line that matched. Use recommend_skills instead when you have a task rather than a keyword.
    ConnectorNo auth
  • AI cleanup of a recording: `speech` = noise + room removal (strength subtle/medium/strong), `music` = keep only the voice from a mixed track, `bg_music` = voice + a little of the original bed. Free. Produces a NEW audio_file_id — use it as the voice source in cast_build_project (cuts planned on the original still apply: same timeline). Enhance the ORIGINAL upload, not an already-enhanced file. On the free plan an API call returns a 60-second head preview (enough to A/B it) — the full-length render is one free click in the editor, or a paid-plan API call. The response says which you got.
    ConnectorOAuth
  • YOUR Hyperliquid account's performance and account facts (api:read), for wallet=main (your own wallet, default) or wallet=agent (the agent deposit wallet); the address is resolved from your token. view=portfolio (default): account value and PnL history over day / week / month / allTime, combined and perps-only (perpDay … perpAllTime) — the call for "how is my portfolio doing". view=summary: a normalized account summary across perps, HIP-3, USD spot and other spot assets. view=fees: your fee tier, maker/taker rates and recent daily volume. view=account_mode: standard | unified | portfolio_margin, with mode_source and stale. view=ledger: deposits, withdrawals and transfers (non-funding ledger updates) between start_time and end_time (epoch ms; start_time defaults to 30 days ago). Each answer names the wallet and address it read. Open positions and balances: get_positions / get_account_balances. The response carries app_url, the portfolio dashboard.
    ConnectorAPI key
  • List recent activity (task creates / updates / status changes / comments / dependency edits) for one project since a given timestamp. Returns up to 100 ActivityLog rows newest-first with actor + entity + action so an agent that just reconnected can catch up on what changed while it was offline. Time window capped at 30 days; for older history use list_audit_log instead. Each item includes entityTitle (the changed entity's current title, so you know WHICH task, project, change request, proposal, issue, page or idea changed without a per-row lookup; null when that entity has since been deleted or moved out of this project) and changedFields (the field names that changed, when recorded). Page and idea rows the caller cannot open are left out, details included, rather than returned with a null title, so a response can hold fewer than limit items and still report hasMore.
    ConnectorOAuth
  • Ask the AI to propose a new schedule for a project that fits all tasks before a target deadline while respecting dependencies. Returns an array of {taskId, startDate, dueDate} proposals (YYYY-MM-DD strings), any warnings, and feasibility status. Use mode="preview" (default) to inspect the proposal first; use mode="apply" to capture a baseline and commit the dates immediately (requires project Owner or Manager role). Cap: 100 tasks per project. Use when the user asks "can we finish by [date]?" or "reschedule this project to meet the deadline".
    Connector
    Destructive
    OAuth
  • Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Consumes a plan from plan_overlay_pack, spending its quoted credits and ATTACHING those scenes to the existing design-approved project (it never creates a new project -- that happened at create_design_sheet time). Calling this again with the same planId after it already succeeded is safe -- it returns the same project rather than attaching the scenes a second time or charging twice. Returns immediately, before any scene has rendered -- call get_pack_status afterward to advance and check progress.
    ConnectorNo auth
  • Open your own builder desk: a Hive room for one outside project, so a developer building on NightWatch gets a dedicated thread with the house. No badge needed. One open desk per agent (a second call returns it with existing=true), at most 3 new desks per 24 hours. Returns {room_id, url, tag, next_reply_by}; the house's first [RULE] post in the room names its reply time. Then post there with hive_post, one issue per post tagged with the returned tag. Requires an agent key (X-NW-User-Key); call agent_connect first if you don't have one. Requires: project, summary.
    ConnectorNo auth
  • Open a chat. kind 'direct': the chat with one colleague ('with') — there is one per pair, so an existing one is found rather than made ('created' false). kind 'group': a group with a title and its members, you its administrator. kind 'agent': a chat of your own with one of the company's agents ('agent', e.g. 'product'), found if you have one. Only the company's own people. A project's chat is never made — it is there for every project; list_chats with projectKey finds it.
    ConnectorNo auth
  • Vollständiger Google-Lighthouse-Audit (Performance, Accessibility, Best Practices, SEO). strategy: 'desktop' oder 'mobile'. Rückgabe: scores{performance, accessibility, best_practices, seo} (0–100), lcp_ms, cls, inp_ms. LANGSAM: rendert die Seite komplett, dauert typisch 10–35 s. Sparsam und nur EINZELN einsetzen (nicht in Schleifen / nicht parallel für viele URLs), und dem Nutzer die Wartezeit ankündigen. Für Core Web Vitals (LCP/CLS/INP) und Performance-Score ist dies das einzige Tool; nur für Title/Meta/H1/Wortzahl/ OnPage-Score stattdessen dfs_onpage_instant (~1 s) nutzen. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).
    ConnectorOAuth
  • List paginated task summaries assigned to the current agent. Use this to inspect your own open work before starting or continuing a substantive request. Prefer this over get_tasks when you only need your queue. My means the current Atomic agent, not every task assigned to the signed-in human. Without an agent execution context this returns an empty page; use get_tasks for the project queue.
    ConnectorOAuth
  • Delete an entire project permanently — every node, dependency edge and agent writeback goes with it, and the map URL stops resolving. Irreversible. Requires confirm_name to exactly match the project's current name (from list_projects), so a stale or wrong project_id can't wipe the wrong project; a mismatch returns the real name so you can retry with it. To stop tracking work without destroying it, edit the nodes instead.
    Connector
    Destructive
    OAuth
  • Disconnect a sign-in based integration (for example Google Ads, Meta Ads or HubSpot) from a deployed agent. Call it without confirm first: it shows what is connected and what will be removed, and changes nothing. After the user agrees, call again with confirm: true. The saved sign-in, the selected accounts and the connection's settings are cleared (your own app keys are kept), the provider is asked to revoke the access where it supports that, scheduled tasks that need the integration stop running, and a running agent restarts. It cannot be undone; reconnect with connect_agent_oauth. For plain credentials such as Telegram, clear fields with set_agent_credentials instead.
    Connector
    Destructive
    API key