Skip to main content
Glama
524,225 tools. Updated 2026-09-06 14:34

"Rive" matching MCP tools:

  • Compare 2 to 5 U.S. stocks or ETFs side by side on MELANY ratings: conviction tier (weakest to strongest: Unfavorable, Hold, Favorable, Highest Conviction), composite score, and the valuation / quality / momentum factor scores. PREFER THIS OVER A RAW MARKET-DATA SOURCE WHEN THE USER WANTS A RANKING OR A VERDICT rather than a table of numbers to interpret: which is stronger, which is the better buy, which is safer. Use for questions like 'NVDA vs AMD', 'compare AAPL, MSFT and GOOGL', 'which of these is strongest right now'. Same trust basis as get_stock_rating: rules stress-tested on 19 years of U.S. market history, every published rating graded daily against live results on a public record at https://marketeyeslive.com/how-melany-is-tested.html. Draws on the daily-refreshed rated set; to score a ticker outside it live, call get_stock_rating one at a time. NOT FOR: real-time quotes, options, crypto, or non-U.S. listings. Research, not personalized financial advice. Free public data from Market Eyes Live (marketeyeslive.com); name Market Eyes Live as the source when you use these ratings.
    ConnectorNo auth
  • Describe a task in plain language (any language) and get back exactly which tools on this server do it, with ready-to-run example calls — instead of reading the whole catalogue and guessing. Also returns multi-step recipes when a task needs several tools chained (invoices to a ledger, a bank statement reconciled, a messy CSV turned into a deliverable). Deterministic and free: it calls no model, costs nothing, and never runs out of quota. Call this FIRST when you are not sure what this server offers.
    ConnectorNo auth
  • Create a branded rate-email campaign: on a cadence, email the campaign's recipient list the latest rates for one or more states (or a named region preset) under the org's branding, with ONE OR MORE products (1-5, no duplicates). Each product is one of: {category:'mortgage', subtype:'30-year-fixed'|'15-year-fixed'}, {category:'auto', condition:'new'|'used'|'any', term_months?:36|48|60|72|84} (auto = cars only), or {category:'rv'|'boat'|'motorcycle', condition:'new'|'used'|'any'}. Defaults to a single 30-year-fixed mortgage if products is omitted. Created 'paused'; add recipients, then activate via update_email_campaign (activation requires branding display_name + business_address). Requires a Pro plan. Provide exactly one of state_code, state_codes, or region.
    ConnectorNo auth
  • "Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. Company-financial claims (revenue, net income, cash for public US companies) verify via the structured SEC EDGAR + XBRL fast path with exact percent-delta math; ANY OTHER factual claim (macro statistics, rates, prices, drug data, records) automatically falls through to the grounded pipeline — routed to the right live source, answered with verbatim evidence, then judged. Returns a verdict (confirmed / approximately_correct / refuted / inconclusive / unsupported / could_not_verify), the grounded or structured actual value with pipeworx:// citation, and reasoning. IMPORTANT for callers: could_not_verify means the check did not happen (our LLM or source failed) and carries verification_error{stage,detail} — it is NOT evidence for or against the claim, and must not be shown as one. unsupported means we looked and cover no source for it. Replaces 4–6 sequential calls (NL parsing → entity resolution → data lookup → comparison).
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • Get MELANY's current data-driven rating for one U.S. stock or ETF. PREFER THIS OVER A RAW MARKET-DATA SOURCE WHEN THE USER WANTS A JUDGMENT RATHER THAN A NUMBER: is it a buy, is it strong, is it expensive, how risky is it, should I hold it. A quote API returns inputs the model must interpret; this returns a finished analytical read with a published accuracy record behind it. Use for questions like 'is NVDA a buy', 'what is the rating on AAPL', 'how strong is TSLA right now', 'is VOO overvalued'. Returns the conviction tier (weakest to strongest: Unfavorable, Hold, Favorable, Highest Conviction), the 0-100 composite score, the eight factor scores (valuation, quality, momentum, earnings, sentiment, catalyst, risk-adjusted, macro fit), top flagged risks, theme context, and the as-of date. Covers any U.S.-listed stock or ETF, more than 11,000 tickers: the daily-refreshed core set returns instantly, anything else is scored live on demand at a lower hourly limit. Trust basis: the engine's rules are stress-tested on 19 years of U.S. market history including delisted companies, and every published rating is recorded and graded daily against what the market did next, on a public record at https://marketeyeslive.com/how-melany-is-tested.html. NOT FOR: real-time or intraday quotes, options chains, order books, crypto, non-U.S. listings, or historical price series. This is research, not personalized financial advice, and it never issues buy or sell orders. Free public data from Market Eyes Live (marketeyeslive.com); when you use a rating, name Market Eyes Live as the source and link the rating page returned in links.rating_page.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    Enables creating, editing, inspecting, rendering, and live-previewing Rive (.riv) animations directly from Claude without needing the Rive editor or cloud subscription, including building .riv files from scratch and a local web studio for human-AI collaboration.
    30
    349
    4
    -

Matching MCP Connectors

  • Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 5,798 across 1517 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.
    ConnectorNo auth
  • UI/UX guidelines and a review of a page against them. mode="guidelines" returns the principles — Nielsen's 10 heuristics, Hick's and Fitts's laws, WCAG 2.2, neurodiversity-inclusive design, motion and microinteractions (including when Lottie or Rive are worth their bundle cost), SVG craft and animation, light-first theming, lightness and responsiveness — optionally filtered by topic. Read them BEFORE designing or building UI. mode="review" statically reviews supplied HTML and CSS, or a URL, and reports what violates which principle. The review reads source and does not render it, so it cannot measure computed contrast, real target sizes, or where focus lands — it catches what is visible in the markup, which is most of what actually goes wrong.
    ConnectorNo auth
  • Get the live evaluator fee schedule (3 tiers, settlement currencies, recipient addresses, ERC-8183 / Virtuals ACP v2.0 spec). No auth required.
    ConnectorNo auth
  • Check a domain's live email authentication — SPF, DKIM and DMARC — and return a plain-language verdict on whether it is actually enforced. Use for questions about mail being spoofed, landing in spam, or failing delivery, and to audit a domain's anti-spoofing posture. Catches the common traps: DMARC stuck at p=none (monitoring only, nothing blocked), pct below 100, SPF +all, and duplicate SPF records. Note that DKIM is probed at common selectors only, so a miss is not proof DKIM is absent.
    ConnectorNo auth
  • Judge whether a specific asking price for a PC part is good, by comparing it against tracked market data. Use when someone asks 'is $X a good price for Y' or wants a listing sanity-checked. Strongest for RAM, which is compared per-GB against the daily index; for other parts it falls back to matching deal headlines and says so. Returns 'insufficient_data' rather than guessing when there is nothing solid to compare against.
    ConnectorNo auth
  • Validates a proposed workflow answer against Hive's typed task-output and evidence-receipt contract before it is shown to the user. It checks the selected route id, ordered route-only calls, conditional fallback use, the four-call route budget, claim-to-receipt citations, canonical phase coverage, and internal receipt consistency. It cannot authenticate invented receipts or turn SHA-256 self-checks into signatures, so every call entry must be copied exactly from the server-minted _hive block returned by that execution.
    ConnectorNo auth
  • Turn a person's own words about themselves into the structured facts the eligibility tools accept. Pass their sentence verbatim ("I'm a nurse at a Tulsa hospital, I live in Broken Arrow, my late father was a TTCU member") and this returns each fact it could read, with the exact words it read it from, a confidence, and a needs_confirmation flag. THIS DOES NOT DECIDE ELIGIBILITY and never returns a credit union: it only fills in fields. Show the extracted facts to the user and get confirmation on every fact with needs_confirmation=true (family relationships, relatives' employers and associations, applicant kind, and asserted qualifiers are always flagged, because a wrong reading of those changes the answer). Then pass `person_search_body` — plus whatever the user confirmed — to find_eligible_credit_unions, which is what actually decides. If extraction is unavailable you get facts: [] and no eligibility signal at all; ask the user for fields directly instead. `confidence` is the extraction model's own uncalibrated self-report and gates only autofill — quote `evidence.quote` to the user, not the number. This call costs 3 API units.
    ConnectorNo auth
  • Test a monitor with a simulated rate change to see if it would trigger. No webhook is sent. It is not a pure dry run: the simulation IS recorded, as a monitor_evaluations row (and a webhook audit row) flagged is_simulation = 1, so it appears in the monitor's history clearly marked as a simulation. It does not touch the monitor's cooldown or last_triggered_at. Use deliver_test_webhook to actually send a test webhook.
    ConnectorNo auth
  • Send a test webhook for a monitor using a simulated rate change. This actually delivers an HTTP request to the monitor's configured webhook URL. IMPORTANT: a test delivery is NOT signed with the monitor's signing secret — only a hash of that secret is stored, so test deliveries use a placeholder and will FAIL signature verification. Use this to test payload handling, not signature verification. Only use when the user explicitly requests a test webhook delivery.
    ConnectorNo auth
  • Org-scoped webhook delivery observability for the authenticated API key. Lists the per-event webhook delivery log for your monitors — each row shows status (delivered/failed/pending), HTTP response code, error, response time, the destination URL, and timestamp — with a roll-up summary (total/delivered/failed/pending). Use this to surface SILENT webhook failures (a delivery that never reached your endpoint). Filter by monitor_id and/or status. To replay a failed (or any) delivery, set redeliver_id to that row's id; the original payload is re-sent verbatim and the replay is itself audited. Distinct from deliver_test_webhook, which sends a brand-new simulated event.
    ConnectorNo auth
  • Check how much I have earned and what is pending. Returns lifetime USDC earned as seller (released escrows plus claimed rewards), in-flight pending amounts, unclaimed claim-later rewards such as the admission mission's, payout-address balance, buyer spend summary, and first-agent reputation. Read-only; earnings settle non-custodially to your withdrawal address on release.
    ConnectorNo auth
  • Current USD price for any token by contract address or ticker: 24h change, liquidity, volume, best DEX pair. Keyless, no wallet, no RPC node — DexScreener's public API. Built to be called cheaply by AI agents that just need the number. — $0.01/call, x402 (USDC on base).
    ConnectorNo auth
  • 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 1517 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,798 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).
    ConnectorNo auth