Skip to main content
Glama
307,057 tools. Last updated 2026-07-28 03:58

"Dash" matching MCP tools:

  • Validate and lint a YAML document. Reports syntax errors with line/column, non-fatal lint warnings (tabs, implicit booleans, duplicate keys, dash-no-space) and document stats (documents, keys, max depth, bytes).
    Connector
  • Submit YOUR probability forecast on a live prediction market and build a public, audited track record. VoxOdds is the neutral scorekeeper: your forecast is stored append-only next to the market price captured at the same instant, both are Brier-scored when the market resolves, and your record appears publicly (model 'ext-<forecaster_id>') on voxodds.com/scoreboard beside the market and VoxOdds' own models — same methodology, losses published, no edits. Use list_trending_markets to find a market_id. `outcome` must match one of the market's outcomes; `probability` is YOUR estimate for that outcome (0.01-0.99); `forecaster_id` is your stable handle (3-32 chars, a-z 0-9 dash). Free; forecasts cannot be deleted or revised.
    Connector
  • Compute a cryptographic hash of text (SHA-1, SHA-256, SHA-384 or SHA-512) and return the hex digest. Use for checksums, cache keys, or verifying content. MD5 is intentionally not offered (broken, and unavailable in Web Crypto). LLMs cannot compute these reliably by hand, so always use this tool instead of guessing.
    Connector
  • List the org's intake connectors (e.g. GitHub Issues → Retasc issues, RTSC-189). Each row: provider, repo, target project, whether outbound sync-back is wired (hasToken), and created/revoked timestamps. METADATA ONLY — the inbound webhook secret and outbound GitHub token are NEVER returned. Read-only. Connecting a NEW repo is Dash-only (it takes a raw GitHub token that must not transit MCP); this surface is read + disconnect.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Settlement layer for AI agent commerce. 10 tools for identity, balance, task marketplace, transfers, and prediction markets. Agents earn FLAT tokens by completing bounties — no seed phrases, zero fees, instant transfers.

  • Read a URL as clean markdown, screenshot a website, url to PDF. Web access for agents, no signup.

  • Disconnect an intake connector by id (from list_connectors). Marks it revoked so its inbound webhook stops syncing — that endpoint then answers 401. Revoke-don't-delete (the row stays, flagged), idempotent, org-scoped (only connectors in YOUR org; an unknown/other-org id is NOT_FOUND). To reconnect, use the Dash (a fresh webhook URL + secret).
    Connector
  • Get a company's valuation multiples over time — EV/Revenue, EV/EBIT and P/E recomputed at each past quarter's filing date, one row per quarter. Up to ~10 years of quarters are sampled, but a row only renders when at least one ratio was computable at its filing date, so the series is bounded by the stored daily price history as well as the facts (a note reports how many sampled quarters were omitted). Every sample is point-in-time: it uses only the facts filed by that date (no look-ahead through restatements) and that day's close, with per-share figures and prices restated onto one split basis, and the same strict USD-only TTM/EV methodology as GetValuationMultiples. Quarter labels (FY{year} Q{n}) follow the company's own fiscal calendar derived from its annual reporting periods. A quarter missing an input has a dash for that ratio, never an estimate.
    Connector
  • Get a company's valuation multiples — EV/Revenue, EV/EBIT and P/E on trailing-twelve-month figures — together with a peer median and quartiles so the multiple can be read in context. The peer cohort compares like with like: when the industry holds enough similar-size companies the quartiles are computed over peers within a market-cap decade band around the company (the reply names the band), else over the whole industry. TTM figures sum the four most recent discrete fiscal quarters; enterprise value is market cap + long-term debt + current debt - cash & equivalents - short-term investments (the last leg subtracted only when tagged), the required concepts all tagged at the same balance-sheet date; a company missing a required input is excluded from that ratio, never estimated. All figures are USD-only (foreign-currency filers get no ratio), and the reply states the as-of dates behind each figure (TTM window end, balance-sheet date). Peer median and P25-P75 quartiles require at least 3 cohort companies with a computable ratio — a dash otherwise. For REITs (SEC SIC 6798) the reply also carries P/FFO and P/AFFO computed from the company's own SEC-stated FFO/AFFO reconciliation (a Nareit-style non-GAAP measure that is never XBRL-tagged), labelled with the company's verbatim measure name and basis (TTM or latest fiscal year); omitted when no verified reconciliation exists. Use GetValuationMultiplesHistory for the same ratios over time.
    Connector
  • Verify a SHA-256 hash against all deposits. Checks your own deposits and public deposits. Returns the matching deposit if found.
    Connector
  • [FIND] START HERE when you know what you want. Free-text search across every active RRG listing. This endpoint answers DEFINED intent, not open browse. Pass at least one concrete dimension: a brand, a product type/category, or an attribute (colour, material, size, SKU/style code). An enquiry that is only generic browse words ("what do you have", "show me everything") is rejected with status:"needs_more_detail" asking you to specify, no results are returned. To browse without intent, call list_drops instead. Indexed fields: title, description, agent description, and all string values in product_attributes (retail_sku / style code, canonical_name, collab, original_release, vendor, category, style_tags, occasion_fit, and any category-specific attributes emitted by enhancement). Accepts any of these query patterns: - product name or partial name - SKU / style code / model number (exact or partial, dash/space insensitive) - brand name, or brand + category ("<brand> <category>") - collaborator name(s) for collab items - attribute keywords from the description ("black suede", "heavyweight cotton", etc.) Multi-token queries are matched independently and ranked by field weight; a SKU-exact hit outranks a body-copy hit. Returns ranked matches with tokenId, priceRangeUsdc, authenticationStatus, retailSku, canonicalName, rrgUrl, and a variantSummary string listing every in-stock size with its price ("3.5=$1583, 4=$1899, 10.5=$770, …"). When the user asks about a specific size, ALWAYS pass that size in the `size` parameter, the response then includes sizeAvailable + sizePriceUsdc + sizeStock for a direct yes/no + price. For queries like "size 10.5" or "size M" the size is auto-extracted, but passing it explicitly is faster and unambiguous. When a size parameter is not used, read variantSummary (or the variants[] array) for per-size pricing BEFORE falling back to the priceRangeUsdc band. Per-size prices are exact; the band is only a floor→ceiling range. Next step: the returned payload has everything needed for the buy, call initiate_agent_purchase with selected_size and/or selected_color set to the chosen variant. Pass selected_color whenever the listing has a colour axis (variants[].color non-null) so fulfillment ships the right finish. get_drop_details is optional (adds signed image URLs + shipping context). If zero matches, try broader tokens, alternate naming (resale items are often indexed under multiple naming clusters, brand code / collab name / designer name / era / colorway). If still zero, call list_drops to browse.
    Connector
  • [FIND] START HERE when you know what you want. Free-text search across every active RRG listing. This endpoint answers DEFINED intent, not open browse. Pass at least one concrete dimension: a brand, a product type/category, or an attribute (colour, material, size, SKU/style code). An enquiry that is only generic browse words ("what do you have", "show me everything") is rejected with status:"needs_more_detail" asking you to specify, no results are returned. To browse without intent, call list_drops instead. Indexed fields: title, description, agent description, and all string values in product_attributes (retail_sku / style code, canonical_name, collab, original_release, vendor, category, style_tags, occasion_fit, and any category-specific attributes emitted by enhancement). Accepts any of these query patterns: - product name or partial name - SKU / style code / model number (exact or partial, dash/space insensitive) - brand name, or brand + category ("<brand> <category>") - collaborator name(s) for collab items - attribute keywords from the description ("black suede", "heavyweight cotton", etc.) Multi-token queries are matched independently and ranked by field weight; a SKU-exact hit outranks a body-copy hit. Returns ranked matches with tokenId, priceRangeUsdc, authenticationStatus, retailSku, canonicalName, rrgUrl, and a variantSummary string listing every in-stock size with its price ("3.5=$1583, 4=$1899, 10.5=$770, …"). When the user asks about a specific size, ALWAYS pass that size in the `size` parameter, the response then includes sizeAvailable + sizePriceUsdc + sizeStock for a direct yes/no + price. For queries like "size 10.5" or "size M" the size is auto-extracted, but passing it explicitly is faster and unambiguous. When a size parameter is not used, read variantSummary (or the variants[] array) for per-size pricing BEFORE falling back to the priceRangeUsdc band. Per-size prices are exact; the band is only a floor→ceiling range. Next step: the returned payload has everything needed for the buy, call initiate_agent_purchase with selected_size and/or selected_color set to the chosen variant. Pass selected_color whenever the listing has a colour axis (variants[].color non-null) so fulfillment ships the right finish. get_drop_details is optional (adds signed image URLs + shipping context). If zero matches, try broader tokens, alternate naming (resale items are often indexed under multiple naming clusters, brand code / collab name / designer name / era / colorway). If still zero, call list_drops to browse.
    Connector
  • Validates a Chilean RUT (Rol Único Tributario) using the official Chilean modulo-11 checksum algorithm. Use this tool when processing Chilean invoices, tax forms, user registrations, e-commerce orders, or any document requiring a valid Chilean taxpayer identifier. Accepts RUT with or without formatting (dots and dash). Returns whether the RUT is valid and the cleaned RUT. Does not verify if the RUT is active in the SII registry.
    Connector
  • Show the signed-in user's Workopia dashboard (saved, tailored, and applied jobs + latest resume). Requires OAuth. Default action is list; optional status_filter (all | saved | tailored | applied). Use whenever the user asks to recall their Workopia activity: 'my applications', 'what jobs have I saved / applied to / tailored', 'show my dashboard', 'where did I leave off'. Returns a secure link to open the full dashboard on the web.
    Connector