"Working with Apple devices and accessing local data" matching MCP tools:

• axint.runA

  AxintA

  Run the enforced Axint Apple build loop outside the Xcode UI. Use: use for the complete proof loop; use swift.validate, cloud.check, or fix-packet when only one stage is needed. Inputs: integration=minimal enforces local advisory no-fix behavior; background returns a job id; outputDir controls artifacts. Effects: starts child processes, writes .axint/run artifacts, may run xcodebuild/tests, and may call Cloud Check.

  ConnectorNo auth

• recipe_deleteA

  Local MCPB

  Use this when the user wants to remove one of THEIR saved recipes/skills (the manifests under ~/.local/share/local-mcp/recipes). Destructive with a preview gate: the first call (without confirm) shows what would be deleted; call again with confirm=true to actually delete. Bundled starter recipes can't be deleted. To modify a recipe instead, recipe_save with the same name and overwrite: true replaces it.

  Connector

  Destructive

  OAuth

• collapsed_as_builtA

  Critical Path PartnersA

  Collapsed As-Built / But-For analysis on a post-impact XER. Implements AACE RP 29R-03 §3.8 Modeled / Subtractive / Single Base method (paired with MIP 3.3 Windows for the dual-method gap report per SCL §11.5). Validates a forensic windows analysis (MIP 3.3) by independently computing the same project drift via subtractive removal of delays from the as-built schedule. For each delay event, the as-built duration of every ``affected_activity`` is shortened by ``impact_days`` working days on that activity's calendar (or removed entirely if ``removal_method="remove"``), then CPM re-runs and the resulting "but-for" finish date is compared to the as-built finish. Cumulative pass removes ALL events at once for a project-level but-for finish. Every finish shift is stated in working days on ``workday_calendar``; the calendar-day span of the same shift is kept beside it, and ``day_unit_basis`` names the unit of every bare ``*_days`` key in the result. Use this tool when opposing counsel demands a but-for analysis or you need a dual-method validation pairing §3.3 (windows) with §3.8 (collapsed-as-built). For prospective fragnet insertion (MIP 3.7), use ``time_impact_analysis_fragnet`` instead. Args: as_built_xer_path: server-side post-impact XER (after delays incurred). as_built_xer_content: full text of post-impact XER (alternative for hosted/remote use). Supply EXACTLY ONE of path/content. delay_events: list of event dicts. Each must have ``event_id``, ``affected_activities`` (list of task_codes), and ``impact_days`` (number of working days on the affected activity's calendar). Optional: ``removal_method`` ('shorten'|'remove'), ``responsible_party``, ``name``, ``description``. output_dir: optional output dir for HTML/CSV (tempdir if ""). project_name: optional override. removal_method: global default 'shorten' or 'remove'. contractor_filter: when True, exclude contractor-caused events from the cumulative pass (owner audit mode). Returns: { "as_built_finish": "YYYY-MM-DD", "per_event_results": [{event_id, but_for_finish, impact_workdays_collapsed, collapse_state, duration_removal_basis, finish_driver_after_removal, ...}, ...], # impact_workdays_collapsed is the event's finish shift in # working days on workday_calendar. Each event also carries # impact_days_collapsed: the same shift in calendar days. # duration_removal_basis discloses WHAT duration was removed # and on what basis; finish_driver_after_removal discloses # WHAT drives the but-for finish (incl. whether it is bound by # the data-date floor) so a reader sees WHY the finish did or # did not move across data dates. "cumulative_but_for_finish": "YYYY-MM-DD", "cumulative_impact_workdays": int, # working days on workday_calendar "cumulative_impact_days": int, # the same shift in calendar days "cumulative_collapse_state": str, # a 'locked_by_actuals' zero is not "no impact" "workday_calendar": str, # the calendar every working-day figure is stated on "day_unit_basis": dict, # each bare *_days key: 'working_days' or 'calendar_days' "dual_method_gap": dict | None, # working days only "output_files": {...}, "warnings": [...], "method": "AACE 29R-03 §3.8 (Modeled/Subtractive/Single Simulation)" }

  ConnectorNo auth

• list_modelsA

  BridgeNode MCPA

  List available models and their prices — free, no payment, no authentication required. Read-only: no state changes; data is served from the server's local config, so repeated calls return identical results (idempotent). Accepts no parameters: the input schema is an empty object, and any arguments passed are ignored. Calling it without arguments returns the complete catalog with per-token prices; there is no filtering, pagination, or configuration. Use this tool to inspect models and prices before calling the paid chat_completions tool. Same data as GET /v1/models (§5.2). Do not use it to generate text (use chat_completions) or to estimate a specific request's cost (use get_price_estimate).

  ConnectorNo auth

• list_devicesA

  ReflectoA

  List the user's own paired Reflecto devices (their phone and desktop) and whether each is reachable. A phone counts as reachable when it has a live push registration, even if it is currently asleep or switched off — reachable does not mean the user is active on it right now. For recency use statusReportedAt (unix seconds of the last device status report); lastSeenAt is coarse (hourly) for phones. Read-only — returns device names and status metadata, never any message or notification content. Call this before send_notification when you need to pick a specific device — pass that device's `deviceId`, not its label, when you mean exactly one: labels can repeat across devices and a repeated label delivers to all of them.

  ConnectorOAuth

• arp_tableA

  Netmon (demo)A

  Lists hosts observed on the local LAN(s) via the ARP table — the 'what devices have we seen recently?' question. Wraps POST /api/getArpTable, which collapses arptable + _dns into one row per IP with hostname + monitored-device id resolution attached. Distinct from `arp_lookup` (single-IP MAC resolution at the current moment): this is the historical view over the last N hours. Use it for 'who's on the LAN today' / 'is there a new device' / 'where did this IP last appear' questions. Each row: {id, ip, mac, timestamp, hostname, device_id}. device_id is non-null when the IP corresponds to a monitored Netmon device; hostname comes from _dns (PTR + custom overrides). Rows are deduped by IP — only the latest seen entry per IP within the window is returned. Permission: devices. Tag-scoping is NOT applied here — ARP is subnet-level, not device-level, so it doesn't have a tag anchor. Operators see the whole LAN regardless of tag scope. Examples: arp_table({}) // last 24h, no filter arp_table({hours: 1, search: "10.0.0"}) arp_table({search: "laptop"})

  ConnectorNo auth

• get_public_holidaysA

  DatoQA — Official Public HolidaysA

  Get published public-holiday entries for one calendar and year or exact inclusive local date. Use a known region id directly (fr-metropole, gb-england-and-wales, hk-general, oh-de); consult list_holiday_regions only if scope is unknown. OpenHolidays entries retain multilingual names, subdivisions and half-day scope; set nationwide_only=true to exclude regional entries. Government feeds and third-party curated calendars are explicitly distinguished. Empty results do not establish working days; future dates can change, and aggregator dates are not individually government-confirmed.

  ConnectorNo auth

• get_public_holidaysA

  DatoQAA

  Get published public-holiday entries for one calendar and year or exact inclusive local date. Use a known region id directly (fr-metropole, gb-england-and-wales, hk-general, oh-de); consult list_holiday_regions only if scope is unknown. OpenHolidays entries retain multilingual names, subdivisions and half-day scope; set nationwide_only=true to exclude regional entries. Government feeds and third-party curated calendars are explicitly distinguished. Empty results do not establish working days; future dates can change, and aggregator dates are not individually government-confirmed.

  ConnectorNo auth

• get_public_holidaysA

  DatoQAA

  Get published public-holiday entries for one calendar and year or exact inclusive local date. Use a known region id directly (fr-metropole, gb-england-and-wales, hk-general, oh-de); consult list_holiday_regions only if scope is unknown. OpenHolidays entries retain multilingual names, subdivisions and half-day scope; set nationwide_only=true to exclude regional entries. Government feeds and third-party curated calendars are explicitly distinguished. Empty results do not establish working days; future dates can change, and aggregator dates are not individually government-confirmed.

  ConnectorNo auth

• list_boxesA

  spacesheepB

  The person's cloud boxes, newest first: state (waking, working, idle, asleep), what it's doing now, the last ask and the last reply. With `box`, that one box with its recent thread and the whole last reply — poll this every 20–30 s after start_box or message_box until state is idle and last_reply is set (a turn takes from seconds to many minutes).

  ConnectorOAuth

• sourcing_strategiesA

  MarketCodeA

  The nine sourcing strategies as data — read this BEFORE running `sourcing_search` in strategy mode. Each preset publishes its thesis, its filters (every key overridable, with the default and the unit), its ranking components with weights and scales, the feature columns it reads, the data gaps that limit it, and its version. Pass `area` as a local-authority GSS code (E09000032) to get `data_ready` per strategy for that authority: `ready`, `partial`, `not_ready` or `unknown`, with the coverage share behind the verdict. A `partial` verdict is usable — say the share when you report the results. Do not run a preset over an authority marked `not_ready` without telling the user what is missing. UK only. Free.

  ConnectorNo auth

• rotate_api_tokenA

  AudD Music RecognitionA

  Replaces the account api_token with a new one and returns it. The OLD TOKEN STOPS WORKING IMMEDIATELY - only call this when the user explicitly asks to rotate/revoke their token.

  Connector

  Destructive

  OAuth

• create_agent_identityA

  AgentsXA

  Create your own PUBLIC agent profile for this OAuth connection, choosing a handle and display name. Requires identity:create approved by your operator and their current Terms/eligibility agreement. Exactly one identity per connection; identical retries return it, changed input conflicts. Cannot select or assume an existing identity, including pilots. No API key is issued, no hosted compute starts, and no trial allowance changes. Choose your identity before posting, following or accessing an inbox. public_visibility_ack=true acknowledges the profile is public. If permission is absent, ask the operator to reconnect with identity:create; never fabricate their consent.

  Connector

  Destructive

  API key

• upload_mediaA

  flayrB

  [writes flayr data · `write` scope] Step 1 of attaching a LOCAL file (video or image) to a draft. Returns a single-use, short-lived `uploadUrl`. Step 2: POST the raw file bytes to it with the file's Content-Type, e.g. `curl -X POST -H "Content-Type: video/mp4" --data-binary @clip.mp4 "<uploadUrl>"` — the JSON response has a `storageId`. Step 3: pass it as `videoStorageId` or `imageStorageId` on create_content or update_content. For media already on the web, skip this and pass `videoUrl` / `imageUrl` instead. Returns 413 when the account's storage is full. (Wraps POST /api/v2/media/upload-url.)

  ConnectorOAuth

• connect_whatsapp_accountA

  Vendo AIB

  Returns a hosted link; the user opens it and scans the QR code with WhatsApp (Linked devices) — that links a REAL phone number to the workspace. Poll list_whatsapp_accounts until status is "ok". Free. Only after preview_connect_whatsapp_account and the user's approval.

  ConnectorNo auth

• fda_searchA

  Fda RegulationsA

  Keyword search across FDA regulations — US Food & Drug Administration rules in 21 CFR. Answers "what FDA regulations cover X", "the FDA regulation / rule about X", "find the FDA requirement for X". Great for topics: good manufacturing practice (GMP / cGMP), quality system regulation, medical device labeling, drug labeling, nutrition facts / food labeling, new drug applications, dietary supplements, cosmetics, biologics, controlled substances, current good manufacturing practice for drugs and devices. Returns matching FDA regulations with citation (21 CFR), heading, excerpt, and source URL. This searches FDA REGULATIONS (regulatory text); for FDA DATA (drug labels, adverse events, recalls) use the openfda tools. Example: fda_search({ query: "medical device labeling" }); fda_search({ query: "good manufacturing practice", limit: 15 }). Keyless.

  ConnectorNo auth

• gov_contracts_searchA

  Us Gov ContractsA

  Search AWARDED US state & local government contracts, normalized across jurisdictions (keyless open data). Filter by vendor (winning supplier), keyword (contract title/description), awarding agency, and minimum dollar amount. Covers state and county contract registries — pass a `jurisdiction` key (see gov_contracts_jurisdictions) to target one, or omit it to search all covered jurisdictions at once. Returns each contract with its ID, vendor, title, agency, amount, and dates. This is STATE/LOCAL award data (for federal contracts use USAspending/SAM tools).

  ConnectorNo auth

• sourcing_strategiesA

  MarketCodeA

  The nine sourcing strategies as data — read this BEFORE running `sourcing_search` in strategy mode. Each preset publishes its thesis, its filters (every key overridable, with the default and the unit), its ranking components with weights and scales, the feature columns it reads, the data gaps that limit it, and its version. Pass `area` as a local-authority GSS code (E09000032) to get `data_ready` per strategy for that authority: `ready`, `partial`, `not_ready` or `unknown`, with the coverage share behind the verdict. A `partial` verdict is usable — say the share when you report the results. Do not run a preset over an authority marked `not_ready` without telling the user what is missing. UK only. Free.

  ConnectorNo auth

• disconnect_sign_in_methodA

  CalyB

  Remove Google or Apple as a way to sign in to the user's Caly account. The last remaining way in can never be removed, so the call is refused (sign_in_method_last_method) if it is the only one; a method that is not connected is refused too (sign_in_method_not_connected_error). Check list_sign_in_methods first. The password is changed with change_password, and to add a password before removing the only Google or Apple sign-in, use send_password_setup_email. Connecting Google or Apple is done by the user on the Caly website, in the Security section of their account settings. Two steps: the first call returns CONFIRMATION_REQUIRED with a confirmToken; tell the user what will happen, then call again with the SAME arguments plus confirmToken.

  Connector

  Destructive

  OAuth

• asterwise_get_kp_ruling_planetsA

  AsterwiseA

  Computes KP ruling planets at a latitude and longitude for the current instant or a given local date and time, with no birth data. Returns the day lord, Moon and Ascendant lord chains, and a deduplicated ruling_planets list. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_kp_chart — if natal confirmation is needed afterwards. INPUT CONTRACT: lat and lon required. Optional target_date (YYYY-MM-DD), target_time (HH:MM), target_timezone (IANA; defaults to the zone at lat/lon). With neither date nor time the server uses the current instant (KP judges ruling planets at the moment of judgment); time only = that time today; date only = 12:00 local. data.target_utc and data.target_timezone show what was used. target_date must be within 1800-01-01 to 2099-12-31. A time skipped by a daylight-saving change is read with the offset before the change (moved forward by the gap); a time that occurred twice is read as the first occurrence; data.local_time_status is 'nonexistent' / 'ambiguous' / 'ok'. DO NOT CONFUSE WITH: asterwise_get_kp_chart — needs BirthData and returns full natal KP cusps. asterwise_get_prashna_chart — horary keyword workflow, not ruling-planet snapshot. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-kp-ruling-planets/

  ConnectorOAuth

• get_parcel_reportA

  Cenogram - Polish Real Estate DataA

  The whole dossier for one land parcel in one call - prefer it over the per-layer parcel tools. Contains the parcel core (location, area, land use, designation); fourteen layers (flood, heritage, landslide, subsurface, surroundings, transit, general-plan zoning (POG), local plans (MPZP), buildings, building activity, agricultural eligibility, land/soil class, nature, road access); the parcel's transactions (newest first, up to 20); local price context (county and gmina median zł/m², last 12 months); municipal context (demographics, infrastructure signals); and a parcel-shape section (outline geometry only). For a coordinate or 'locality + number' use resolve_parcel first; for a street address use list_parcels_in_area. For the plan or designation pass preset="zoning" (core, MPZP, POG, nearby-designation signal only). Section states: covered; covered_no_data (checked, nothing found; billed); not_covered (outside our data; refunded); not_computed (timed out; refunded - the report can be partial). The local-plan section answers in_plan / no_plan / unknown (unknown is never a claim that no plan exists). Context sections use full / low_sample / suppressed / no_data (shape: full / no_data). Long lists are capped with a count. Reading it: the nearby designation signal comes from RCN deeds of neighbouring land, not the planning register - it describes the neighbourhood, not this parcel; confirm with the local plan (MPZP) or a zoning decision. Neither it nor the shape section says whether a parcel can be built on or divided. Construction age is an ESTIMATE with an interval (permit records start in 2016), often "not established". Costs 45 API tokens (preset="zoning": 11), billed by outcome: an unresolvable parcel is refunded; a resolved one with no layer data pays only the 1-token core floor; with a covered layer, in full. Requests are rate-limited per API key per minute (parallel agents on one key share it). On "Too many requests", wait the given seconds and retry sequentially.

  ConnectorOAuth