Skip to main content
Glama

ARM Verify — Entity Intelligence API

by app.railway.up.brilliant-illumination-production-9bda
OverviewDiscussionsAdmin

map_ownership

Trace the corporate ownership chain above a company and identify the natural persons who ultimately control it. RETURNS JSON with: ownership_chain (array of parent entities, each with name, relationship, jurisdiction and is_ubo_candidate), natural_persons (array of identified beneficial owners, each with name, nationality and natures_of_control such as "ownership-of-shares-75-to-100-percent"), lei of the subject entity, complexity ("SIMPLE", "COMPLEX" or "UNKNOWN"), data_confidence ("HIGH", "MEDIUM" or "LOW") and notes describing the chain depth found. SOURCES: GLEIF Relationship API for LEI parent-child records, Companies House PSC (People with Significant Control) Register for UK entities, and the OpenCorporates corporate network. USE WHEN beneficial-ownership disclosure is required under AML or KYC rules, or to detect ownership by a sanctioned parent. BILLING: with an API key each call is charged $12.00 from the key's credits, exactly as POST /verify (refused when the balance is too low); bank portal sessions are not charged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNoRequested ownership-chain depth, 1 to 3 (1 = immediate parent only, 3 = up to three levels up). Example: 2. Accepted for forward compatibility but NOT yet enforced — the current implementation returns the full chain it can discover from the available sources regardless of this value.
entity_nameYesFull registered company name of the subsidiary or subject company whose owners you want. Example: "Volkswagen AG".
jurisdictionYesISO 3166-1 alpha-2 country code of incorporation, uppercase. Examples: "GB", "DE", "US", "NL". UK entities ("GB") return the richest data because the PSC Register is queried in addition to GLEIF.
registration_numberNoOptional national company number. Strongly recommended for UK entities, where it makes the PSC Register lookup exact instead of name-based. Example: "00445790" (GB, 8 digits). Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / depth / description
      Previous value: -"Ownership chain depth (1-3)"New value: +"Requested ownership-chain depth, 1 to 3 (1 = immediate parent only, 3 = up to three levels up). Example: 2. Accepted for forward compatibility but NOT yet enforced — the current implementation returns the full chain it can discover from the available sources regardless of this value."
    • changedInput schema / properties / depth / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / entity_name / description
      Previous value: -"Company name"New value: +"Full registered company name of the subsidiary or subject company whose owners you want. Example: \"Volkswagen AG\"."
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"ISO 2-letter country code (e.g. GB, DE, US)"New value: +"ISO 3166-1 alpha-2 country code of incorporation, uppercase. Examples: \"GB\", \"DE\", \"US\", \"NL\". UK entities (\"GB\") return the richest data because the PSC Register is queried in addition to GLEIF."
    • changedInput schema / properties / registration_number / description
      Previous value: -"Company registration number — improves UK PSC lookup accuracy"New value: +"Optional national company number. Strongly recommended for UK entities, where it makes the PSC Register lookup exact instead of name-based. Example: \"00445790\" (GB, 8 digits). Omit if unknown."
  2. Changed4 schema fields changed
    • addedInput schema / properties / depth / description
      Added value: +"Ownership chain depth (1-3)"
    • addedInput schema / properties / entity_name / description
      Added value: +"Company name"
    • addedInput schema / properties / jurisdiction / description
      Added value: +"ISO 2-letter country code (e.g. GB, DE, US)"
    • addedInput schema / properties / registration_number / description
      Added value: +"Company registration number — improves UK PSC lookup accuracy"
  3. Changed4 schema fields changed
    • removedInput schema / properties / depth / description
      Removed value: -"Ownership chain depth (1-3)"
    • removedInput schema / properties / entity_name / description
      Removed value: -"Company name"
    • removedInput schema / properties / jurisdiction / description
      Removed value: -"ISO 2-letter country code (e.g. GB, DE, US)"
    • removedInput schema / properties / registration_number / description
      Removed value: -"Company registration number — improves UK PSC lookup accuracy"
  4. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"ISO 2-letter country code"New value: +"ISO 2-letter country code (e.g. GB, DE, US)"
    • addedInput schema / properties / registration_number
      Added value: +{
+  "description": "Company registration number — improves UK PSC lookup accuracy",
+  "type": "string"
+}
  5. First observed

TDQS

Score is being calculated.

All ARM Verify — Entity Intelligence API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources