Skip to main content
Glama
596,016 tools. Updated 2026-09-21 06:10

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

  • 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.
    ConnectorNo auth
  • Monte Carlo Schedule Risk Analysis — P10/P50/P80/P90 completion-date forecast for a Primavera P6 schedule. Implements an AACE-style quantitative SRA (the same math as CPP's browser Tool_11 Portfolio Risk Engine, scripted Python counterpart). For each iteration, every activity duration is sampled from the chosen distribution (Triangular, BetaPERT, Uniform, Lognormal, etc.) parameterized by % of baseline duration; CPM re-runs and the project finish date is recorded. After all iterations, P10/P50/P80/P90 completion dates and a sensitivity tornado (per-activity correlation to project finish) are reported. Use this tool when you need probabilistic completion forecasts or a tornado/sensitivity ranking. For the QRAMM-aligned five-level maturity badge (AACE 122R-22) on the result, pipe the response into ``qramm_maturity``. Args: xer_path: server-side path to the schedule XER. xer_content: full text of the schedule XER (alternative for hosted/remote use). Supply EXACTLY ONE of path/content. iterations: number of MC iterations (default 5000). distribution: 'Triangular', 'BetaPERT', 'Uniform', 'Lognormal' (case-insensitive — passed through). optimistic_pct, most_likely_pct, pessimistic_pct: % of baseline duration for the distribution params (defaults: 85 / 100 / 120). seed: optional fixed seed for reproducibility (0 = system entropy = non-reproducible). output_dir: optional output dir; tempdir if "". Returns: Full SRA result dict, key paths: - 'baseline.percentiles': lowercase p-keys {'p10','p25','p50','p75','p80','p85','p90','p95'}, each {'day', 'date'}. NOTE: keys are lowercase — read result['baseline']['percentiles']['p80'], not 'P80'. - 'baseline.config': sim params used - 'baseline.sensitivity': per-activity tornado rows - 'risk_register_simulation.percentiles' (only when a risk_register is supplied): SAME lowercase convention, {'p10','p50','p80','p90'} each {'day', 'date'}. - 'project_name', 'data_date', ... - HTML / DOCX paths if outputs emitted
    ConnectorNo auth
  • Create a social post on iHatePosting. action 'draft' saves it (the default, and the safe choice); 'schedule' needs scheduledDate (YYYY-MM-DD) + scheduledTime (e.g. '9:00 AM', in the account owner's timezone); 'now' publishes immediately to a real audience. Platforms with requirements — Pinterest a board, YouTube a title, TikTok and Instagram media — are set through `options` and `mediaIds`; call get_platform_rules for what each one needs, and validate_post to check before you commit.
    ConnectorNo auth
  • Processes sales invoices in a batch using reconciled product, VAT and Sales-analysis lines. Results are reported per submitted item and partial success is possible. Requires a valid routeToken issued for the matching action workflow. The token remains valid through lookup, preview and the permitted transaction. Placeholder tokens are invalid. A routeToken does not bypass preview or explicit-confirmation requirements. A call without confirmWrite: true returns confirmation_required and a payload preview. confirmWrite: true applies the previewed change after explicit confirmation. Passing preflight is not confirmation. Requires confirmCounterpartyExplicit: true; confirmation is scoped to the counterparty selected for the current preview.
    Connector
    Destructive
    No auth
  • Get 8-week progress for a specific exercise: weekly e1RM trend, personal records, plateau detection, last session details, and strength_state — the trend STATE (progressing / holding / stalling / deloading / insufficient_data) classified over the 6-week window stated in its window_weeks, the same signal shown on the iOS lift detail page. Prefer strength_state over raw weekly points when judging whether a lift is improving. For the per-lift % gain ("+59%") and the 8-week state, use get_strength_climb — its constituents carry indexed_pct and their own window_weeks; the two states can differ for one lift because the windows differ, so quote the window with the state. Use when the user asks about a specific lift (e.g., "am I getting stronger on bench press?" or "have I plateaued on squats?"). Pass EITHER exercise_id (exact — from search_exercises or a prior resolution.candidates) OR exercise (a name, fuzzy-matched against the user's history). Prefer exercise_id when you have it: a fuzzy NAME can match several variants the user trains (e.g. "Incline Bench Press" → dumbbell vs machine), and the response's `resolution` block reports which id was chosen, whether it was `ambiguous`, and the `candidates` — if ambiguous, re-query with the exact exercise_id you meant. For muscle-group-level interpreted analysis (fatigue, plateau, effective volume), use get_muscle_state. For raw time-series data, use get_muscle_group_progress.
    ConnectorOAuth
  • 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

Matching MCP Servers

Matching MCP Connectors

  • Visa Requirements MCP — passport visa rules for any nationality → destination pair

  • Visa Requirements: Most up-to-date visa requirements with color-coded status indicators covers 200.

  • 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 }`.
    ConnectorNo auth
  • Retrieve the results of a job. Can be called before completion for partial results, or after completion for the full set. Returns clustered, validated, and enriched web results. While job status is active, call this repeatedly (typically page=1) to refresh partial output. When job reaches completed, iterate all pages. If job fails, call once more to capture any partial output.
    ConnectorNo auth
  • Retrieve the results of a job. Can be called before completion for partial results, or after completion for the full set. Returns clustered, validated, and enriched web results. While job status is active, call this repeatedly (typically page=1) to refresh partial output. When job reaches completed, iterate all pages. If job fails, call once more to capture any partial output.
    ConnectorNo auth
  • Fetch the result or progress of a previously initiated StockLens analysis. Returns status (in_progress/complete/failed), progress percentage, and full result when complete. Each call returns the current state once; it does not wait for completion. While status is in_progress, retry_after_seconds is the earliest sensible time to check again — check again only if the user asks to continue. Complete results include composite score, domain breakdowns, key insights, and may include a Plus Analysis AI narrative. Does NOT start a new analysis and does NOT rank or screen stocks — call discover_stocks for a multi-stock list. Does NOT accept a ticker; only the analysis_id from initiate_analysis.
    ConnectorNo auth
  • Enqueue a fresh deterministic analysis run for a saved project. Returns immediately with `agentStatus` (`queued`, `running`, `current`, `failed`, or `none`) and a receipt id; does not block on completion. Irreversible: a queued run cannot be un-queued from MCP. Re-check with `getProjectContext`, but no more than once every 15 seconds — it is a multi-query bundle, not a status endpoint.
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • Get the full record for a single V&A object by its system number (e.g. "O72610", as returned by search_objects). Returns title, maker, object type, materials, description, date, place, dimensions, and a usable image URL. Keyless.
    ConnectorNo auth
  • ARCANE's live scenario tracker: for each pre-registered scenario, where the world is on its branching map — checkpoint COMPLETION as N/M (confirming signals fired of total), a direction of resemblance, staleness, and which fork checkpoints have fired or are pending. A live STATE view, NOT a forecast: completion is not a probability and direction is resemblance, not odds. ARCANE never states a scenario's likelihood. Check as_of/stale.
    ConnectorNo auth
  • Update a Clarity process name, guidance, visibility, or completion status. Team Builders can edit names and guidance, only the creator or a team manager can change visibility, and completion requires a Lead Builder role.
    ConnectorNo auth
  • Complete a subtask, optionally recording a typed response_value (e.g. the weight or reps for that set). Each completion is timestamped, so consecutive set completions yield per-set durations. Returns progress including all_subtasks_complete — when true, complete the parent task with tascan_complete_task.
    ConnectorNo auth
  • Record one completion of a custom goal. The goal is created on first use, so no setup call is needed; names are lowercase letters, digits, underscores, and hyphens, max 64 chars. Pass visitorUid (the _fs_vid cookie value of a visitor the tracking script has already seen) so the completion attaches to that visitor's sessions and source; omit it for an anonymous completion. Each call appends a completion, so repeating it counts the goal twice. Use track_payment for revenue, which records a payment goal on its own. Undo with delete_goals. Requires websiteId or domain with a workspace token.
    ConnectorOAuth
  • Get the active project's security score (0–100) and the count of open findings by severity. Pass trendDays to also get the daily score history over that many days — that is how you tell whether a project is improving or drifting. Use this for the score and open counts; for the findings behind it use get_security_findings. Requires project context.
    ConnectorAPI key
  • 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)
    ConnectorNo auth
  • 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)
    ConnectorNo auth
  • Build a hierarchy tree for a VFB term, showing ancestors (parents) and/or descendants (children). Use relationship "part_of" for brain region structure (e.g. "what are the parts of the mushroom body?") and "subclass_of" for cell type hierarchies (e.g. "what types of Kenyon cell are there?"). Descendants are returned as a nested tree for both relationship types. Ancestors are returned as a nested chain, filtered to nervous system terms for part_of. Start with max_depth=1 for direct parents/children, and offer to go deeper if the user wants more detail.
    ConnectorNo auth