Skip to main content
Glama
650,553 tools. Updated 2026-10-14 10:52

"A debugger for reverse engineering and software analysis" matching MCP tools:

  • Run a deliverability/content analysis on a raw RFC 822 email (.eml source: full headers + body). IMPORTANT LIMITS: with no live SMTP session, SPF, blacklist and reverse-DNS cannot be verified from a file - for the authoritative score use create_mailtest instead.
    ConnectorNo auth
  • Technology assets: developed technology under life-cycle risk, software under cost and income, data assets with a quality adjustment, and platforms with network effects. Method selects the formula. Use for developed technology, software, data, and platform intangibles; developed_technology and software blend cost and income evidence. For patents, trademarks, copyrights, and trade secrets use valuation_ip; for customer relationships use valuation_customer. Per method: developed_technology needs rd_costs + life_cycle_stage + competitive_advantage + discount_rate + cash_flow_projections; software needs development_cost + maintenance_cost + user_base + revenue_model + useful_life + discount_rate; data_asset needs acquisition_cost + quality_score + revenue_contribution + useful_life + discount_rate; platform needs network_size + network_effects_coefficient + revenue_per_user + growth_rate + discount_rate. cash_flow_projections for developed_technology run over the remaining useful life. Only method is required; all other parameters are method-dependent — supply those the selected method names and omit the rest (defaults apply where defined). Rates and premiums are decimals (0.10 = 10%). Pure arithmetic: no I/O and no external calls, rounded to 2 decimals; parameters belonging to other methods are accepted and ignored. An unknown method, or a missing method-required parameter, returns an error instead of a value.
    ConnectorNo auth
  • Get Lenny Zeltser's malware analysis report template. The report covers Executive Summary, Sample Snapshot, Malware Family Identification, Component Inventory, Runtime Requirements, Sources, Capabilities, Indicators of Compromise, Analysis Details, What We Don't Know, optional Infection Vector, optional Detection Engineering, About this Report, Appendix: Analysis Environment, and optional Appendix: Analysis Scripts. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI for local analysis.
    ConnectorNo auth
  • Multi-hop traversal from a claim over typed relation edges of ONE class. Default walks the epistemic §7 edges transitively (every relation value in the §7 enum — support/extend/qualify/refute/background/shared_evidence/same_as/addresses/causes); relation_class="engineering" walks the dependency graph (depends_on/satisfies). ★ An empty `reached` carries `empty_reason` — not_a_claim_id | anchor_not_found | subtype_not_in_class | other_direction_only | class_mismatch | no_edges — because "nothing here" and "you looked in the wrong place" are different findings and used to come back identical. ★ Those are the values a record carries; the graph stores them as ENG_DEPENDS_ON/ENG_SATISFIES edges, which you never write. This sentence used to name the epistemic set by its RECORD values and the engineering set by its EDGE LABELS, so a reader applying the visible pattern produced `ENG_depends_on` — a third thing, rejected by the validator (which accepts exactly depends_on and satisfies). direction="out" = forward (dependencies / cited); "in" = reverse (impact set — who depends on this). ★ This `direction` is the TRAVERSAL direction of the read and has NOTHING to do with the `direction` FIELD on a relation record — different thing, same name. Do not copy in/out into a record. For engineering it also returns cycle_detected (start claim in a dependency cycle). Class label-spaces are disjoint — a §7 walk never crosses into engineering edges and vice versa. ★ A0-3b: every reached node carries is_superseded. The walk goes THROUGH superseded claims deliberately — a superseded claim is a real historical link, and refusing to traverse it would silently drop CURRENT claims lying behind it. There is no latest_only here on purpose: filter the stamped result yourself if you want only current heads. ★ `edges` — the walked edges themselves, each with the properties it carries (relation_id, relation, direction, is_superseded, link_strength = the verifier's, grounding = the author's, correction) — only the keys present; an edge written before 2026-09-16 carries relation_id alone, so read its record by id for the rest. `edge_summary` counts how many edges carry link_strength / grounding, so a PSnd over the edge set knows its denominator.
    ConnectorAPI key
  • Get full detail for a Tuki solution: description, who it is for, capabilities, status and contact / CTA. Use after `list_solutions` or when the user asks about a specific Tuki product (WhatsApp Booking OS, boutique ticketing, rental inventory software, event post-sale, tailor-made tourism software).
    ConnectorNo auth
  • Laurent Knauss' technical skills, grouped by domain (Agentic AI, RAG & Voice AI, Software engineering & Cloud, Automation & tooling). Each skill has a label and an optional short detail. Use this to assess fit for AI/agentic development roles.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • 27 engineering compliance and calculation tools for the built environment (UK, EU, UAE).

  • Agent Replay Debugger MCP — record every agent step + deterministic replay. Step-debugger for

  • Read a compact bootstrap of every product skill URL and invoke prefix — not Software-tab cards and not the hashed registry. Use this when a client needs skill URLs in one shot. Do not use it for Software-tab refresh, hashed registry discovery, or exec; use Softwares, fraggate_list, or fraggate_call instead. Prefer GET /v1/software for hub Software tabs. This helper is URL bootstrap only. Returns compact product list with skill URLs.
    ConnectorNo auth
  • Read a compact bootstrap of every product skill URL and invoke prefix — not Software-tab cards and not the hashed registry. Use this when a client needs skill URLs in one shot. Do not use it for Software-tab refresh, hashed registry discovery, or exec; use Softwares, fraggate_list, or fraggate_call instead. Prefer GET /v1/software for hub Software tabs. This helper is URL bootstrap only. Returns compact product list with skill URLs.
    ConnectorNo auth
  • Find which guidance serves a FinOps question - how to commit, size, allocate, charge back, forecast, or govern cloud and AI spend. Use this for questions like "how should we size Savings Plans", "what should Finance own in chargeback", "what does a Crawl-stage org tackle first" - anything that maps to FinOps Framework facets (domain, capability, phase, persona, maturity) - and you want only the references that serve it, instead of scanning the full list. All filters are optional and combine with AND semantics. String matching is case-insensitive and exact (not substring). Examples: - ``find_references(domain="Optimize Usage & Cost")`` - ``find_references(phase="Optimize", persona="Engineering")`` - ``find_references(persona="Engineering", persona_primary_only=True)`` - ``find_references(capability="Rate Optimization")`` - ``find_references(maturity="Crawl")`` Args: domain: FinOps Framework domain (e.g. ``"Optimize Usage & Cost"``, ``"Quantify Business Value"``, ``"Manage the FinOps Practice"``). capability: FinOps capability (matches ``fcp_capability`` and ``fcp_capabilities_secondary``). phase: FinOps phase (``"Inform"``, ``"Optimize"``, ``"Operate"``). persona: Persona (matches ``fcp_personas_primary`` and ``fcp_personas_collaborating``). maturity: Entry maturity level (``"Crawl"``, ``"Walk"``, ``"Run"``). persona_primary_only: when True, ``persona`` matches only the primary list. Use it when the default match barely narrows the set - broad personas like Engineering collaborate on nearly every file, so filtering on collaboration is descriptive, not discriminating. ``persona="Engineering", persona_primary_only=True`` is the engineering reading list; the default is the everything-they-touch view. Returns ``{"filters": {...}, "references": [...], "total": N}``. A query that matches nothing also returns `hint` and `valid_values`, so a typo is distinguishable from a genuine gap in coverage.
    ConnectorNo auth
  • Get all notes for your account. Notes are automatically decrypted and returned in reverse chronological order. Use them internally for tool chaining but present only human-readable information (titles, content, dates). # fetch_notes ## When to use Get all notes for your account. Notes are automatically decrypted and returned in reverse chronological order. Use them internally for tool chaining but present only human-readable information (titles, content, dates).
    ConnectorNo auth
  • Canonical software product facts with sources — pricing, features, integrations, platform, and limits, where every fact carries a source URL and a last-verified date. Use to verify software claims (e.g. current pricing) or to gather grounded data before recommending or comparing tools. Accepts a product name or domain (e.g. "hubspot.com").
    ConnectorNo auth
  • Convert any number to scientific notation and engineering notation. Returns the coefficient, exponent, a formatted string with Unicode superscripts (e.g. '3.14 × 10²'), and engineering notation where the exponent is a multiple of 3. Useful for expressing very large or very small values compactly, common in physics, electronics (picofarads, gigahertz), and astronomy. Accepts output from sig_figs and log_calc for precision-aware formatting.
    ConnectorNo auth
  • List the accounts that follow a given X user, identified by @handle, newest follower first. Returns up to 200 per page by default with `has_next_page` and `next_cursor`; each entry is a full user object (handle, name, bio, follower count, verification). Use this for audience analysis, mapping a competitor's follower base, or finding influential followers. For the reverse direction (who this user follows) use `get_twitter_user_followings`. For only the verified subset use `get_twitter_user_verified_followers` — note that one takes a numeric `user_id`, not a handle.
    ConnectorOAuth
  • List the accounts that follow a given X user, identified by @handle, newest follower first. Returns up to 200 per page by default with `has_next_page` and `next_cursor`; each entry is a full user object (handle, name, bio, follower count, verification). Use this for audience analysis, mapping a competitor's follower base, or finding influential followers. For the reverse direction (who this user follows) use `get_twitter_user_followings`. For only the verified subset use `get_twitter_user_verified_followers` — note that one takes a numeric `user_id`, not a handle.
    ConnectorOAuth
  • List the accounts that follow a given X user, identified by @handle, newest follower first. Returns up to 200 per page by default with `has_next_page` and `next_cursor`; each entry is a full user object (handle, name, bio, follower count, verification). Use this for audience analysis, mapping a competitor's follower base, or finding influential followers. For the reverse direction (who this user follows) use `get_twitter_user_followings`. For only the verified subset use `get_twitter_user_verified_followers` — note that one takes a numeric `user_id`, not a handle.
    ConnectorOAuth
  • Search 40M+ items in the Internet Archive — books, movies, audio, software, images, and archived web pages. Filter by mediatype (texts/movies/audio/software/image/data/web) and creator. Returns identifier, title, creator, date, and description for each match (Internet Archive advancedsearch.php)
    ConnectorNo auth
  • Retrieve a full knowledge entry by domain and slug. Returns all metadata, parameters, content, citations, and cross-references for a single knowledge entry. Args: domain: The engineering domain (e.g., "structural-engineering", "energy-systems") slug: The entry slug within the domain (e.g., "superstructure/primary-geometry")
    ConnectorNo auth
  • Get all entries that reference or are referenced by a given entry. Given an entry ID (e.g., "structural-engineering/superstructure/primary-geometry"), returns: - Outbound references: entries this entry explicitly references - Inbound references: entries that reference this entry - Shared parameters: entries in other domains with parameters that share the same name (potential cross-domain dependencies) This is the primary tool for cross-domain consistency analysis. Args: entry_id: The full entry ID (domain/subdomain/slug format)
    ConnectorNo auth
  • Compare software/tools side by side — a fact-by-fact comparison of two products (pricing, features, integrations, limits) with source URLs and verified dates for every claim. Use for "X vs Y" software comparison questions. Accepts product names or domains; pair order does not matter.
    ConnectorNo auth
  • Get stock split history for a company including forward and reverse splits with dates, ratios, type classification, and cumulative 2-year reverse split ratio. Relevant for NASDAQ/NYSE minimum bid-price compliance (1:250 cumulative reverse-split cap). IMPORTANT: `cumulativeReverseSplitRatio2yr` is null when it CANNOT BE STATED, which is NOT the same as no reverse splits — read `cumulativeWithheldReason` to tell them apart. `unconfirmed_splits_in_window` means at least one in-window reverse split is evidenced by only one source, so no cumulative is defensible: the confirmed splits alone would understate it, and understating a cumulative can put an issuer that breaches the 1:250 cap under it. Each row also carries `confirmed`; a `confirmed: false` split appears only in the announcement calendar, which retains every announcement and retracts none, so it is usually an amended or superseded announcement and occasionally a real split the effected-splits ledger missed. Both are returned. `ratioDisplay` and `type` are likewise null for a ratio whose exact factor cannot be determined.
    ConnectorNo auth