Skip to main content
Glama
465,565 tools. Updated 2026-08-19 04:29

"Code intelligence tools for LLMs to understand codebase structure and locate functionality" matching MCP tools:

  • Run an OWASP-oriented security pass over a source file. PREMIUM (license). Checks injection sinks, auth/session handling, crypto misuse, SSRF/deserialization, and unsafe file/path handling — each finding cites the line, the OWASP risk class, and a concrete fix direction. Typical input {"code": "<file contents>"} returns {"issues": N, "findings": [{"line": N, "class": "A03 Injection", "fix": "...", "code": "..."}], "owasp_note": "..."}. Use on one source file when vulnerabilities are the question. Not for style or structure (complexity_report), and never a substitute for a security professional on high-risk code. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    Connector
  • Expert developer playbooks — not your repo. Stripe webhooks & checkout, Supabase RLS, Next.js auth (clerk, next-auth), payment flows, CSP/HSTS, deploy patterns. operation=search finds entries by question; operation=get returns full guidance by slug from search. Read summary and checklist first. 2 credits hosted. No project path. Call when standard patterns beat guessing — wiring stripe checkout, fixing auth middleware, Supabase RLS policies, hardening after audit_headers. Use AFTER repo tools if code context is still thin. NOT for user's codebase (get_project_context, find_code, read_code), registry packages (check_package), tests (check_test), live URL (audit_headers), or saving decisions (project_memory). Example: Zephex_dev_info({ operation: 'search', query: 'Stripe webhook raw body verification', category: 'payments' }) then get with returned slug. Read-only.
    Connector
  • Publish one public Markdown text post as a selected agent owned by the signed-in human operator. Use list_my_agents first to obtain the agent ID. Use the dedicated code tools for code requests and reviews; App and Cabana posts are not available through this connector release. Call only after the user explicitly confirms the exact title, body, tags, agent, and optional karma reward.
    Connector
  • Deterministic structure/checksum validation of an EU VAT number (incl. the Belgian modulo-97 checksum) with the normalized identifier and a stable issue code. Format plausibility only — not a live VIES result. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.
    Connector
  • Switch Vision — watch and understand a video (or image) like a human and answer a question about it: scenes, subjects, actions, on-screen text, pacing, mood and sentiment. Pass video_url (a public https video URL, including YouTube) OR one of your own Switch videos (a video/asset id from list_my_videos / list_my_assets / upload_media). Add an optional question to focus the analysis (e.g. "what is the tone and energy?", "list the cuts and what each shot shows"). Use this whenever the user gives you a reference video and wants its style, energy, structure or content understood — for example before making a new video that matches it.
    Connector
  • Get regulatory obligations - specific requirements extracted from regulations. Each obligation includes the requirement text, applicable article reference, deadline, which entity types it applies to, actor roles, and current status. Results are paginated (max 50 per page). Supports keyword search via the query parameter (trigram + ILIKE matching on obligation text). Combine with regulation, entity_type, and actor_role filters for precise results. Set canonical=True to get deduplicated canonical obligations with enforcement intelligence instead. Canonical obligations return one entry per unique legal requirement per actor role, with compliance difficulty and enforcement metrics. Use get_actor_roles first to discover available actor roles per regulation. Args: entity_type: Filter by entity type code (e.g. 'credit_institution', 'payment_institution'). regulation: Filter by regulation code (e.g. 'dora', 'mica', 'aml'). status: Filter by status: 'upcoming', 'active', 'overdue', or 'expired'. query: Keyword search on obligation text (e.g. 'ICT risk', 'strong customer authentication'). actor_role: Comma-separated actor roles to filter by (e.g. 'credit_institution,significant_institution'). Use get_actor_roles to see available roles. canonical: If True, return deduplicated canonical obligations with enforcement intelligence instead of raw obligations. page: Page number (default 1). per_page: Results per page (default 20, max 50).
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Search ClinicalTrials.gov for clinical trials — find trials and look up a NAMED trial by keyword, condition, drug/therapy, status (e.g. 'Recruiting'), or phase (e.g. 'Phase 2'). Use for "clinical trials for <disease/drug>", or to locate a specific study like "the FLOW trial", "semaglutide kidney outcomes trial" (use ct_get_study for its full design/results). Returns NCT IDs, titles, status, enrollment, and sponsor info.
    Connector
  • Validate a single International Bank Account Number (IBAN) against the official ISO 13616 structure for its country. What it checks: the country code, total length for that country, the national BBAN structure, and the MOD-97 check digits. When the bank/branch code maps to a known institution, the response also includes the bank name, BIC/SWIFT code, and country. Returns JSON with fields such as `valid` (boolean), `countryCode`, `checkDigitsValid`, the `formatted` IBAN, and an optional `bank` object. On a malformed input the call still succeeds with `valid: false` and a `reason` (e.g. INVALID_FORMAT, INVALID_CHECKSUM); it does not throw for invalid IBANs. Use this when you have one account number to verify. For many IBANs prefer `validate_bulk_ibans`; to pull IBANs out of prose use `extract_ibans_from_text` first. No account data is stored; validation runs in memory and is discarded.
    Connector
  • START HERE — Returns the complete Stratalize tool catalog: governed MCP tools across finance, healthcare, governance, real estate, crypto, and intelligence. Available via public MCP (no auth) or x402 micropayments on Base ($0.02 atomic · $0.10 benchmark · $0.50 synthesis · $1.00 premium · $3.00 outcome pack). Org intelligence, agent governance, and role briefs require OAuth. Call this first to discover tools by role or vertical.
    Connector
  • START HERE — Returns the complete Stratalize tool catalog: governed MCP tools across finance, healthcare, governance, real estate, crypto, and intelligence. Available via public MCP (no auth) or x402 micropayments on Base ($0.02 atomic · $0.10 benchmark · $0.50 synthesis · $1.00 premium · $3.00 outcome pack). Org intelligence, agent governance, and role briefs require OAuth. Call this first to discover tools by role or vertical.
    Connector
  • CRITICAL STARTING POINT. Returns high-level game mechanics, survival timers, and economic parameters. Use this to understand how to win and avoid penalties.
    Connector
  • START HERE — Returns the complete Stratalize tool catalog: governed MCP tools across finance, healthcare, governance, real estate, crypto, and intelligence. Available via public MCP (no auth) or x402 micropayments on Base ($0.02 atomic · $0.10 benchmark · $0.50 synthesis · $1.00 premium · $3.00 outcome pack). Org intelligence, agent governance, and role briefs require OAuth. Call this first to discover tools by role or vertical.
    Connector
  • Provides explanatory text for STRING features and limitations. Use this tool when the user question involves: - What is STRING is or how to use the tool (how_to_use_string, cytoscape) - functionality not available via MCP tools (e.g. GSEA, regulatory networks, large datasets). - meaning of the lines in the network (line_colors)
    Connector
  • Free sample of the benchmark data shape for any supported commodity. Returns the full field hierarchy with real field names, units, string labels, and nested structure — but all numeric values are replaced with '<number: paid>'. Use this to understand exactly what fields you will receive from the paid benchmark.commodity endpoint before spending $0.10 USDC. Includes provenance fields (attestation_uid, source_cid, result_cid) and the paid REST endpoint URL.
    Connector
  • Get a summary of insider ownership for a stock, ranked by shares held. Shares Owned is each insider's actual-share (non-derivative) position — options and other derivative holdings are excluded. Each row is as-of the last line of that insider's most recent SEC Form 3/4/5 filing (former insiders may linger with stale dates or zero shares), and share counts are restated onto today's split basis, so they can differ from the raw figures in older filings. Returns at most maxResults insiders (default 30). Use this to understand the insider ownership structure of a company; use GetInsiderTransactions for the underlying trades.
    Connector
  • Get pre-built template schemas for common use cases. ⭐ USE THIS FIRST when creating a new project! Templates show the CORRECT schema format with: proper FLAT structure (no 'fields' nesting), every field has a 'type' property, foreign key relationships configured correctly, best practices for field naming and types. Available templates: E-commerce (products, orders, customers), Team collaboration (projects, tasks, users), General purpose templates. You can use these templates directly with create_project or modify them for your needs. TIP: Study these templates to understand the correct schema format before creating custom schemas.
    Connector
  • Get Lenny Zeltser's expert writing guidelines for security reports and assessments. Provides guidance on tone, structure, clarity, executive summaries, and avoiding common writing mistakes. Includes rating-sheet items (the four lens sheets: structure, look, words, tone) as concrete reference points for grounded feedback. Works for any security document. This server never requests your documents and instructs your AI to keep them local—guidelines flow to your AI for local analysis. Note: For incident response reports specifically, use the ir_* tools which provide deeper section-by-section review criteria.
    Connector
  • The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
    Connector
  • Verify the 6-digit code sent to the patient's email. Returns a guest-scope bearer token for intake, consent, order, and checkout tools. Requires the session_id from auth_start — no email needed. After checkout and payment, call auth_check_payment to upgrade the token to full scope for portal access.
    Connector
  • Returns available evaluation tools, what they check, and their pricing. Call this first to understand what Axcess can evaluate and how much each evaluation costs. This tool is FREE. All evaluation tools require USDC payment on Base network. Returns: JSON with tool descriptions, pricing, and rubric categories.
    Connector