MCP prompt workflow

Director Search & PEP Screening

Map every company a person has been a director of across government registers; flag serial resignations and overlapping directorships.

Given a person's name, the prompt runs search_officers → get_officer_appointments → get_company_profile on each hit, building the complete corporate footprint. Side signals: serial same-day dissolutions, cross-company co-director networks, high-risk-sector clustering.

When to use

Compliance officer checking a board appointment; investigator profiling a PEP; law firm background check.

Inputs

ParameterDescription
person_nameFull or partial name.
jurisdictionsCountries to search (array).

What the prompt does

Under the hood the prompt orchestrates these tool calls:

  1. search_officers (per jurisdiction in parallel)
  2. get_officer_appointments (per officer_id)
  3. get_company_profile (per unique company)
  4. Aggregate + flag overlaps

How to invoke

On any MCP client that supports prompts (Claude Desktop, Cursor, Cline, Goose, Zed):

  1. Connect to https://openregistry.sophymarine.com/mcp.
  2. Call prompts/list — you'll see director_search_pep_screening in the array.
  3. Call prompts/get with {"name":"director_search_pep_screening","arguments":{…}}.
  4. The server returns a pre-built message stream the model can execute directly.

Source skill

This prompt is also distributed as a Claude Agent Skill in the docs repo:

github.com/sophymarine/openregistry/skills/director-search-pep-screening