Skip to main content
Glama
670,106 tools. Updated 2026-10-17 14:14

"A server for finding code debugging tips and techniques" matching MCP tools:

  • Look up a NUCC provider taxonomy code (the specialty codes used on HIPAA transactions + NPI registrations) or search by keyword. Returns classification + type + optional specialization. Source: NUCC Health Care Provider Taxonomy Code Set (public; CMS-accepted). WHEN TO USE: Resolving a NUCC provider taxonomy code to its specialty description. WHEN NOT: For finding a provider by specialty in a region (not yet implemented).
    ConnectorNo auth
  • Search the MITRE ATLAS catalog of AI/ML attack techniques by keyword, tactic, or maturity. Default response is SLIM (description truncated to 240 chars per row); pass include='full' for the verbose record. Pass exclude_id when chaining from atlas_technique_lookup to skip self in sibling-tactic searches. Use this to discover techniques matching a threat-model question, e.g. 'what techniques target LLM serving infrastructure?'. Drill into atlas_technique_lookup with any returned technique_id for the full description, ATT&CK bridge, and pivot hints. For broader cross-referencing: when a result has attack_reference_id, that bridges to D3FEND mitigations via d3fend_defense_for_attack. Free: 30/hr, Pro: 500/hr. Returns {query (echoed filters), total, results [{technique_id, name, description (truncated by default), tactics, inherited_tactics, maturity, attack_reference_id, subtechnique_of}], next_calls}.
    ConnectorNo auth
  • Best for: "will this Shopify CSV import?" or "what is wrong with my product file?". Checks the file against the Shopify import rules: required columns, handles, options, duplicate variants, prices, statuses, image URLs and barcodes a spreadsheet mangled. Returns: blocking findings (Shopify rejects them or imports them wrong) and warnings, up to 200 each, every one with row, handle, rule and fix, plus totals. Input tips: send csv, the full file text from Shopify admin (Products > Export), header row first, up to 2 MB. A file with no recognisable header comes back as a missing-required-column finding, not an error. A larger file is refused with csv_too_large; split it by rows. Not for: GTIN or Merchant Center questions (use merchant_feed_check) or listing text (use listing_text_audit). It has no domain mode: it needs the file.
    ConnectorNo auth
  • Search the China Footnotes guide for sights and neighbourhoods a first-time foreign visitor might go to. Matches English or Chinese names, aliases, district, type and tags. Suited to questions about what to see or do in a covered city, and to finding a place's id from its name. Coverage today: Shanghai (50 places), Beijing (20 places), Xi’an (10 places), Chengdu (12 places), Chongqing (10 places), Hangzhou (10 places). Returns short summaries with ids and page links, best match first; matchedAll is false when no place matched the whole query and the results only share some words with it. Opening hours, tickets, booking and traveler tips come from get_place.
    ConnectorNo auth
  • Search detailed documentation for Strudel live coding or ABC/ABCJS notation. Returns relevant code examples and explanations from the official docs. Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need — for specific functions, advanced techniques, or when you're unsure about syntax. Powered by semantic search over strudel.cc and ABCJS docs.
    ConnectorNo auth
  • LLM CODE DEBUGGING — POST {code, error} and get a diagnosis: what is wrong, the root cause, and a concrete fix with corrected code. Paste the failing snippet plus the error message or stack trace; any language, up to 20,000 chars combined. Optional {language} and {context} ('happens only on the second call'). Fast cheap LLM under the hood. Want deterministic no-AI lint instead? POST /api/lint/:language ($0.002). ($0.01 per call, paid via x402)
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    A
    quality
    D
    maintenance
    Enables LLMs to automatically diagnose coding errors through codebase search, test execution, and live debugger integration (DAP/V8 CDP). Provides a secure, policy-gated environment for investigating failures while preventing destructive operations.
    9
    -
  • F
    license
    A
    quality
    D
    maintenance
    MCP server that exposes the OBBBA No Tax on Tips federal deduction logic as callable tools, enabling users to check eligibility and estimate tip deductions.
    4
    -

Matching MCP Connectors

  • Permit-verified ADU rentals, pre-approved plans and cited ADU rules for LA, San Diego, SF and NYC.

  • Corporate travel: search and book flights, hotels, rail and transfers, manage orders.

  • Lists the bills Beyond Payday's Save money page offers tips for, each with the tip set (`playbook`) matched to it: its label, a one-line summary and the tip titles. `source` says how the match was made — 'user' (the household chose it), 'rule' (a confident keyword match), 'ai' (saved AI match) or 'fallback' (the category's general tips). The tips are general, hand-written suggestions, not advice about this household's providers or contracts. Needs the Save money permission and bills access; a child account has neither unless the owner grants it, and then sees only bills assigned to it. For each bill's full details use beyondpayday_list_bills; to change a bill use beyondpayday_update_bill. Paginated: pass limit (1-100, default 25) and offset; the response carries total and nextOffset — keep calling until nextOffset is null before totaling. Figures are estimates from user-entered data — not tax, financial, investment, insurance, or legal advice.
    ConnectorOAuth
  • Best for: "what will import duty and VAT be on this?" for one item shipped to the UK or US from a known tariff line. Returns: duty (the general rate plus US chapter 99 extra duties when they match), VAT, US fees and total, all in the input currency, with each chapter 99 heading, rate and reason, the headings skipped, sources and date. complete is true only when every part was worked out; a rate that is not a plain percentage comes back as text with no amount. Input tips: hs_code is a full line (UK 10 digits, US 8 or 10), such as "6109100010"; copy the code field from bulk_hs_candidates and narrow a short code first. Send destination, goods_value and shipping in one currency. For the US also send origin (2 letters) and transport. Not for: the EUR 3 EU low-value duty (use eu_duty_estimate). For destination EU, duty rates are not looked up, so only VAT is calculated (send country).
    ConnectorNo auth
  • Bulk ATLAS technique lookup — retrieve full records for up to 50 techniques in a single request instead of N separate atlas_technique_lookup calls. Designed as the natural follow-up to atlas_case_study_lookup, whose techniques_used array can be passed directly. Each item is the same shape as atlas_technique_lookup, including parent-tactics inheritance for sub-techniques (inherited_tactics=true flag) and per-item next_calls (D3FEND bridge when attack_reference_id present, sibling-technique search by tactic, parent lookup for sub-techniques). Free: 30/hr (1 per item), Pro: 500/hr. Returns {results [{technique_id, status (ok|not_found|invalid_format), technique, error}], total, successful, failed, partial, summary}.
    ConnectorNo auth
  • Search Cyclesite's expert buying guides (24+ articles by cycling-journalism authors). Returns up to 3 matching guides with title, excerpt, difficulty, reading time, and URL. Use for educational queries that don't need live inventory. Example: 'how do I choose a bike size?', 'tips for buying a used e-bike'.
    ConnectorNo auth
  • Describe what's going wrong — your human's complaint, or a failure you notice in your own behavior — and get the matching techniques. Deterministic matching; if the description fits two problems it returns one clarifying question instead of guessing.
    ConnectorNo auth
  • Retrieve the complete markdown of one documentation article by the id returned from `search` (for example `en/claude-code/advanced-techniques/hooks-automation`). The text is returned in full; `metadata.gated` only reports whether the article sits behind the paywall on the web. An unknown id is an error — call `search` first.
    ConnectorNo auth
  • Maps a finding's `rule` value from analyze_install_script, check_maintainer_changes, or check_package_provenance to the matching human-authored incident-response playbook (the same content published at /docs/playbooks) and returns its concrete, ordered steps, severity tier, real-incident references, and prevention tips — not just a link. Pass the exact `rule` string(s) a prior finding already returned (batch up to 10 in one call to cover a whole findings array; duplicates resolving to the same playbook are deduplicated) or an `id` to look up a specific playbook by slug directly. Each matched rule also gets its own short situationNote explaining specifically what that rule caught — so a batch of several different rules landing on the same playbook does not read as identical, repeated boilerplate. An unrecognized rule or id is not an error — it comes back with matched:false and a note, since a low-severity or baseline-only finding (e.g. analyze_install_script's lifecycle-present) legitimately has no dedicated playbook.
    ConnectorNo auth
  • Maps a finding's `rule` value from analyze_install_script, check_maintainer_changes, or check_package_provenance to the matching human-authored incident-response playbook (the same content published at /docs/playbooks) and returns its concrete, ordered steps, severity tier, real-incident references, and prevention tips — not just a link. Pass the exact `rule` string(s) a prior finding already returned (batch up to 10 in one call to cover a whole findings array; duplicates resolving to the same playbook are deduplicated) or an `id` to look up a specific playbook by slug directly. Each matched rule also gets its own short situationNote explaining specifically what that rule caught — so a batch of several different rules landing on the same playbook does not read as identical, repeated boilerplate. An unrecognized rule or id is not an error — it comes back with matched:false and a note, since a low-severity or baseline-only finding (e.g. analyze_install_script's lifecycle-present) legitimately has no dedicated playbook.
    ConnectorNo auth
  • Get remediation advice for a single finding as GitHub-flavored markdown. When AI Assist is enabled and within budget this is a suggestion written for this exact finding; otherwise it falls back to the static guidance-library text and says so in 'source'. Unlike the other reads this one can spend AI budget, which is why it is a separate tool. Use this for advice on one finding; for the whole library use list_security_guidance. Requires project context.
    ConnectorAPI key
  • Retract support for a finding you authored, with a reason. Original content remains visible and labeled withdrawn. Identical retries are safe; this does not claim the finding is disproven.
    ConnectorNo auth
  • Find candidate tariff codes for products. Best for: "what HS code could this product use?" for up to 20 product titles, from the UK Trade Tariff and, if asked, the US Harmonized Tariff Schedule. Returns: up to 3 candidates per product and market with code, description and source. Every code is a candidate, not binding; a large list may be cut short and says so per product. Input tips: products (1 to 20) of {title, optional description}, such as {"products": [{"title": "ceramic coffee mug"}], "markets": ["UK"]}. markets is UK, US or both (default UK). Hand-off: to get a duty amount, copy a candidate's code into landed_cost_estimate hs_code. It needs a full line: 10 digits for the UK, 8 or 10 for the US. A shorter code must first be narrowed to a full line. Not for: a binding classification or a duty amount by itself.
    ConnectorNo auth
  • Describe the graph this server reads, without looking up any fact in it. Returns the snapshot id and creation time, the schema version with notable schema changes, the node labels (types), the relationship verbs, the contributing sources, and the path templates that graph_path accepts. When to call it: once at the start of a session, to learn the valid values for the label argument of graph_lookup, graph_search and graph_neighbors, the verb values for graph_neighbors and the template names for graph_path; and when you report a finding, to cite the snapshot id it came from. What it is not for: it returns no CVEs, techniques, groups or detections. Use graph_lookup to find those. It takes no arguments, only reads, and gives the same answer to every caller of a snapshot.
    ConnectorNo auth
  • Draft a formal EU261/UK261 compensation claim letter (subject, legal basis, amount, 14-day payment request, escalation notice) for the passenger to send themselves, plus sending tips. Nothing is sent. Use after check_compensation and pass its amount. Do NOT use to check eligibility; use check_compensation.
    ConnectorNo auth
  • Look up a MITRE ATLAS technique — the AI/ML adversarial attack catalog. ATLAS catalogues TTPs targeting machine learning systems: prompt injection, model evasion, training data poisoning, model theft, etc. Roughly 80% of ATLAS techniques are AI/ML-specific (no ATT&CK bridge); 20% mirror an enterprise ATT&CK technique via attack_reference_id — use that to pivot to D3FEND defenses (d3fend_defense_for_attack) and CVE search. Sub-techniques inherit `tactics` from the parent (inherited_tactics=true flag) when ATLAS upstream leaves them empty. Use this tool when the user asks about AI/ML threats, LLM red-teaming, or adversarial ML; for multiple techniques in one call (e.g. drilling into a case study's techniques_used), prefer bulk_atlas_technique_lookup. Returns 404 when the id is not in the synced ATLAS catalog. Free: 30/hr, Pro: 500/hr. Returns {technique_id, name, description, tactics, inherited_tactics, maturity (demonstrated|feasible|realized), attack_reference_id, attack_reference_url, subtechnique_of, created_date, modified_date, next_calls}.
    ConnectorNo auth
  • Explain what a numeric HTTP status code such as 404 or 429 means by returning its standard reason phrase and a short description for debugging or API responses. Use when: - What does HTTP status 404 mean? - Get the standard name and description for status code 429 - Explain an HTTP response code returned by an API Do not use when: - Decide whether a request succeeded without needing the status name - Look up MIME types or content-type headers (use mime_lookup) - Diagnose TLS, DNS, or network failures that are not HTTP status codes
    ConnectorNo auth