Skip to main content
Glama
472,070 tools. Updated 2026-08-24 00:43

"Understanding Sequential Thinking in Server Systems" matching MCP tools:

  • Diff two design systems from live URLs — the only URL-scoped design-token diff engine. Fetches both URLs in parallel, extracts their :root custom properties, and produces a structured diff across 8 dimensions: tokens added (in A not B), removed (in B not A), renamed (heuristic Levenshtein ≤ 2), value-changed (same name, different value), scale-stop-changed (spacing/radius/color scale steps), contrast-drift-per-pair (WCAG contrast ratio change for shared color tokens), structure-delta (token count + category distribution), and score-delta (runs /score on both URLs and diffs). Use this to answer "what actually changed between two design systems" or "how does our design system differ from a reference". When NOT to use: for single-site drift detection, use designesy_drift_score; for continuous monitoring, use designesy_monitor_score. Executable — fetches both URLs, extracts CSS + tokens, computes diff. No browser needed. Returns JSON: { ok, urlA, urlB, score (0-100, diff completeness), grade, pass, warn, fail, total, tokensA, tokensB, added[], removed[], renamed[], valueChanged[], scaleDiff, structureDelta, contrastDrift[], scoreDelta, checks[] }. Results cached ~24h per URL pair.
    Connector
  • Get payment system cutoff times for major clearing systems. Covers RTGS (T2 — formerly TARGET2, CHAPS, Fedwire, BOJ-NET, SIC), net settlement (CHIPS, BACS), SEPA schemes (SCT, SCT Inst, OCT Inst, SDD Core, SDD B2B), FX settlement (CLS, FXYCS), and other systems (CIPS, SPEI, FAST). For same-day EUR guidance: filter by currency="EUR" to retrieve all SEPA schemes plus T2 in one call — the scheme-level view is usually what treasurers need. Underlying CSMs (TIPS, RT1, EURO1, STEP2) are referenced in scheme notes. DST-observing systems also carry `season_now` and `operative_cutoff_today` fields computed for the current date. cutoff_utc/cutoff_local are the STANDARD-TIME (winter) values; summer_offset holds the DST value. Quote the cutoff that `operative_cutoff_today` points at for TODAY's season — do not default to the winter figure when DST is currently in force (e.g. the T2 customer cutoff is 15:00 UTC in summer, not the 16:00 UTC winter value). Args: system: System name (e.g., "T2", "TARGET2", "FEDWIRE", "CHAPS"). Case-insensitive. "TARGET2" and "T2" both resolve to the same entry (T2 is the post-March 2023 name). Omit to list all or filter by currency. currency: ISO 4217 currency code to filter by (e.g., "USD", "EUR"). Examples: payment_cutoff_times(system="T2") payment_cutoff_times(currency="EUR") payment_cutoff_times(currency="USD") payment_cutoff_times()
    Connector
  • Create a multi-agent sequential chain: stages validate in order against one Blueprint, repairs propagate forward, TTL bounds the run. Siblings: submit_chain_stage advances the chain; handoff_audit verifies a transition between stages. Returns chain_id.
    Connector
  • Get the wiki tag hierarchy with page counts per category. Useful for understanding what content exists, and for finding a valid tagPath before writing.
    Connector
  • Accessibility tree of the DESKTOP grid browser page (by pageId), as text — for finding elements and understanding layout. Not a device: the equivalent for a phone or tablet is webpage_snapshot (by udid).
    Connector
  • Return a dasha (planetary period) timeline as a nested tree anchored on a date — past, present and future in ONE call. Works for BOTH planetary (graha) and sign (rasi) dasha systems; just name the system and the tool routes it automatically. Every period node has the SAME shape: 'level' (maha/antar/pratyantar/sookshma), 'ruler' (planet for graha, sign for rasi), 'start', 'end' (YYYY-MM-DD) and 'relation' (past/current/future). The result has 'dasha_type' ('graha' or 'rasi'), 'system', 'as_of' (anchor date), 'depth', and: 'current' — a ready-made summary of the running period ('maha'/'antar'/'pratyantar', a 'path' string, and 'current_period_ends'); 'maha_timeline' — every Maha-dasha over the life; 'current_maha' with its 'antars'; for graha systems 'current_antar' with its 'pratyantars'; and, at depth 4, 'current_pratyantar' with its 'sookshmas'. Rasi systems have two levels (no pratyantar). To drill into a SPECIFIC period regardless of date, pass 'maha' (and optionally 'antar') as a ruler name — the matching branch comes back under 'selected_maha'/'selected_antar' with a 'selection' echo. HOW TO REQUEST: send only birth details for the default (vimsottari, anchored today, depth 3). Optionally set 'system' to EXACTLY one enum token. Planetary (graha) systems: vimsottari (standard 120-yr), ashtottari, yogini, shodasottari, dwadasottari, panchottari, satabdika, chaturaaseeti_sama, shashtisama, shattrimsa_sama, dwisatpathi, kaala, buddhi_gathi, naisargika, aayu, tara, karaka, tithi_ashtottari, tithi_yogini, karana_chaturaaseeti_sama, saptharishi_nakshathra, rasi_bhukthi_vimsottari, yoga_vimsottari, ashtaka_varga_planet, ashtaka_varga_sign, ashtaka_varga_pinda, moola_graha, rashmi. Sign (rasi) systems: narayana, chara, kendraadhi_rasi, sudasa, drig, nirayana, shoola, kendraadhi_karaka, lagnamsaka, padhanadhamsa, mandooka, sthira, tara_lagna, brahma, varnada, yogardha, navamsa, paryaaya, trikona, kalachakra, chakra, sandhya_panchaka, chathurvidha_utthara, karaka_kendraadhi, lagna_kendraadhi, niryaana, raashiyanka. Optionally set 'as_of_date' (YYYY-MM-DD, separate from birth 'date') to anchor on another time, e.g. '2030-01-01'. Data only — no interpretation.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Find relevant Smart‑Thinking memories fast. Fetch full entries by ID to get complete context. Spee…

  • ifsc-in MCP — Indian bank branch IFSC code lookup via Razorpay's open

  • Change the session type or the brief on an existing booking — what the buyer wants to discuss, what they want out of it, or the background they want read first. Use this when the buyer refines their thinking after booking, which is common: people work out the real question after the date is in the diary. Only the fields you pass are changed. This does not move the meeting — use reschedule_booking for that.
    Connector
  • Point-in-time ranking records for SPECIFIC players: per system, the newest record in force ON OR BEFORE as_of — never one dated after it. Every other ranking field in this API is the CURRENT value joined at read time; this is the historical answer. Systems are never collapsed: ATP/WTA and the ITF circuits carry rank+points, UTR a rating. ITF and UTR history begins 2026-07-29. Requires the ULTRA plan.
    Connector
  • Returns every distinct code_type (e.g. CPT, MS-DRG) with catalogued cost data, along with each type's distinct code count and total hospital reports. Unpaginated. Use this to discover which code systems have data before drilling into list_codes.
    Connector
  • Fetch a public business website page and return structured, accessible facts for a buyer-readiness review. It only examines the supplied public URL and does not scrape review platforms or private systems.
    Connector
  • Upload a file to the Compoid MCP server. Accepts a data URI (data:<mime>;base64,<data>). Returns the server-side path to use as file_upload in Compoid_create_record or Compoid_update_record.
    Connector
  • Convert a grade from any of 13 African grading systems to the international 4.0 GPA scale used by scholarship applications worldwide. Covers all 54 African countries. Also returns the grade class (e.g. 'First Class Honors') and how the GPA is interpreted in Germany, UK, France, USA/Canada, Australia, Netherlands, and Japan/Korea/China.
    Connector
  • Calculate recommended RAM and ARC sizing for a ZFS storage pool based on workload type, pool size, deduplication status, and L2ARC cache size. Computes minimum and recommended RAM in gigabytes, ARC target size, and dedup table overhead. Accounts for workload-specific IO patterns: NAS (sequential, 1GB/TB), database (random, 2GB/TB), virtualization (mixed, 1.5GB/TB). Deduplication adds approximately 5GB per TB for the DDT. L2ARC index requires 1GB RAM per 10GB of L2ARC. Essential for TrueNAS, FreeNAS, and custom ZFS server builds.
    Connector
  • The eight thinking-failure problems ContextOverflow covers, phrased the way a human experiences them. Start here to see what exists.
    Connector
  • Submit system intel to your faction's shared map (Submit intel in the same JSON format as game responses. Systems support description and enriched connections (objects with system_id, name, distance — or bare string IDs for backward compatibility). POIs support description, class, position, and base_name. Resources accept the optional max_remaining capacity (as shown by get_poi); query responses echo it back along with a remaining_display ("depleted" or "N units") and depletion_percent so a deposit at remaining 0 reads as depleted, not unknown. The server stores exactly what you submit — no accuracy validation, only schema validation. Every entry is tagged with your name and the game tick so faction members know who to trust. Does not require docking. Requires a faction_intel facility at any base.)
    Connector
  • Return the canonical list of 26 ancient divination systems Mythsensus implements (slug, English + Thai name, region, required inputs). Use first when asked "what systems do you support?".
    Connector
  • Returns a list of all available product knowledge categories, each with a short description. Categories represent the main pillars of Product Thinking – Foundation, Sense, Focus, Discovery, and Delivery. Each category provides structured resources for product owners, designers, and teams, covering groundwork, user research, opportunity analysis, validation, and agile delivery. Use this tool to guide users to the right area for their current product challenge.
    Connector
  • Propose a new/updated Idea note → Inbox. Title-match to update; send the COMPLETE revised text. Set resync:true ONLY when you rewrote the note FROM the current systems (get_stale lists notes the systems have moved past) — it stops the adopted note from immediately nagging to re-generate the systems it was just written from.
    Connector
  • Returns the complete Trident 2D specification including grammar, syntax rules, coordinate system, containers, nodes, connections, shapes, and icon reference. Use this when you need deep understanding of the Trident DSL.
    Connector
  • Score an entire counterparty portfolio in one call (up to 200 entities by LEI or name). Returns portfolio-level composite E/S/G scores, tier distribution, aggregate fee surcharge impact in basis points, worst offenders (bottom 10% by composite), top performers, MiCA Article 72 ongoing monitoring status, and SFDR PAI flags. The canonical pre-settlement compliance check for treasury systems and TMS integrations.
    Connector