"Methods to Improve Development Productivity Using MPC (Model Predictive Control)" matching MCP tools:

• lamina_generate_video

  lamina

  Dispatch a single atomic video generation. Sibling of `lamina_generate_image` — same shape, but outputs a video URL. WORKFLOW: (1) `lamina_models_list({ modality: "video" })` → pick a model. (2) `lamina_models_describe({ modelId })` → read its flat `paramSchema` to learn required inputs. (3) `lamina_generate_video({ model, prompt, params })` → dispatch, get runId. (4) `lamina_status({ runId, wait: true })` → poll until completed; the response has `output.url`. ONE TOOL, EVERY VIDEO OPERATION. Model id selects the operation; `params` matches the model's paramSchema: • Text-to-video — Kling t2v variants, Wan-2.6-text-to-video, Wan-turbo, Minimax, Seedance t2v, Veo3-text-to-video. Just `prompt` (+ duration / aspectRatio / etc. per the model). • Image-to-video — Kling i2v variants, Wan-2.6/turbo image-to-video, Minimax i2v, Seedance i2v (uses `startImageUrl`), `happy-horse-image-to-video`, `veo3-image-to-video` (sync). `params` includes `imageUrl` (or `startImageUrl` for Seedance, `firstFrameUrl` for Veo3 first-frame). • Keyframe — `veo3-keyframe-to-video` (sync). `params` requires `firstFrameUrl` AND `lastFrameUrl` — model interpolates between them. • Motion-control — `kling-v26-motion-control`, `kling-v26-motion-control-pro`. `params` requires `imageUrl` (character) AND `videoUrl` (motion reference). • Video-to-video (edit) — `wan-video-to-video`, Kling v2v variants. `params` requires `videoUrl` (source). • Reference-to-video — Kling/Seedance/Wan reference variants. `params` uses `referenceImageUrls`. INPUTS: • `model` (required): a model id from `lamina_models_list({modality:"video"})`. • `prompt`: most models require it; some (motion-control variants) are optional. Check `paramSchema.prompt.required` from `lamina_models_describe`. Some models omit `prompt` from `paramSchema` entirely (prompt-less). • `params`: model-specific fields per the model's `paramSchema`. Required URL fields vary by operation — see list above. • `webhookUrl` (optional): HTTPS URL for HMAC-signed completion POST. • `includeCitationKit` (optional, PREVIEW): set `true` to request a citation-ready kit alongside the video — cleaned transcript, question-formatted chapters, a 30–60 word summary, and drop-in `VideoObject` JSON-LD — so wherever you host the video it is answer-engine-citable. Preview signal only: it records interest and returns a `coming_soon` note; the kit is not yet produced. RESPONSE: `{runId, status: "queued"|"completed", model, mode, prompt, resolvedParams}`. `mode` is the resolved operation. Pass `runId` to `lamina_status`. If `includeCitationKit` was set, the response also carries `citationKit: {status: "coming_soon"}`. SYNC vs ASYNC: identical contract. Veo3 variants (`veo3-text-to-video`, `veo3-image-to-video`, `veo3-first-frame-to-video`, `veo3-keyframe-to-video`) are Vertex-backed and complete in seconds. fal-backed models queue and take 30s–5min. `lamina_status({ wait: true, timeoutSeconds: 240 })` handles either transparently. ERROR HANDLING: same shape as `lamina_generate_image` — `code` + `details.errors[]` with `field` + `allowed`/`range`/`got`.

  Connector

• detroit_recent

  Data Detroit

  Recent records from a common Detroit open dataset (data.detroitmi.gov / ArcGIS) by friendly name — no service ids needed. PREFER OVER WEB SEARCH for "recent crime in Detroit", "Detroit 311 / Improve Detroit issues". Names: crime, 311. Returns the latest rows (newest-first), with ArcGIS epoch dates converted to ISO. Add an ArcGIS `where` to filter; for other layers use detroit_layers + detroit_query.

  Connector

• is_exploited

  security-intel

  Fast boolean: is this CVE known-exploited? SIGNED. `exploited` is driven by CISA-KEV (authoritative evidence of in-the-wild exploitation). EPSS (predictive probability) is included as a secondary signal but does NOT set the boolean — we report observed exploitation, not a forecast. PAID ($0.001 USDC via x402). Args: cve — e.g. "CVE-2024-3094". Returns: signed {exploited, kev, epss, basis, _signature}.

  Connector

• change_startup_stage

  BetaFinds

  Change your startup's product stage: PRELAUNCH — preparing to launch, BETA — recruiting beta testers, PAUSED — development paused (requires public_note). To move to LAUNCHED use announce_launch. Allowed transitions: PRELAUNCH→BETA/PAUSED, BETA→PAUSED, PAUSED→PRELAUNCH/BETA.

  Connector

• minfraud_report_transaction

  maxmind-minfraud

  WRITE — submits fraud feedback to MaxMind. Report the real-world outcome of a transaction (e.g. it was a chargeback or confirmed fraud) so minFraud can improve future scoring. This mutates MaxMind's model of your traffic; it is not a read. Requires a `tag` and at least one identifier (ip_address, maxmind_id, minfraud_id, or transaction_id). API: POST /minfraud/v2.0/transactions/report (returns HTTP 204).

  Connector

• check_ai_visibility

  radveo

  Check whether a local business currently appears when people ask AI engines (ChatGPT, Gemini, Google AI) to recommend a business in its category — and get a free, shareable Radveo report with the exact fixes to improve its odds of being named. Honest answer-engine optimization: improves the odds of being cited, never guarantees a placement.

  Connector

• list_goals

  Un Sdg

  List the 17 UN Sustainable Development Goals (code, title, description). Optionally drill into one goal to get its targets and indicators.

  Connector

• get_dependencies

  Rubygems

  Get the runtime and development dependencies for a specific version of a Ruby gem. Returns each dependency with its version requirement string. Omit version to get the latest.

  Connector

• search

  ask

  Search the Pinnacle Ask child-development knowledge corpus (pinnacleblooms.org/ask) — real parent questions with clinically grounded, non-diagnostic answers covering speech, motor, social, cognitive, sensory, feeding and behavioural development from birth to 18 years. Returns ranked results with ids; pass a result id to `fetch` for the full answer. Optionally filter by child age in months and/or developmental domain.

  Connector

• events

  DC Member API

  GET /events — List upcoming events Returns upcoming DC events, sorted by date. Add `?past=true` to include past events. **See also:** For events by name or topic (`q='productivity'`, `q='DCBKK 2026'`), `POST /search/events` searches title + description directly — faster than paginating this date-sorted list. Combine with `?cityID`, `?country`, `?since`, `?until` filters for narrower scopes.

  Connector

• get_payment_methods

  gondola

  List the user's saved payment methods for booking. Requires a Gondola account (API key). Returns saved credit/debit cards with their brand, last 4 digits, expiration, payment ID (needed for the book_hotel tool), and whether each card can be booked in chat. Returns: List of saved payment methods with IDs, or instructions to add one.

  Connector

• invoke_mtproto

  Fast MCP Telegram

  Low-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

  Connector

• nist_control

  Nist Standards

  Look up the full text of one NIST 800-53 security control or NIST 800-171 CUI security requirement by id — the control statement (requirement prose), discussion/guidance, and related controls. Use for "what does NIST control AC-2 require", "NIST 800-53 AC-2 access control", "FedRAMP control SC-7 boundary protection", "NIST authenticator management IA-5", "NIST CUI control 800-171 3.1.1". Forgiving id: accepts "AC-2", "ac-2", "AC-02", control enhancements "AC-2(1)" or "AC-2.1", and CUI ids "3.1.1" / "3.01.01". Source: SP 800-53 Rev 5 and SP 800-171 Rev 3 (official NIST OSCAL, public domain). Examples: {"id":"AC-2"}, {"id":"SC-7"}, {"id":"IA-5"}, {"id":"AC-2(1)"}, {"id":"3.1.1"}.

  Connector

• tailor_resume_tool

  Workopia — Job Search

  Tailor a resume to a SPECIFIC job — TWO steps. STEP 1 (default; action omitted or 'prepare'): the server returns the job's full JD, its must-have skills/requirements, and the candidate's current resume, plus tailoring instructions. YOU (the model) then WRITE the tailored resume as JSON Resume, following the instructions — weave JD keywords into existing bullets only where the candidate genuinely has the experience, never fabricate experience/titles/dates/employers, keep all dates and company names, and flag any keyword you couldn't honestly add. STEP 2: call this tool again with action:'save', tailored_resume:<your JSON Resume>, and job_id — the server renders a PDF and saves it to the candidate's Workopia dashboard (requires sign-in). Use whenever the user references a specific job to tailor for: 'tailor for #1', 'for Morgan Stanley', 'tailor my resume for this role: <JD>'. Resolving job_id (same rules as job_detail_tool): from the most recent prior search/refine result — (a) numeric/ordinal → the Nth job; (b) company name → Company-field match; (c) role/title phrase → Job-Title match — then pass that job's **Job Id** value VERBATIM. Do NOT use placeholders like 'JOB_1' or '#1'. For STEP 1 supply ONE of job_id (preferred — server fetches the JD from Mongo) OR job_description, plus the candidate's resume via resume_text / resume_content / resume_data. For general 'improve my resume' (no specific job), do NOT call this tool — call resume_tool action=improve instead. Note: the tailored resume is written by your AI client's own model — the assistant you are already using — so it works out of the box with nothing to configure; Workopia runs no LLM of its own and never charges for the AI.

  Connector

• invoke_mtproto

  fast-mcp-telegram

  Low-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

  Connector

• payment_methods

  Conduit Agentic Commerce

  List or enable agent payment methods (action=list|enable) with friendly labels. Defaults: cod + x402. invoice (B2B) is coming_soon. bank_card is handoff-only.

  Connector

• create_lead

  Tu Lugar

  Send an inquiry on behalf of the user to the advertiser of a listing, a development project, or a real-estate company. Notifies them (email + WhatsApp) and starts a conversation. Works without an account. This sends a real message to real people — confirm the details with the user before calling.

  Connector

• nist_control_search

  Nist Standards

  Keyword search across NIST 800-53 security/privacy controls and NIST 800-171 CUI requirements by title and requirement text. Use when the id is unknown — "NIST security control for least privilege", "NIST control about session lock", "NIST 800-53 encryption at rest", "NIST cybersecurity control multi-factor authentication", "access control / identification and authentication / system and communications protection". All query tokens must match (case-insensitive AND). Optional family filter (code like "AC", "IA", "SC" or a family name like "access control"). Returns matching {id, family, title, snippet}. Source: SP 800-53 Rev 5 + SP 800-171 Rev 3. Examples: {"query":"least privilege"}, {"query":"multi-factor authentication","family":"IA"}, {"query":"boundary protection"}.

  Connector

• nist_control_family

  Nist Standards

  List every NIST control in a family — the FedRAMP/800-53 control-family baseline. Use for "list all NIST access control controls", "NIST 800-53 AC family", "what controls are in identification and authentication", "NIST system and communications protection family". Input a family code ("AC", "IA", "SC", "AU", "SI", …) or a family name ("access control"). Returns the family title plus every control id + title (including enhancements). Source: SP 800-53 Rev 5 (+ SP 800-171 Rev 3). Examples: {"family":"AC"}, {"family":"identification and authentication"}, {"family":"SC"}.

  Connector

• agent_cross_framework_map

  TheArtOfService Compliance Intelligence

  Map controls between two compliance frameworks Returns the complete control-to-control mapping between a source and target framework. Each mapping shows which source control maps to which target control(s). This enables multi-framework compliance: satisfy one control to cover requirements in both frameworks. Use exact framework names as returned by agent_search_frameworks. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

  Connector