Skip to main content
Glama
741,331 tools. Updated 2026-11-04 03:22

"A server with Bybit integration capable of interacting with P2P" matching MCP tools:

  • Submit an uploaded PDF for faxing. Step 1 (before this tool): upload the PDF over plain HTTP multipart, using any HTTP client you have — shell, JavaScript fetch with FormData, Python, etc.: curl -F "file=@document.pdf" https://www.sendthisfax.com/api/upload fetch("https://www.sendthisfax.com/api/upload", {method: "POST", body: formDataWithFile}) The response contains fax_public_id and page_count. PDFs must be unencrypted, at most 50 MB and 1000 pages. Step 2: call this tool with the fax_public_id and the recipient fax number. Two modes: - With an API key (Authorization: Bearer stf_live_... on this MCP connection): the fax price is debited from the prepaid credit balance and sending starts immediately — no checkout, no browser. sender_email and billing_country are optional (they default to the key's records). Buy credits at https://www.sendthisfax.com/en/credits. - Without an API key: sender_email and billing_country are REQUIRED and the tool returns a checkout_url the USER must pay in a browser; the fax is sent automatically once paid. In both modes, poll get_fax_status until status reaches "delivered" or "failed" (failures after payment are auto-refunded). For integration testing, +19898989898 is the designated test recipient number.
    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
  • Long/short positioning that perp venues publish for one symbol: binance, bybit, gate, okx. The venues do NOT measure the same thing, so every row carries `basis`: binance = top traders by POSITIONS; okx and gate = top traders by ACCOUNTS; bybit = ALL accounts. Compare a venue with itself over time, never as a like-for-like average across venues. `long_share` / `short_share` are fractions of 1 (0.63 = 63 %); `long_short_ratio` = long / short (1.72 = 1.72 longs per short; above 1 is long-heavy). Without `hours`: the newest 5-minute print per venue and its age in seconds (`venues` printed within the last hour, `stale_venues` went silent). With `hours` (1-168): an hourly `long_short_ratio` series per venue, the last print in each UTC hour. Covers about 40 major symbols only; any other symbol returns empty lists and a note, never zeros. `symbol` is the canonical base asset ('BTC').
    ConnectorOAuth
  • The CRM pipeline as a board: every stage in board order with how many contacts sit in it, plus a count of contacts with no stage. A "deal" here is a contact in a pipeline stage — there are no deal amounts. List the contacts in one stage with search_leads (stage).
    ConnectorAPI key
  • Returns instructions for migrating to PropelAuth in a frontend framework such as React, JavaScript, TypeScript, or when using Next.js for just the frontend (e.g. client-side rendered). Guidance includes migrating from several auth providers, such as Clerk or Auth0. Each guidance will include documentation from the auth provider and PropelAuth. It is important to follow the instructions carefully to ensure a successful integration. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc. CRITICAL: If the current implementation uses a traditional OAuth/OIDC flow (e.g., via express-openid-connect, passport-auth0, or similar backend-managed session libraries), you MUST select 'OAuth' as the framework, regardless of the frontend library (React/Vue/etc.). Only select 'React' or 'Javascript' if the current implementation uses a frontend-only SDK (like @auth0/auth0-react) or if using fullstack Next.js.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI harnesses to maintain a persistent memory layer backed by a local SQLite file, providing MCP tools to add, search, deprecate, and synchronize facts without deleting history.
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Middleware that converts a serverless handler with OpenAPI spec into an MCP endpoint following stateless MCP principles.
    9 npm
    34
    MIT

Matching MCP Connectors

  • Bybit crypto exchange, unified account and Funding wallet balances, open derivatives positions, orde

  • Search UK houses with land and manage your private saved-homes board.

  • Returns instructions for migrating from an existing auth provider to PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application. If the user is using Next.js as just a frontend (e.g. client-side rendered with or without server routes), use the migrate_to_propelauth_frontend tool. Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc
    ConnectorNo auth
  • Single 'call this first' entry-point that briefs an agent on the entire Revuo directory. Returns the taxonomy with subcategories, product counts per category, locked-vertical flags (the three verticals Revuo prioritizes), capability slugs valid per category, the canonical capability-kind taxonomy (integration/compliance/format/standard/workflow), and product-bound agent surfaces (mcpServer, agentSkill, grokBot). Surfaces are a property of a product — they are NOT category slugs. Use this once at the start of a session to ground every subsequent products.search / products.find_by_capability / tools.find_for_task call. Response: { directory: { name, tagline, url, policyUrl, capabilityKinds[] }, lockedVerticals[], categories[] (each with subcategories[], productCount, isLockedVertical, capabilitySlugs[]), surfaces[] (kind, description, listedOn=product), tools: { ...tool-name hints } }.
    ConnectorNo auth
  • Single 'call this first' entry-point that briefs an agent on the entire Revuo directory. Returns the taxonomy with subcategories, product counts per category, locked-vertical flags (the three verticals Revuo prioritizes), capability slugs valid per category, the canonical capability-kind taxonomy (integration/compliance/format/standard/workflow), and product-bound agent surfaces (mcpServer, agentSkill, grokBot). Surfaces are a property of a product — they are NOT category slugs. Use this once at the start of a session to ground every subsequent products.search / products.find_by_capability / tools.find_for_task call. Response: { directory: { name, tagline, url, policyUrl, capabilityKinds[] }, lockedVerticals[], categories[] (each with subcategories[], productCount, isLockedVertical, capabilitySlugs[]), surfaces[] (kind, description, listedOn=product), tools: { ...tool-name hints } }.
    ConnectorNo auth
  • Watchlist sweep over up to 10 coins in one call: the headline funding and open interest figures per coin — average funding, total open interest in USD, funding spread — with no per-venue rows, which keeps the response compact enough to compare positioning across a basket. Costs a single upstream call no matter how many coins you request, so prefer it over repeated single-coin calls. Figures come from the major liquid venues — Binance, Bybit, OKX and Hyperliquid; thin venues are excluded, since their outlier rates would otherwise distort the average by an order of magnitude. Coins with no major-venue data are listed in "unavailable" instead of failing the whole request. Reach for get_derivatives instead when you need the per-venue detail on one coin. Funding is returned in PERCENT per 8 hours (0.0061 means 0.0061%, not 0.61%) and also ANNUALIZED as a percent per year — 0.0067% per 8h is 7.3% a year, which says immediately whether a long is paying more than a bond yields. Open interest is in USD. Current snapshot.
    ConnectorNo auth
  • Search the CrowdSpace catalogue of crowdfunding and P2P lending platforms. Returns per platform: name, investment types, industries, country of headquarters, minimum investment, advertised return range, and the URL of its CrowdSpace profile. Use it to answer "which platforms let me…" questions and to cite specific platforms, always linking the returned profile URL. Do NOT use it for a full platform profile (fees, descriptions and terms are on the profile page, deliberately not in this API), nor for market-wide numbers — get_market_overview answers those in one call instead of paging through hundreds of results. Every filter value is enumerated in this schema; do not invent one. The catalogue keeps platforms that have stopped operating: a closed one is marked "no longer operating" in the result, and the count says how many of the matches are still running — say so rather than quoting the raw total as live platforms. Where a field is not in the result — fees, terms, the full description, the funding volume behind a sort — say it is not served here and link the profile. Do NOT fill the gap from your own knowledge: a figure you remember about a platform will be read as a figure from this catalogue.
    ConnectorNo auth
  • Real-time operational state of the public Lunium services, measured by an internal probe every 5 minutes: overall state plus per-component state (api, pix_charge = cash-in rail, crypto_sale = cash-out rail, webhooks, contract_docs) with latencies in ms, mapped to operational | degraded | unavailable | unknown. Missing, unknown or stale observations are not proof of an outage. Call it BEFORE debugging your own integration: if a rail is degraded, the right move is to wait or inform your user - not to rewrite working code. Also call it right after a call failed with erro=provedor_indisponivel or tempo_esgotado, to distinguish a Lunium-side incident from a mistake in your payload. Free, no key, safe to call often (new data at most every 5 minutes).
    ConnectorNo auth
  • Call this when the user asks how much leverage an exchange allows on a coin, what the maintenance margin or risk limit ladder is, which venue offers the highest leverage for a symbol, or whether an exchange recently cut leverage. Returns the current ladder per venue (tier, notional floor and cap, max leverage, maintenance margin rate) recorded daily by ByKaranteli, plus a change log. Pass symbol for one base asset (e.g. SOL) and venue for one exchange (bybit, okx, gate, htx, bitget, mexc). Without symbol, the first 30 rows of each list and the first 5 tiers of each ladder; pass symbol for every tier, or limit (up to 300).
    ConnectorNo auth
  • List active Storage objects in the caller's org, newest first. Each row is metadata plus ``download_url`` (bearer ``GET /v1/drive/{id}/content``). Published objects also include a fresh ``signed_url`` (presigned bucket GET, primary for agents) plus ``signed_url_expires_in`` / ``signed_url_expires_at``, and durable ``share_url`` / ``public_url`` (``/d/{share_token}``, console/human fallback). ``/d/{token}`` is Storage's public raw-bytes route. Pass ``work_id`` or ``project_id`` to list attachments (``project_id`` wins if both are set; folder filters are ignored on those joins). Pass ``parent_id`` / ``folder_id`` to list one folder (``root`` = org root). Omit both to list every active object. Folders sort first. Archived objects stay joined but are omitted. ``work_id`` / ``project_id`` list every Storage join (blobs and document-capable objects). Transcripts stay on ``file_list(work_id=)``. ``drive_list`` is a deprecated alias of this tool.
    ConnectorNo auth
  • Native balance and ERC-20 token balances of an address on one chain (eth_mainnet, base_mainnet, arbitrum_one, optimism_mainnet, polygon_pos, solana_mainnet; tokens where a data-capable upstream exists). Use it for a portfolio or a pre-flight funds check. Not for transfer history (use get_history) and not for a raw eth_getBalance you want to shape yourself (use rpc_call). Returns JSON: chain, address, native, tokens, tokens_note. Read-only; costs 10 weighted units, metered on your key. Needs your API key.
    ConnectorNo auth
  • Send a short text message (iMessage/SMS) to the user's own phone, the number they verified on the iMessage or SMS integration. Sends right now by default; pass send_at to schedule it for later (a reminder for tomorrow morning, a nudge before a meeting). send_at must be ISO 8601 WITH the user's UTC offset, e.g. 2026-09-18T09:00:00-04:00: work out their timezone from the conversation or ask, never guess UTC. Scheduled texts can be listed with list_scheduled_texts and cancelled with cancel_scheduled_text. The recipient is always the user themself; no other number can be reached. If no verified number is on file, the response says so and carries the link to connect one. Keep messages short and concrete; there is a rate cap, so never use this for routine chatter. If a send returns setup instructions, relay them and wait for the user to complete that step before retrying. Never report a failed send as delivered.
    Connector
    Destructive
    No auth
  • Check the selected service's current runtime readiness, input limits, pricing and retention before use. Returns service and details; ready=false means the underlying service is unavailable. Free cached runtime read; no external probe, payment, analysis or historical document retrieval. Use get_utility_example for a fixed integration sample instead.
    ConnectorNo auth
  • Read-only operation — no side effects, no parameters. Returns the real on-chain payment history to this service's fee receiver on Base: total_volume_usd, total_sales, by_token, up to 100 history rows (tx hash, payer, amount, block, timestamp), source="real_blockchain", plus the wallet state and a market snapshot. Use it when you need provable revenue or settlement evidence; use get_market_stats for prices and get_bot_status for integration health. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).
    ConnectorNo auth
  • Read-only operation — no side effects, no parameters. Returns the service's Telegram integration status as JSON: telegram_bot_running, telegram_token_configured, last_heartbeat, uptime_started, messages_sent, active_users, commands_processed, vip_invites_sent, plus the wallet state. Use it to confirm this service's own monitoring is alive (and its heartbeat recent) before trusting other outputs; use get_market_stats for market data or get_onchain_sales for provable revenue. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).
    ConnectorNo auth
  • [modeled, RISK AHEAD, CEX, over time] The same estimated CEX map as get_liquidation_map but as a time series: grid[t][b] is the estimated USD of leveraged positions with their liquidation price in price bin b at time cols[t] (ms), bins[b] the bin's centre price (240 bins fitted to the traded range), price[t] the close. A level disappears once price trades through it. Call this only to see WHEN a cluster formed and whether it survived; for the current picture call get_liquidation_map (far smaller answer, split by leverage and exchange). The answer is large (about 35,000 numbers). symbol: BASEUSDT. exchange: all | binance | bybit | okx. range: 12h | 1d | 3d | 7d.
    ConnectorNo auth
  • [modeled, RISK AHEAD, CEX, over time] The same estimated CEX map as get_liquidation_map but as a time series: grid[t][b] is the estimated USD of leveraged positions with their liquidation price in price bin b at time cols[t] (ms), bins[b] the bin's centre price (240 bins fitted to the traded range), price[t] the close. A level disappears once price trades through it. Call this only to see WHEN a cluster formed and whether it survived; for the current picture call get_liquidation_map (far smaller answer, split by leverage and exchange). The answer is large (about 35,000 numbers). symbol: BASEUSDT. exchange: all | binance | bybit | okx. range: 12h | 1d | 3d | 7d.
    ConnectorNo auth