"DaVinci Resolve" matching MCP tools:

• portal_resolve_entityA

  SQDA

  Resolve user-facing blockchain entities into query-ready identifiers, with ambiguity kept explicit. COMMON USER ASKS: - Resolve USDC on Base - Resolve WETH on Ethereum - Resolve BAYC contract FIRST CHOICE FOR: - resolving a token symbol like USDC to token contract addresses - resolving EVM contract aliases, protocol names, pool identifiers, or Hyperliquid coin names before querying - checking which token-list addresses a symbol maps to before querying logs or transfers - turning a user-friendly token name into deterministic EVM filters WHEN TO USE: - The user names a token symbol such as USDC, WETH, DAI, or PEPE and you need contract addresses before querying raw data. - The user names a well-known EVM contract, protocol, pool identifier, or Hyperliquid ticker and you need a deterministic follow-up filter. - You need to disambiguate bridged token variants on an EVM network. - You want a source-backed token address rather than relying on memory or hardcoded constants. DON'T USE: - You already have the exact address, pool id, protocol slug, or coin filter and can pass it directly. EXAMPLES: - Resolve USDC on Base: {"network":"base-mainnet","kind":"token","query":"USDC","limit":10} - Resolve WETH on Ethereum: {"network":"ethereum-mainnet","kind":"token","query":"WETH","limit":5} - Resolve BAYC contract: {"network":"ethereum-mainnet","kind":"contract","query":"bored apes"} - Resolve Hyperliquid coin: {"kind":"hyperliquid_coin","query":"bitcoin"}

  ConnectorNo auth

• ios_crash_symbolicateA

  Robot Actions — Remote Device ControlB

  Symbolicate a crash report (by id from ios_crash_analytics): resolve stack frames from `imageName + offset` into `symbol + offset (file:line)` using `atos` and symbol binaries on the host. System/OS frames resolve from Xcode’s on-disk DeviceSupport symbols (when a device of that iOS build was prepared in Xcode). App frames resolve only when a matching `.dSYM` is provided via `dsymPath` (matched by Mach-O UUID). Unresolvable frames are returned as-is. By default only the faulting thread is symbolicated.

  ConnectorOAuth

• goal-resolve-escalationA

  Planner (proof-of-done)A

  Resolve a pending AC escalation. Owner decides: edit (provide new AC text), split (move AC to a child goal), drop (remove the AC outright, optionally with a linkedGoalId audit reference), or reject (agent must find another way). All prior evidence on the AC is deleted for edit/split/drop so the agent must submit fresh proof.

  ConnectorNo auth

• goal-resolve-escalationA

  Planner MCP — provable "done" for AI agentsA

  Resolve a pending AC escalation. Owner decides: edit (provide new AC text), split (move AC to a child goal), drop (remove the AC outright, optionally with a linkedGoalId audit reference), or reject (agent must find another way). All prior evidence on the AC is deleted for edit/split/drop so the agent must submit fresh proof.

  ConnectorNo auth

• resolve_teamA

  Lumify Sports IntelligenceA

  Resolve messy team names, abbreviations, metros, or aliases to a Lumify team_id using sport, league, event, or player clues. Prefer this before list_teams when the string is a nickname or city token. Returns ambiguous instead of guessing — never auto-pick candidates[0]. City-only metros sit below the auto-resolve floor.

  ConnectorAPI key

• portal_debug_resolve_time_to_blockA

  SQDA

  ADVANCED: Resolve a timestamp to the nearest indexed block or slot. COMMON USER ASKS: - Resolve one hour ago on Base - Resolve an older time on Polkadot WHEN TO USE: - You are debugging timestamp windows or building a manual block-range query. - You want to inspect exact versus estimated timestamp-to-block resolution. DON'T USE: - You just want to query by time; most public tools already accept natural timestamps directly. EXAMPLES: - Resolve one hour ago on Base: {"network":"base-mainnet","timestamp":"1h ago"} - Resolve an older time on Polkadot: {"network":"polkadot","timestamp":"2026-04-08T12:00:00Z"}

  ConnectorNo auth

• list_team_membersA

  hyperpingA

  Users on the project, with names and emails. Use to resolve user IDs from schedules/policies.

  ConnectorNo auth

• get_receiptA

  quorumA

  Resolve receipt ids to the real records behind them. This is how you CHECK a claim: if an id does not resolve, the claim citing it was not real. Takes one id or many. Long records are truncated with notice; pass full: true for complete text.

  ConnectorNo auth

• get_agent_identity_jwksA

  RunOnProof — Payment Decision and Agent IDC

  Resolve RFC 8037 public verification keys for one opaque Agent ID without enumerating identities.

  ConnectorNo auth

• create_service_area_system_classA

  AssetLabB

  Link a system class to a service area. Requires service_areas:write scope. Resolve IDs first: list_service_areas → service_area_id, list_system_classes → system_class_id.

  ConnectorAPI key

• companies-resolve-domainA

  SaberC

  Resolve a company name to its official domain. Supply country and article context for ambiguous names. Branch on status; ambiguous candidates are alternatives, not a ranked answer. Allow up to four minutes.

  ConnectorNo auth

• get_entitiesA

  WikidataA

  Batch version of get_entity — resolve up to 50 Wikidata Q-ids in ONE call instead of looping single get_entity calls. Same fields as get_entity per entity (labels, descriptions, aliases, claims, sitelinks, revision info), keyed by Q-id. Any id that does not resolve (bad format, deleted, or genuinely unknown) is reported in "not_found" rather than failing the whole batch — the other ids still resolve. Pass "language" (comma/pipe-joined for several) the same as get_entity to get multilingual labels for every entity in the batch.

  ConnectorNo auth

• dns_differentialA

  mcpB

  Resolve a domain through filtered public DNS resolvers and their unfiltered controls to detect provider threat-feed blocks.

  ConnectorNo auth

• queryA

  kernelcadA

  Use this when you need to resolve or inspect topology against a script's lowered geometry. Selected by `mode` (default 'evaluate'): - 'evaluate' — inspect a Query (@kc[...] ref, @kcq[...] DSL, or { ast }); returns matched entities. Pass expect:'unique' to assert exactly-one. - 'resolve' — resolve a single @kc[...] / @kcq[...] ref to one entity ({ ref }). - 'lineage' — walk the HistoryMap for a named face ref ({ feature_id, ref }). All params except `mode` are forwarded verbatim.

  ConnectorNo auth

• resolve_channelA

  PoolParty Main Stage AirtimeA

  Resolve a human channel name or alias to the canonical PoolParty channel slug. PP0, Main Stage, and main resolve to "main"; PP1 resolves to "pp1". Read-only. No auth required.

  ConnectorNo auth

• get_research_claimA

  Kaal Corpus: Verifiable Claim LayerA

  Resolve one TrustCarry Protocol v0.3 research claim by full identifier or three-digit sequence.

  ConnectorNo auth

• resolve_incidentA

  validoria-mcpB

  Resolve an incident to mark it as handled. Changes status to RESOLVED and sets the closed timestamp.

  ConnectorNo auth

• profile_entity_idA

  ZooqA

  Resolve a public handle to the person entityId used by the live person endpoints (posts, comments, interests, lookalikes). Resolve once, reuse the id. (Costs 10 Zooq credits.)

  ConnectorNo auth

• companies_entity_idA

  ZooqA

  Resolve a company slug to the numeric organization id used by the live company endpoints (posts, similar, affiliated, insights). Resolve once, reuse the id. (Costs 10 Zooq credits.)

  ConnectorNo auth

• profile_entity_idA

  ZOOQ - LinkedIn Data for AI AgentsA

  Resolve a public handle to the person entityId used by the live person endpoints (posts, comments, interests, lookalikes). Resolve once, reuse the id. (Costs 10 Zooq credits.)

  ConnectorNo auth

• companies_entity_idA

  ZOOQ - LinkedIn Data for AI AgentsA

  Resolve a company slug to the numeric organization id used by the live company endpoints (posts, similar, affiliated, insights). Resolve once, reuse the id. (Costs 10 Zooq credits.)

  ConnectorNo auth