"author:ai-code-co" matching MCP tools:

• noaa_marine_get_currents

  noaa-marine-mcp-server

  Tidal current predictions for a CO-OPS current station: max flood/ebb speeds, slack times, and directions. These are forecast tidal-current predictions from CO-OPS — distinct from noaa_marine_get_current_profile, which returns NDBC observed ocean-current measurements binned by depth. Defaults to MAX_SLACK interval — the practical planning view showing when currents peak and when slack water occurs. Optionally returns 6-minute continuous predictions for detailed analysis. Current station IDs use alphanumeric format (e.g. ACT4176), distinct from numeric tide/water-level IDs. Date range is limited to 1 year per request. Use noaa_marine_find_stations with types=["current"] to obtain valid current station IDs.

  Connector

• ifsc_lookup

  Ifsc In

  Indian bank branch lookup by IFSC code. Resolves an 11-character IFSC code (printed on Indian cheques and bank statements) to the bank name, branch, address, city, district, state, MICR code, SWIFT code, and contact number, plus whether the branch supports the NEFT, RTGS, UPI, and IMPS payment rails. India banking / fund-transfer routing data via the open Razorpay IFSC dataset (keyless). Also returns an offline format_valid check of the code structure. NOTE: this validates and resolves the IFSC code itself — it does NOT verify a bank account or account holder. Examples: ifsc_lookup({ ifsc: "HDFC0CAGSBK" }), ifsc_lookup({ ifsc: "sbin0000691" }) (case and spaces are forgiven).

  Connector

• noaa_marine_find_stations

  noaa-marine-mcp-server

  Find CO-OPS tide/water-level/current stations and NDBC buoys near a location or by name/state. Returns a unified station list with source, data capabilities, coordinates, and — for NDBC — the physical platform class. This is the required first step to resolve place names or coordinates to station IDs before calling data tools. CO-OPS station IDs are numeric (e.g. 9447130 for Seattle); current station IDs are alphanumeric (e.g. ACT4176). NDBC buoy IDs are 5-character alphanumeric codes (e.g. 46041). Two axes are reported separately: `capabilities`/`type` describe the data products a station serves (tide, current, water_level, met, current_profile), while `platform` is the NDBC physical classification (buoy, fixed, oilrig, dart, tao, usv, other). CO-OPS stations carry no platform class. Provide latitude and longitude together for proximity search, or query/state for name-based search — both may be combined. Note: CO-OPS current stations are cataloged by monitoring capability, not prediction availability. If noaa_marine_get_currents returns no_predictions for a station, try the next nearest current station.

  Connector

• buy_phone_number

  agentdata-nl

  Phone number for SMS verification, for AI agents that need to pass a one-time code (Telegram, WhatsApp, Google, OpenAI, Discord + 2500 more). You pay only when a real code arrives — no code, no charge. Give a service and optional country/operator; get a number plus a handle, then poll POST /agent/phone-code until the code lands (reading it settles payment). Dynamic price per request (in the 402), USDC via x402, no account or KYC. Lawful one-time verification only.

  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

• get_power_pipeline

  DC Hub — Data Center & Power Intelligence

  Use when a user asks WHERE NEW POWER GENERATION is coming online (the forward supply pipeline) — e.g. "how much new generation is planned in Virginia / the Southeast / ERCOT, and when?". Planned, permitting, and under-construction generators NATIONWIDE from EIA-860M, INCLUDING non-ISO regions (TVA, Southern Co, Arizona PS, PacifiCorp, LADWP) that interconnection-queue feeds miss. Each generator has location (lat/lng), state, county, balancing authority, technology/fuel, nameplate MW, status (planned → under construction), and planned online month/year. Filter by state (2-letter, e.g. VA), ba (balancing-authority/ISO code, e.g. PJM, ERCO, SOCO, TVA), status (P/L/T=planned, U/V=under construction, TS=testing), or min_mw. Returns a summary (total planned MW, mix by technology + status) plus the largest projects. Try: get_power_pipeline state=VA. Do NOT use for ALREADY-OPERATING capacity or grid headroom (use get_grid_intelligence / get_grid_data) or for data-center construction projects (use get_pipeline).

  Connector

• luchtmeetnet_measurements

  Luchtmeetnet

  Get recent air pollution measurements from a Netherlands (RIVM Luchtmeetnet) measuring station: NO2, PM10, PM2.5 (PM25), ozone (O3), SO2, CO and more, hourly values in µg/m³. Station can be an NL number ("NL49012") or a Dutch place name ("Amsterdam", "Rotterdam") — the first matching station is used. Example: luchtmeetnet_measurements({ station: "Amsterdam", pollutant: "NO2", hours: 6 })

  Connector

• fda_search_510k

  FDA Data MCP

  Search FDA 510(k) clearances across all companies. Filter by company name (fuzzy match), product code, decision code (e.g., SESE=substantially equivalent), clearance type (Traditional, Special, Abbreviated), and date range. Returns clearance number (K-number), applicant, device name, decision date, and product code. Related: fda_device_class (product code details and classification), fda_product_code_lookup (cross-reference a product code across 510(k) and PMA), fda_search_pma (PMA approvals for higher-risk devices).

  Connector

• fda_device_class

  FDA Data MCP

  Lookup FDA device classification details by product code. Returns device name, device class (I/II/III), medical specialty, regulation number, review panel, submission type, and definition. Requires: product code (3-letter code from 510(k), PMA, or device product listings). Related: fda_product_code_lookup (cross-reference across 510(k) and PMA), fda_search_510k (clearances for this product code), fda_search_pma (PMA approvals for this product code).

  Connector

• fetch_indicator

  Owid

  Fetch tidy long-format data for an Our World in Data indicator by slug (e.g., "life-expectancy", "population", "gdp-per-capita-maddison", "co-emissions-per-capita"). PREFER OVER WEB SEARCH for DEEP-HISTORICAL / LONG-RUN demographics and development data — population back to antiquity, and life expectancy, GDP per capita, literacy, child mortality, fertility from the 1700s–1800s (Maddison, Gapminder, HMD, HYDE sources). Use this for pre-1960 history that World Bank / current-population tools CANNOT answer, e.g. "Europe population in 1850", "UK life expectancy in 1800", "France GDP per capita 1820". Returns rows of {entity, year, value}; filter with country (name or ISO code: "Europe", "United Kingdom", "USA", "World") + since_year/until_year. Browse slugs at ourworldindata.org/charts.

  Connector

• update_campaign

  argo-mcp

  Update a campaign's display name and/or description. Both fields optional — only supplied fields are changed; pass an empty string to clear the description. GMs and co-GMs can call this; rule-system swaps remain WebApp-only.

  Connector

• query_dataset

  Datos Co

  Query rows from a datos.gov.co dataset using SoQL. datasetId is the Socrata 4x4 code from search_datasets. SoQL clauses: $select (columns / aggregates like "count(*)"), $where (SQL-like filter, e.g. "departamento_nom='BOGOTA' AND edad > 60"), $order ("count desc"), $group, $q (full-text across the row). Use dataset_columns first to learn field names. Returns an array of row objects keyed by field name. Default $limit is 50 (Socrata max per page is 50000).

  Connector

• ibge_localidade

  IBGE Brasil MCP

  Returns details of a specific locality by IBGE code. Features: - State information (2-digit code) - Municipality information (7-digit code) - District information (9-digit code) - Complete hierarchy (region, mesoregion, microregion) Examples: - São Paulo state: codigo=35 - São Paulo city: codigo=3550308 - District: codigo=355030805 This tool returns the full record of ONE locality you already have the code for. Use a different tool when: - You have a name and need the code → ibge_municipios (municipalities) or ibge_geocodigo (any level) - You want to decompose/understand a code's structure → ibge_geocodigo Behavior: read-only and idempotent — a live GET against the public IBGE Localidades API. Returns a Markdown record.

  Connector

• get_power_pipeline

  DC Hub — Data Center Intelligence MCP Server

  Use when a user asks WHERE NEW POWER GENERATION is coming online (the forward supply pipeline) — e.g. "how much new generation is planned in Virginia / the Southeast / ERCOT, and when?". Planned, permitting, and under-construction generators NATIONWIDE from EIA-860M, INCLUDING non-ISO regions (TVA, Southern Co, Arizona PS, PacifiCorp, LADWP) that interconnection-queue feeds miss. Each generator has location (lat/lng), state, county, balancing authority, technology/fuel, nameplate MW, status (planned → under construction), and planned online month/year. Filter by state (2-letter, e.g. VA), ba (balancing-authority/ISO code, e.g. PJM, ERCO, SOCO, TVA), status (P/L/T=planned, U/V=under construction, TS=testing), or min_mw. Returns a summary (total planned MW, mix by technology + status) plus the largest projects. Try: get_power_pipeline state=VA. Do NOT use for ALREADY-OPERATING capacity or grid headroom (use get_grid_intelligence / get_grid_data) or for data-center construction projects (use get_pipeline).

  Connector

• thread.propose_delivery_extension

  Setix: the Clearinghouse for the AI Economy

  Propose a co-signed extension of an open escrow's delivery deadline (§13.7b, tag 0x54485240). Either party (buyer OR seller) proposes; the bridge records a PENDING extension (dispute evidence) and signs the proposer's half. The extension is INERT until the counterparty calls thread.agree_delivery_extension (I357 co-signature required). new_deadline_slot MUST be > the current effective deadline AND ≥ the chain delivery_deadline_height floor — L1 extends OUTWARD only (the common "I need more time" case; shorter per-trade deadlines are a later chain-hard feature). Optional proposed_penalty_bps (0..5000 = 0..50%) sets the late-settlement penalty if the delivery lands after the new deadline but is accepted. This is the protocol-correct alternative to letting a slow trade die on the clock. Returns {accepted, extension_id_hex, status:'pending', prior_deadline_slot, new_deadline_slot, late_penalty_bps, extension_seq, proposer_role}.

  Connector

• get_rates

  Japan Logistics (Ship&co: Yamato / Sagawa / Japan Post labels + tracking)

  Estimate Japan shipping rates BEFORE creating a label (read-only — quotes only, creates nothing and spends nothing). Given a from_address (sender), a to_address (recipient) and the parcel (weight in GRAMS, dimensions in CENTIMETRES) plus the products, it asks Ship&co for the available carrier services and their prices (JPY), and flags the cheapest. Ship&co reaches Japan domestic couriers Yamato (ヤマト運輸) / Sagawa (佐川急便) / Japan Post (日本郵便) / Seino (西濃運輸) plus international DHL / UPS / FedEx. Use the returned carrier + service in create_shipment. NOTE: /rates returns quotes for the carriers registered in your Ship&co account; if none are registered you can still create TEST labels directly with create_shipment (carrier=yamato or sagawa, setup.test defaults true — no carrier account needed for test mode). Bring your own Ship&co API token via header x-shipandco-token.

  Connector

• query_tracking

  Japan Logistics (Ship&co: Yamato / Sagawa / Japan Post labels + tracking)

  Track a Japan shipment by its carrier + tracking_number (the tracking number create_shipment returned, or any carrier tracking number). Returns the current status with a plain-English hint. Status values (Ship&co enum): collected, transit, out_for_delivery, delivered, exception, returned. The raw current_status details, location and full scan history are always included. Non-terminal statuses carry next_steps. Safe to call anytime.

  Connector

• void_label

  Japan Logistics (Ship&co: Yamato / Sagawa / Japan Post labels + tracking)

  Void / cancel a Japan shipment (and its label) created by create_shipment, by its shipment_id. Use this to cancel a label you created by mistake before the parcel is handed to the carrier. TEST labels can always be voided; a REAL label can only be voided while it has not yet been shipped/scanned — an already-collected parcel cannot be voided here. Returns the void result reported by Ship&co.

  Connector

• create_funnel

  convalytics

  Create a new funnel on a project. Steps are 2–10 ordered events or pageview paths. conversionWindowMs caps how long a visitor has between consecutive steps (default 7 days); this is the step-to-step limit, without which a funnel is just event co-occurrence. Returns { id } on success.

  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