Skip to main content
Glama
615,520 tools. Updated 2026-09-27 06:04

"Tether" matching MCP tools:

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables MCP-compatible agents to remember, recall, link, and forget durable notes across devices, with local SQLite storage and optional libSQL/Turso sync.
    4
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to securely control a real, logged-in browser with per-site permissions, per-action approvals, secret redaction, and a tamper-evident audit log, all locally without a cloud relay.
    325,085 npm
    MIT

Matching MCP Connectors

  • Tether MOS telemetry + Boltz BTC↔USDC atomic swap broker MCP

  • Tether MiningOS bridge — site telemetry, paying demand, BTC to USDC settlement

  • Save durable memories with automatic deduplication: re-remembering a fact updates it instead of creating duplicates, keeping notes refined across sessions.
    MIT
  • Search project memories by keyword or plain language, then follow related associations to find the most relevant notes before starting a task.
    MIT
  • Retrieve token data including current and historical prices, decimals, symbols, logos, and verification status across supported blockchains. Supports single or batch queries.
    MIT
  • Mark a memory as no longer current by its ID, soft-deleting it to exclude it from recall while preserving the record for reversible restoration.
    MIT
  • Monitor whale transactions, CEX inflows/outflows, bridge activity, and stablecoin mints/burns to spot market-moving events and anomalies.
    MIT
  • Check if USDT or other stablecoins can be traded, bought, sold, or withdrawn in a country, including MiCA status, venue delistings, custody rights, and compliant alternatives.
    MIT
  • Establish a bidirectional connection between two memory entries using their unique IDs, enabling easy navigation and association.
    MIT
  • Query the canonical stablecoin freeze ledger — the HISTORY of freeze / unfreeze / destroy events by Tether (USDT), Circle (USDC/EURC), Paxos (USDP) and First Digital (FDUSD), sourced from the issuers' own on-chain blacklist events across Ethereum, Polygon, Optimism, TRON and more. Filter by frozen address, chain, kind, or time; omit all filters for the most recent events. This is the EVENT HISTORY — to check whether an address is frozen right now, use check_stablecoin_freeze instead. Each row is a verifiable on-chain fact (issuer acted on address at block/time); it never states the cause. Free.
    ConnectorNo auth
  • Unified search across every Aether corpus at once — SEC filings, Japan/EDINET and Korea/DART annual reports, EU financial regulation, and earnings calls/press-release exhibits — auto-routed and merged into one corpus-tagged, citation-complete result set. Use this for MOST questions: you do NOT have to pick the right corpus, and it will not miss same-day earnings (8-K earnings exhibits live in the transcript/press corpus, which a filings-only search silently misses). Each hit carries a `corpus` tag, an accession/citation string, a source URL, a 0-1 confidence score and an anchor_id. ALWAYS pass `issuer` (ticker, cik, or company_name for non-US filers) plus `fiscal_year` when you know it — it is forwarded to every corpus, so one named subject scopes filings and earnings calls together: fast and precise. A call with no issuer runs as scope=cross_company: slower, ranked by relevance only, and the response sets `quality_caveat` — check for that field before trusting the result. Use scope=cross_company deliberately, only for questions genuinely about many issuers ("which filers name NVIDIA as a supplier"). Filters are forwarded, not dropped: form_type / accession_number / section / return_format reach the filing corpora (sec/jp/kr), quarter and fiscal_year reach the earnings-call corpus, and EU regulation takes none of them (it has no issuer, form or quarter) — a filing filter therefore narrows an omitted `corpora` to sec/jp/kr. Any field not listed here is REJECTED with a 400 naming it, rather than silently ignored. Reach for financial_search / transcript_search / regulation_search only when you deliberately want to force a single corpus. Ownership questions do not go through search at all: holdings_by_security and holdings_by_manager.
    ConnectorNo auth
  • Search SEC filings (10-K, 10-Q, 8-K, registration statements/prospectuses and press exhibits; S&P 500 coverage, ~10 years) with hybrid semantic + keyword retrieval. TWO MODES. Search mode (pass `query`): results ranked by relevance, highest first. FETCH MODE (omit `query`): no ranking at all — pass an issuer plus any of form_type / fiscal_year / accession_number / section and get that filing's sections back in filing-date-desc then document order, in tens of milliseconds. Use fetch when you already know WHICH document you want and only need its text. ALWAYS pass `issuer` (ticker, cik or company_name) — the company the question is about — plus `fiscal_year` and/or `form_type` when you know them. Scoped calls are fast and precise. A call with no issuer runs as scope=cross_company: slower, ranked by relevance only, and the response sets `quality_caveat` — check for that field. Use scope=cross_company deliberately only for questions that are genuinely about many companies ("which filers name NVIDIA as a supplier"). Built for agents: every hit is a ready-to-cite payload — exact filing-section text, form type, filing date, accession-numbered citation, source URL and a 0-1 confidence score — no HTML parsing, no EDGAR pagination. Use for revenue/segment figures, risk factors, M&A and contract terms, customer/supplier concentration, and any claim that must trace to a primary source. Coverage is NOT US-only: Sweden/Bolagsverket, Japan/EDINET, Korea/DART annual reports are included. Those issuers have no US ticker — pass `issuer.company_name` (e.g. "Sivers Semiconductors", "Samsung Electronics", "Ajinomoto") or scope a whole market with `jurisdiction` (["SE"], ["JP"], ["KR"]).
    ConnectorNo auth
  • Search earnings-call transcripts and earnings press-release exhibits by speaker turn (CEO/CFO prepared remarks, analyst Q&A, press releases). Returns verbatim quotes as agent-ready payloads: speaker name/role, fiscal year + quarter, call date, source_type (asr_call = our own ASR of the real call vs press_release), sec.gov source URL and citation string. Use for guidance, management tone and forward-looking color that filings don't capture; pair with financial_search to back narrative with filed numbers. ALWAYS pass `issuer` (the ticker whose calls you mean) plus `fiscal_year` when you know it — a named call is scoped to that issuer's calls, fast and precise. A call with no issuer runs as scope=cross_company: slower, ranked by relevance only, and the response sets `quality_caveat` — check for that field. Use scope=cross_company deliberately, only for questions genuinely about many companies ("which management teams talked about tariff pass-through"). Narrow further with speaker_role, lookback_quarters or source_type. FETCH MODE: omit `query` entirely and pass issuer.ticker plus fiscal_year / quarter / date_from / date_to to get that call's segments back in call-date-desc then spoken order, with no ranking and in tens of milliseconds — the right tool when you already know WHICH call you want. For onset/"first mention" questions (when did a topic first come up), bound with date_from/date_to and set order='earliest' — a date pair, not a fiscal year, is the right tool there.
    ConnectorNo auth
  • What a fund owns: an institutional manager's reported equity book from SEC Form 13F — top positions by value, with quarter-over-quarter share changes and new/increased/decreased flags. Answers 'what does Bridgewater hold', 'what did this fund buy last quarter', 'show me their largest positions'. Look up by manager name (partial match; the largest matching filer wins, since names like 'Vanguard' map to several distinct CIKs) or by exact CIK. Also returns the filer's published contact details — signatory, title, phone, and business address from the filing's cover page and signature block, each citable to the accession number. EDGAR publishes no email address for 13F filers, so none is returned and none should be inferred. Coverage: quarter ends from 2024-12-31 through 2026-06-30; the newest quarter is still filling in as filers submit, and a manager who has not filed it yet falls back to their most recent quarter, named in coverage_caveat. 13F covers US-listed long equity and options only — no shorts, cash, bonds or non-US listings — and is filed 45 days after quarter end, so it is a lagged snapshot, not a live portfolio.
    ConnectorNo auth
  • Assess CURRENT congestion and delay risk at a single seaport. Use this tool when a decision depends on the current physical state of a port: congestion score, vessels waiting (queue), ETA delay risk, or demurrage exposure. Call BEFORE making recommendations involving port selection, cargo routing, vessel scheduling, ETA risk, demurrage exposure, freight timing, or supply-chain disruption. Returns a live operational signal (not a static port-information lookup) with congestion score, real observed vessel state, estimated delay, expected/worst-case demurrage (USD), confidence, source provenance and validation window. Args: port_id: UN/LOCODE of the port, e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá), "CNSHA" (Shanghai).
    ConnectorNo auth
  • Get the short-horizon 24/48/72h congestion projection for a port. Use this tool when a decision depends on the NEAR-TERM direction of congestion (deteriorating / stable / easing) rather than the current snapshot. Complements get_port_risk. This is a SYNTHETIC projection, not a live forecast. Args: port_id: UN/LOCODE of the port, e.g. "BRSSZ" (Santos), "BRPNG" (Paranaguá).
    ConnectorNo auth