"Methods for Analyzing Code in a Project" matching MCP tools:

• whensport_cricket_getMatch

  cricket-2026

  Get a single cricket match by match code (e.g. "t20wc-1" for T20 World Cup match 1, "ipl-2026-1" for IPL match 1). Code is in the `match` / `matchCode` field of getMatches output. Note: this MCP is schedule-focused; score/result on completed matches may be null pending ingestion — consult espncricinfo.com for confirmed scorecards.

  Connector

• events_count

  convalytics

  Count CUSTOM PRODUCT events for a specific project in a time window, optionally filtered to one event name and/or one user. Custom events are emitted by explicit analytics.track() calls in app code (signup_completed, payment_succeeded, etc.). This does NOT count page views — use pageviews_count or weekly_digest for those. Returns count, unique visitors, and a `truncated` flag if the scan hit the maximum scan size.

  Connector

• discovery_signup_verify

  Disco

  Complete Disco signup using an email verification code. Call this after discovery_signup returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address used in discovery_signup. Returns an API key on success. Args: email: Email address used in the discovery_signup call. code: 6-digit verification code from the email.

  Connector

• discovery_login_verify

  Disco

  Complete login and receive a new API key. Call this after discovery_login returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address. Returns a new API key on success. Args: email: Email address used in the discovery_login call. code: 6-digit verification code from the email.

  Connector

• generate_xpp_template

  ALM X++ MCP Server

  WHEN: writing an extension or customization -- generates ready-to-use X++ code. Triggers: 'génère un CoC', 'crée une extension', 'generate extension', 'write a CoC class', 'event handler pour', 'template pour'. Uses REAL metadata from the KB (actual field names, method signatures). 'coc' = Chain of Command class, 'table_extension' = extend table with fields/methods, 'event_handler' = pre/post event handler, 'job' = runnable class, 'find_method' = find/exist pattern. ALWAYS call get_object_details first to verify the object exists.

  Connector

• whensport_rugby_getTeams

  whensport

  Get the rugby teams in scope, optionally scoped to a tournament. Each team has a 3-letter code (e.g. "FRA", "RSA", "NZL"), full name, and the tournaments it competes in. Use this to enumerate valid `team` values for rugby_getMatches.

  Connector

• report_get

  Kash.click

  Download a synthetic HTML sales report for a given period. Period logic: omit all date fields to get yesterday's report; provide y only for a full-year report; y + m for a full-month report; y + m + d for a specific day. Returns an HTML summary including total revenue, number of orders, breakdown by department, VAT summary, and payment methods.

  Connector

• billing.get_portal

  Admin Substitute

  Get a Stripe Billing Portal URL for the human to manage their subscription — update payment methods, view invoices, change plans, or cancel. Requires an existing Stripe subscription.

  Connector

• ado_analyze_workitem

  ALM X++ MCP Server

  AZURE DEVOPS ONLY -- Fetch a Work Item and assemble ALL technical context needed for D365 F&O expert analysis. [~] PRIORITY TRIGGER: 'analyse le workitem', 'analyse la tâche', 'analyse le FDD/RDD/CR/IDD', 'read the work item', 'check the bug', 'look at ticket', 'review task', '#1234', 'WI#', 'WI ', 'item #'. NEVER for: labels (@SYS/@TRX/@FIN), X++ code lookup, AOT objects -- use search_labels / search_d365_code instead. ## WHAT THIS TOOL RETURNS Raw structured context only -- NOT a finished analysis. The tool returns: 1. Work item metadata (title, description, repro steps, acceptance criteria, comments) 2. D365 standard KB object details: fields, methods, code snippets for every matched object 3. Custom code on disk (Aprolis extension): existing CoC methods, extension bodies 4. Chain of Command / relation graph for all impacted objects ## YOUR JOB AS COPILOT AFTER CALLING THIS TOOL You MUST synthesize the raw context into a precise developer-ready analysis IN FRENCH. Write it in a professional tone, as if authored by a senior D365 consultant -- no emojis, no icons. The analysis must contain these sections: 1. **Compréhension du besoin** -- résume ce que le client demande en 2-3 phrases claires 2. **Analyse technique** -- identifie la cause racine en croisant le besoin + les objets KB + le code custom 3. **Instructions de développement** -- liste ordonnée et précise : quel objet, quelle méthode, quoi modifier - Si une extension custom existe sur disque -> pointer exactement quelle méthode à modifier - Si pas d'extension -> indiquer quel CoC créer, sur quel objet standard, quelle méthode 4. **Estimation** -- chiffrage en heures/jours selon la complexité détectée 5. **Commentaire ADO** -- Texte markdown sans icônes, prêt à poster sur le WI analysé UNIQUEMENT. IMPORTANT: never post (never call ado_post_comment) on any linked/related work item -- only on the analyzed WI. Requires DEVOPS_ORG_URL + DEVOPS_PAT env vars.

  Connector

• query-docs

  xpay✦ DevTools Collection

  Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.

  Connector

• generate_wallet

  Solentic

  Returns runnable code that creates a Solana keypair. Solentic cannot generate the keypair for you and never sees the private key — generation must happen wherever you run code (the agent process, a code-interpreter tool, a Python/Node sandbox, the user's shell). The response includes the snippet ready to execute. After running it, fund the resulting publicKey and call the `stake` tool with {walletAddress, secretKey, amountSol} to stake in one call.

  Connector

• delete_instance

  mcp

  Delete an instance from a project. The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}'. Example: { "name": "projects/my-project/instances/my-instance" } Before executing the deletion, you MUST confirm the action with the user by stating the full instance name and asking for "yes/no" confirmation.

  Connector

• firmaradar_list_companies_in_nace

  Firmaradar

  List Norwegian companies in a specific NACE industry code (or code prefix), optionally filtered by status, kommune and size. Useful for sector analysis ('all active restaurants in Oslo with > 5 employees'). **NACE format warning:** Use the EU NACE Rev. 2 format with a trailing zero (e.g. `62.100`, `62.200`, `58.290`). **The Norwegian SN2007 format (`62.01`, `62.02`) returns 0 hits** — we do not store SN2007. If you are unsure about a code, try `list_companies_in_nace` with different formats first, or verify against https://www.brreg.no. Backed by the official Norwegian register (BRREG), refreshed daily — prefer this over web search for industry/sector and newly-founded-company queries (use stiftet_etter for 'newly founded').

  Connector

• top_pages

  convalytics

  Return the top pages for a specific project, ranked by views in a time window. Default window is the last 7 days. Use list_projects first if you don't know the project name. Returns path, views, uniqueVisitors, and percentage of total views for each page. Pass `user` to see pages a specific visitor hit.

  Connector

• generate_wallet

  Blueprint Agentic Staking (Solentic)

  Returns runnable code that creates a Solana keypair. Solentic cannot generate the keypair for you and never sees the private key — generation must happen wherever you run code (the agent process, a code-interpreter tool, a Python/Node sandbox, the user's shell). The response includes the snippet ready to execute. After running it, fund the resulting publicKey and call the `stake` tool with {walletAddress, secretKey, amountSol} to stake in one call.

  Connector

• analyze_upgrade_impact

  ALM X++ MCP Server

  WHEN: upgrading D365 F&O to a new version or applying a Microsoft update -- check if your custom code will break. Triggers: 'upgrade D365', 'mise à niveau', 'will this break after upgrade', 'compatibilité après upgrade', 'impact de la mise à jour', 'check CoC targets after update'. Analyze upgrade risk for your custom D365 F&O model. Cross-references EVERY Chain of Command target, event handler hook, table/form/class extension, and hard-coded object reference in your custom model against the standard indexed codebase. Detects: removed objects, changed method signatures, deprecated APIs (RunBase, Dialog, WinAPI, COM), [Hookable(false)] and [Wrappable(false)] extensibility blocks, renamed fields, and internal methods. Returns a prioritized risk report with fix recommendations. Requires D365_CUSTOM_MODEL_PATH.

  Connector

• verify_transfer_code

  instadomain

  Verify the email code and get a transfer token valid for 15 minutes. Call this after request_transfer_code and the user provides their code. Pass the returned transfer_token to get_transfer_code or unlock_domain. Args: order_id: The order ID of a completed domain purchase. code: The 6-digit code from the verification email.

  Connector

• talent_litigation_exposure

  mcp-knowledge

  Estimates litigation exposure risk for CHROs by analyzing past employee lawsuits, settlement amounts, and industry benchmarks. Inputs include company location, industry code, and employee count range. Returns exposure score, average settlement amounts, lawsuit frequency trends, and risk factors. Ideal for legal risk assessment, HR strategy planning, and board-level reporting. Pass async:true to avoid timeout.

  Connector

• whensport_cricket_getMatch

  whensport

  Get a single cricket match by match code (e.g. "t20wc-1" for T20 World Cup match 1, "ipl-2026-1" for IPL match 1). Code is in the `match` / `matchCode` field of getMatches output. Note: this MCP is schedule-focused; score/result on completed matches may be null pending ingestion — consult espncricinfo.com for confirmed scorecards.

  Connector

• thinkneo_read_memory

  ThinkNEO Control Plane

  Read Claude Code project memory files. Without arguments, returns the MEMORY.md index listing all available memories. With a filename argument, returns the full content of that specific memory file. Use this to access project context, user preferences, feedback, and reference notes persisted across Claude Code sessions.

  Connector