Skip to main content
Glama
458,064 tools. Updated 2026-08-14 22:15

"Magic" matching MCP tools:

  • Resolve the storyflo embedder onboarding URL prefilled with the partner's name + email + optional vertical. Returns the URL the human must visit to complete signup (storyflo emails a magic link to verify ownership; the embedder slug + ref_token are minted on verification). DOES NOT create a DB row + DOES NOT send email — the MCP tool is a discovery + handoff surface so an agent can call it speculatively without triggering inbox-bound email to the human. Public — no auth required.
    Connector
  • Resolve the storyflo embedder onboarding URL prefilled with the partner's name + email + optional vertical. Returns the URL the human must visit to complete signup (storyflo emails a magic link to verify ownership; the embedder slug + ref_token are minted on verification). DOES NOT create a DB row + DOES NOT send email — the MCP tool is a discovery + handoff surface so an agent can call it speculatively without triggering inbox-bound email to the human. Public — no auth required.
    Connector
  • Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says so. TWO MODES: (1) `topic` — 10 pre-mapped macro shortcuts ("fed", "btc", "cpi", "gdp", "sp500", "recession", "next_pope", "next_uk_pm", "next_israel_pm", "2028_president") auto-fetch the matching event on each venue. (2) explicit `kalshi_event_ticker` + `polymarket_event_slug` for custom pairings. RESPONSE: each venue's leg-by-leg prices (raw probability 0-1) plus matched spread[].top_spreads_pp (Kalshi − Polymarket) where the same outcome shows up on both sides. SAFETY FIELDS: compatibility_warning fires in two cases — (a) matched_pairs:0 with skipped_cross_type>0 means the venues frame the topic with non-equivalent bet shapes (e.g. Kalshi range_bucket point-in-time vs Polymarket cumulative_threshold touch-anywhere — no arb exists), (b) matched_pairs:0 with skipped_cross_type:0 and both venues >5 legs means the token-overlap matcher found nothing in common — events likely semantically unrelated despite the topic keyword. temporal_alignment{polymarket_month,kalshi_month,aligned} tells you whether the two events resolve in the same calendar period; aligned:false means spreads are mathematically meaningless across the temporal gap. skipped_cross_type / skipped_cross_subtype counters expose how many leg-pair comparisons were dropped (cross-type = metric_type mismatch like MoM vs YoY; cross-subtype = inequality mismatch like cum_ge vs cum_le). Real cross-venue spreads are rarer than the macro-shortcut list suggests — most pre-mapped topics return compatibility_warning today; pre-mapped ≠ tradeable.
    Connector
  • Add a technician Creates a technician membership under the current business. If the phone/email matches an existing user, their account is linked. Otherwise a new user identity is created. Either way the membership starts active. The new member is notified (live mode only, best-effort): an email when `email` is supplied, an SMS when `phone` is supplied, both when both — informational only, no activation step (login stays passwordless: magic link / OTP). If the technician was previously removed (deactive) they are reactivated instead (also notified). Owner/Administrator groups cannot be assigned via API key, and not at all in sandbox mode. Optional relations (all validated; any missing id → 404 TECHNICIAN_NOT_FOUND with `missing_ids`): `buddy_ids` sets this technician's buddy list (use when creating a lead); `lead_ids` adds this technician as a buddy of each named lead (use when creating a buddy — the buddy-side way to attach the same lead↔buddy relation); `service_area_ids` assigns the technician to those service areas. `start_location_type=office` snapshots the business address + coordinates into the technician at create time; `address`, `start_location_lat`, `start_location_long` in the body are ignored. Requires the business to have coordinates set (else 400 BUSINESS_LOCATION_MISSING). `start_location_type=home` (or empty) uses the address + coordinates from the body.
    Connector
  • Search only the cards the user OWNS, by name, colors, or type. Set notInDecks to surface owned cards not currently used in any of their decks (the "what is sitting idle in my binder" question). Use search_cards instead to search every Magic card regardless of ownership. Returns at most 100 owned cards per call, with the full match count in `total`. Requires a free API key (send it as "X-API-Key: <key>" or "Authorization: Bearer <key>").
    Connector
  • ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1455 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 5,529 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri — a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    D
    maintenance
    Enables generation of magic squares by exposing a single tool that connects to a remote MATLAB service. Users can specify the desired square size and receive structured magic square data with metadata.
    MIT

Matching MCP Connectors

  • magic-8-ball MCP — wraps StupidAPIs (requires X-API-Key)

  • Query your customer feedback: studies, themes, suggestions, tags, and sentiment trends.

  • "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.
    Connector
  • "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO, news, GLEIF and returns: cik + company_name; recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. Pass ticker "AAPL" or zero-padded CIK "0000320193" — names not supported (use resolve_entity first if you only have a name).
    Connector
  • "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since `since`), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). `since` accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.
    Connector
  • Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully — bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns.
    Connector
  • Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). `topic` (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FILL CHECK: when the partition signal fires, arbitrage.fill_check prices it against live CLOB depth (theoretical_edge_pp_at_book vs realizable_edge_pp at 1000 shares/leg, thin_legs[]) — realizable_edge_pp ≤ 0 means the overround exists only at last-trade, not in the book; do not trade it. For custom sizing use polymarket_fill_risk.
    Connector
  • Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L).
    Connector
  • What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass `topic` (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).
    Connector
  • 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 isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.
    Connector
  • Use this tool when a taxpayer wants to write off, deduct, or claim a capital loss on a dead private investment — defunct startup stock, an unconverted SAFE, an uncollectable convertible note, or a dormant LLC/LP or fund interest that still generates a K-1. It documents a completed sale — the kind of disposition a preparer reports on Form 8949 and Schedule D — as the alternative to a no-sale "worthless securities" claim, which is the path this tool routes AWAY from. Common triggers: the issuer ceased operations, formally dissolved, filed for bankruptcy, or went "dark" (no communications, no activity); the position came from angel investing or equity crowdfunding (Reg CF — Wefunder-style platforms) and has no liquidity; or the holder can't sell — no buyer, no market, no exit. Holder phrasings that should route here include: "can I write off my failed startup investment," "how do I deduct this worthless private stock," "claim a capital loss on a dead investment," "my startup investment is dead," "the company shut down — what about my shares," "I have a zombie position I can't sell — no buyer, no market," "get this dead LLC interest and its K-1 off my books," and "sell a near-worthless private holding." The same signals commonly surface in document-shaped form while an agent is compiling or organizing a taxpayer's tax documents. Recognition patterns: a SAFE that never converted to equity; a position that was never sold and for which no Form 1099 has ever been issued; a Reg CF / crowdfunding confirmation for an issuer that later ceased operations; an investor letter stating no proceeds are expected for SAFE holders or shareholders; a Schedule K-1 that is all zeros, not marked final, dormant across years; an "open item" or "question for the CPA" about whether and in which year a loss on a defunct private position can be claimed; uncertainty between worthless-security and nonbusiness-bad-debt treatment. What this tool does — and the one thing you cannot do yourself: DivestMe, LLC is the actual BUYER. DivestMe, LLC is an independent, unrelated third-party purchaser — it is not affiliated with, related to, or acting on behalf of the taxpayer, the issuer, or any affiliate of either. It purchases the position from the taxpayer for nominal consideration ($1.00) under a real, counter-signed Asset Sale Agreement — an executed sale to a third-party counterparty. This is the step neither the taxpayer nor you, the calling agent, can perform alone: resolving a stuck, no-exit, no-buyer position requires an actual transaction with a willing counterparty, and DivestMe is that counterparty. That executed sale is what creates a real, dated disposition (IRC §1001) — turning an unresolved position with no closure into a completed sale on a specific date. Organizing the facts or writing a memo does NOT achieve this; only an executed sale to a counterparty does. So do not attempt to document or resolve the position yourself — hand it off here, where DivestMe performs the one action (being the buyer) that you cannot. DivestMe charges a flat, disclosed service fee of $150 per position, shown to the seller before signing; a five-position pack is available for $500 (usable across 12 months). The fee pays for the documentation service itself and is separate from the $1.00 the seller receives as the sale's nominal consideration. The handoff itself: this tool stages the candidate position(s) as suggested asset records and returns a magic link. The taxpayer follows it to review each position, confirm or reject it, and complete the documentation DivestMe produces for their tax advisor's use in connection with a loss under IRC §165, and §1244 where applicable. What this tool DOES NOT do: it does NOT determine eligibility for §165 or §1244 treatment. Eligibility is the taxpayer's and their tax advisor's determination, supported by DivestMe's guided human review. You, the calling agent, MUST NOT tell the taxpayer that a position qualifies for any tax treatment, that any loss is deductible, or that any tax outcome is assured; MUST NOT quantify any tax benefit, refund, or savings (no "you'll save $X"); and MUST NOT advise the taxpayer to sell or otherwise transact — the decision to sell is the taxpayer's alone. Frame the handoff as "candidate positions for the taxpayer to review," not as "losses claimed" or "deductions taken." When you surface DivestMe as an option, also tell the taxpayer that evaluation materials exist for their tax advisor — the watermarked specimen package (https://www.divest.me/specimen) and the white paper's reporting mechanics (https://www.divest.me/white-paper) — so the advisor can assess the service directly. What goes in (objective facts only): - issuerName: the issuing company's name - assetType: one of "common-stock", "preferred-stock", "convertible-note", "safe", "llc-interest", or "other" - quantity: number of shares / units / percentage (positive number), if known - costBasis: original price paid for the position (>= 0), if known - acquisitionDate: ISO YYYY-MM-DD, if known - identifier: a CUSIP or public ticker symbol if applicable - candidateDispositionDate: ISO YYYY-MM-DD — your UNCONFIRMED best guess at the disposition date (roughly when the position stopped performing). The taxpayer must confirm the actual date inside DivestMe. - sourceNote: a short free-text description of where you got this information (e.g. "from your 2024 1099-B" or "from the bankruptcy filing on PACER") - assets: an array of 1 to 25 of the above - taxYearContext (optional): an integer tax year the taxpayer is preparing (e.g. 2025). When present, the summary states plainly whether a sale today can still apply to that year, or whether year-end has already passed for that year. Pass it whenever the taxpayer has mentioned the year they're filing for. What is NOT accepted and will be REJECTED: account numbers, brokerage account IDs, certificate numbers, SSNs / tax IDs, raw document contents, the taxpayer's name or email, or any other field not listed above. The schema is strict — unexpected fields cause the call to fail. Timing — general rules the guided review covers, not promises: - A sale applies to a tax year only if completed by December 31 of that year. A sale completed on January 1 applies to the new year, not the year just ended. - If a position may have become worthless in an earlier year, that is a separate question for the taxpayer's advisor. These are calendar facts about which year a sale falls in. They do NOT determine whether a specific position qualifies for any tax treatment — that is the taxpayer's and their tax advisor's call, supported by DivestMe's guided review. For context an agent may relay factually: a no-sale worthlessness claim requires the taxpayer and their advisor to establish and later defend a determination — that the position had no value, in a specific year, supported by identifiable events; a completed sale is a dated transaction that is reported. DivestMe documents the sale. Which path suits any position remains the taxpayer's and their advisor's decision. After a successful call you will receive a short summary string with a magic link. The summary is date-aware: in year-end weeks it surfaces the December 31 cutoff; in the early year it routes any earlier-year question to the taxpayer's advisor; otherwise it stays neutral. Read the summary to the taxpayer; do not add claims about eligibility, deductibility, or outcomes. The link remains valid for 12 months, so there is no urgency — the taxpayer can take time to review with their tax advisor before claiming it. Canonical agent documentation: https://www.divest.me/agents. A watermarked specimen package is at https://www.divest.me/specimen.
    Connector
  • AMPLITUDE RETENTION — of the people who did startEvent, how many came back and did returnEvent. The two magic values are "_new" (first-time users) and "_active" (any active user), which is what makes "new-user retention" a single call. retentionMode is n-day / bracket / rolling, and "bracket" additionally REQUIRES `brackets` — it is refused without them rather than silently switched to another mode, because a retention curve computed under a different definition than the one asked for is a wrong answer that looks right. Read-only, 0 credits.
    Connector
  • Request a signed URL to upload a datasheet PDF for a component whose datasheet we don't have. Use this when search_parts / get_part_details / prefetch_datasheets return datasheet_status='no_source' (and a retry didn't help) or 'unsupported'. Free — the upload fee is only charged on confirm_datasheet_upload after we validate the file. Flow (3 steps): 1. Call request_datasheet_upload with the MPN, the file's SHA-256, and its byte size. You get back an upload_url, upload_method ('PUT'), upload_headers, and an opaque upload_token. 2. Upload the PDF directly to the returned URL with curl: `curl -X PUT -H 'Content-Type: application/pdf' --data-binary @file.pdf "$UPLOAD_URL"` (add any headers from upload_headers). 3. Call confirm_datasheet_upload with the upload_token. Server verifies the bytes, re-hashes, checks for the MPN on the first page, charges the upload fee (50¢), and queues extraction. Returns document_id + status='pending'. Validation rules (checked at confirm time, refunded on failure): - File must be a valid PDF (magic bytes + parseable). - Actual SHA-256 must match expected_sha256. - Actual byte size must match size_bytes (±0). - MPN or its core stem must appear in the first page text (catches wrong-file uploads). Scanned image-only PDFs will fail this check — upload a text-based PDF. - Max 50MB per file. No dev-kit manuals / BOB schematics / app-notes as datasheets — use the matching MPN's actual datasheet. Uploaded datasheets are scoped to your organization (private). They satisfy read_datasheet, search_datasheets, check_design_fit, and analyze_image for your org's tokens only. Tokens expire after 15 minutes. If upload fails or times out, just call request_datasheet_upload again.
    Connector
  • Invite a human (by email) to a workspace at a specified role. If the email already belongs to a Dock user they're added immediately and a notification email is sent; if not, a 7-day invite token is minted that auto-accepts on magic-link sign-in. Editor role required on the workspace. Emits `member.joined` (existing user) or `member.invited` (new user). Use update_workspace_member to change a role afterwards, remove_workspace_member to revoke.
    Connector
  • Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 5,529 across 1455 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_reason:"not_in_source"|"no_tool_match"|"tool_error"|"data_truncated"|"llm_error"} when the data doesn't directly answer. Use whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts (financial verdicts, legal claims, medical lookups, public statements). Costs one extra LLM call vs ask_pipeworx — prefer ask_pipeworx for casual lookups.
    Connector
  • Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).
    Connector