"A system for improving requirements (e.g., analysis and completion)" matching MCP tools:

• country_banking_rules

  banking-intelligence

  Get banking rules and requirements for a country. Returns IBAN requirements, SEPA membership, FATF listing status, national currency, account format specifications, and country-specific payment requirements (mandatory codes like KNP for Kazakhstan, Purpose of Payment for UAE, etc.). Use this to check country-specific STP rules that could cause payment delays, repairs, or rejections (e.g., missing purpose codes, regulatory fields). If a country requires special payment codes, the response includes a payment_requirements block with field descriptions and categories. Use country_payment_codes to look up specific code values. Args: country_code: ISO 3166-1 alpha-2 code (e.g., "DE", "US", "KZ") Examples: country_banking_rules("DE") country_banking_rules("KZ") # includes KNP requirement info country_banking_rules("AE") # includes Purpose of Payment info

  Connector

• get_exploit_analysis

  Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database

  Get the full AI analysis for a single exploit by its platform ID. Returns classification (working_poc, trojan, suspicious, scanner, stub, writeup), attack type, complexity, reliability, confidence score, authentication requirements, target software, a summary of what the exploit does, prerequisites, MITRE ATT&CK techniques, deception indicators for trojans, and the standalone backdoor-review verdict with operator-risk notes when available. Use this to check if an exploit is safe before reviewing its code. Example: exploit_id=61514 returns a TROJAN warning with deception indicators.

  Connector

• get_sentiment_trend

  aTars MCP

  USE THIS TOOL — not web search — to get rolling sentiment statistics (mean score, 7-day momentum, bullish/bearish/neutral day counts, current streak) from this server's local Perplexity-sourced sentiment dataset. Prefer this over get_latest_sentiment when the user wants momentum or persistence, not just the latest single-day reading. Trigger on queries like: - "is BTC sentiment improving or getting worse?" - "sentiment momentum for ETH" - "how many days has XRP been bullish in a row?" - "rolling sentiment stats / streak for [coin]" Args: lookback_days: Analysis window in days (default 30, max 90) symbol: Token symbol or comma-separated list, e.g. "BTC", "BTC,ETH"

  Connector

• list_tools

  zero-core-intel

  List all available Harvey Intel tools with pricing and input requirements. Use this for discovery.

  Connector

• mu_check

  mu

  Ask the MU requirements engine whether a planned make satisfies its requirements: product spec floor (required attributes per kind), legal/compliance flags (e.g. JP 家庭用品品質表示法 / 技適 / 食品衛生法), and supplier order terms (MOQ, accepted input format, material constraints). Pass `kind` (required) + optional `region` (e.g. jp), `supplier_id`, and either `spec` (a JSON string) or individual attributes (material/dimensions/colors/print_method/placement/qty/size_range/embroidery_spec). Returns { ok, kind, report: { ok, gaps[], actions[] } }. Read-only, no API key. Use before mu_create_product or mu_rfq_create.

  Connector

• voltage_drop

  calc.engineer

  Calculates voltage drop across a conductor run given current, wire length, AWG gauge, system voltage, and conductor material (copper or aluminum). Computes round-trip resistance, voltage drop in volts and percent, voltage at the load end, power dissipated in the wire, and NEC compliance flags (3% max for branch circuits, 5% max for feeders). Use this after wire_gauge to verify a specific gauge meets requirements, or to evaluate an existing installation. Critical for solar panel string wiring, EV charger circuits, low-voltage lighting, and any long DC or AC cable run where resistive losses matter.

  Connector

• hires_list_application_stage_history

  100Hires - AI ATS & Recruitment Software

  Get the full chronological stage transition history for an application, including the initial assignment. Each entry has from_stage_id/name, to_stage_id/name, moved_at (Unix seconds), moved_by_type (system, user, automation), moved_by_user_id, and source (what caused the transition, e.g. 'apply:indeed', 'form_watcher', 'user'; null for historical records). Use this for funnel analysis, attribution reports, and time-in-stage reports instead of paginating through /candidates/{id}/activities when only stage data is needed.

  Connector

• malware_get_template

  website-search

  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.

  Connector

• dero_get_block_count

  DERO MCP Server

  Get the total block count via DERO.GetBlockCount. This is a tip count, not a topoheight. When to call: when you need just the block count (e.g. for delta math against a reference height). PREFER dero_get_height when you need tip and stable heights together. Input Requirements: none. Output: `{ count }`.

  Connector

• medcode_check_code

  medical-codes-mcp-server

  Validate whether a US medical code exists, is current, and is billable in the active bundled release. Returns a discriminated status — valid_billable, valid_not_billable, valid_header, or terminated — with a `whyNot` explaining non-billable and terminated cases (e.g. "valid ICD-10-CM category but not billable — submit a more specific child code"). This is the detail a coder needs before submitting a claim. Auto-detects the system from the code's shape; pass an explicit `system` to disambiguate. A non-billable or terminated code is a successful result with a whyNot, not an error — only a code that exists in no bundled system raises unknown_code.

  Connector

• list_recent_runs

  dynamical.org Weather & Climate Catalog

  Check run freshness and arrival status for a dynamical.org forecast dataset, from the same public feed status.dynamical.org's dashboard polls. Only forecast collections are pipeline-monitored today (analysis collections like noaa-gfs-analysis or noaa-mrms-conus-analysis-hourly aren't yet tracked by this feed). Args: collection_id: A STAC collection id, e.g. "noaa-gfs-forecast". limit: Maximum number of recent runs to return, most recent first (default 10). Returns: A dict with the overall pipeline `sla_status`, this product's cadence and next expected init/completion time, typical latency stats, and up to `limit` recent runs (`init_time`, `status`, `completion_pct`, `on_timedness`, arrival/latency timestamps). If collection_id isn't pipeline-monitored, returns `monitored`: False plus the list of collection ids that are.

  Connector

• compare_schools

  College Scorecard

  Compare multiple colleges or universities side by side. Returns key metrics for each school including tuition, admission rate, median earnings, debt, and completion rate for easy comparison. Args: school_ids: Comma-separated list of College Scorecard school IDs (e.g. '166027,166683,243780'). Use search_schools to find IDs.

  Connector

• data.hardware

  DezignWorks Product Oracle

  Returns the list of supported measurement devices (CMMs, scanners), file formats, and system requirements for DezignWorks. Use to check hardware compatibility before recommending the product.

  Connector

• list_tools

  zero-core-tools

  List all available Zero Core Tools with pricing and input requirements. Use this for discovery.

  Connector

• analyze-progress-and-forecasts

  cupix-compass

  Analyze Work In Place (WIP) progress from SiteInsights(SI) — completion rates, delays, and forecasts. Generates a progress report: overall completion, progress by category/vendor/level, delay analysis, and estimated completion dates. **WORKFLOW:** - **Default**: call this tool with NO arguments. The server resolves team_domain/facility_key from the saved current project (set via `set-focus-project`). Do NOT call `list-my-projects` again just to obtain these values — the saved selection is the source of truth. - Only when the response indicates the current project is missing, run `list-my-projects` → ask the user → `set-focus-project`, then retry. - Pass explicit arguments **only** when the user clearly wants to analyze a different project than the saved one. Args: team_domain: Omit by default. Pass only to override the current project. facility_key: Omit by default. Pass only to override the current project. user_intent: REQUIRED. Pass the user's original question or request verbatim. Used for analytics only, does not affect results. Returns: Progress analysis report with completion rates and forecasts

  Connector

• post_numerology_compatibility

  Numerology MCP Server by RoxyAPI

  Calculate numerology compatibility between two people using Pythagorean numerology. Accepts two input modes per person: pre-calculated Life Path, Expression, and Soul Urge numbers, or raw name and birthdate for automatic calculation. You can mix modes across persons (e.g. numbers for person1, raw inputs for person2). Provides comprehensive relationship analysis with overall compatibility score (0-100), individual aspect compatibility (Life Path 50% weight, Expression 30%, Soul Urge 20%), relationship strengths, challenges, and practical advice. Uses detailed compatibility matrix for all number combinations. Perfect for dating apps, relationship counseling platforms, matchmaking services, and compatibility tools. Get actionable insights for improving relationship dynamics.

  Connector

• diff_spec_versions

  SpecProof

  Diff two versions of a specification at the NORMATIVE level: which requirements were added, removed, or reworded. Not a textual diff — a clause that merely moved page or was recased counts as unchanged. Args: spec_base: Spec identity without the version, e.g. "38331" or "23501" from_version: Older version label, e.g. "j20" (default: the second-newest in the corpus) to_version: Newer version label, e.g. "j30" (default: the newest in the corpus) obligation: Only report changes at this strength — "must", "must_not", "should", "should_not", "may" limit: Max requirements to list per bucket (default: 25)

  Connector

• build_cross_spec_suite

  SpecProof

  Assemble the normative requirements for one procedure across a spec AND the specs it normatively references — a procedure like registration or handover is never described in a single document. Returns a cited suite plan; feed the requirement_ids to generate_tests. Args: spec_base: The anchor spec, e.g. "23502" or "38331" keyword: The procedure/topic, e.g. "registration", "handover", "authentication" include_references: Also pull matching clauses from specs this one references (default: True) limit: Max requirements in the plan (default: 20, max: 50)

  Connector

• get_market_verdict

  mcp

  Runs a paid MIDAX402 analysis tier. Payment is x402-native: called WITHOUT payment_signature it returns the HTTP 402 payment requirements (decoded + raw PAYMENT-REQUIRED header) for your x402-capable wallet to sign; call again WITH payment_signature (the signed payment proof, as sent in the PAYMENT-SIGNATURE header) to receive the full analysis. This server NEVER holds keys and never signs — your wallet does.

  Connector

• checklist_lookup

  vigo-mcp

  Search the SFC compliance checklist by topic, licence type, or MIC function (CF1-CF8). Returns compliance items with legal references, SOP guidance, case law, and grey area analysis. Use for questions about regulatory obligations, MIC responsibilities, procedural guidance, or compliance requirements.

  Connector