zFinia Intelligence

Company KYB & Sanctions Check

company_evidence_pack

Company enrichment and KYB data for due diligence by domain: verify a counterparty, supplier or vendor before outreach, onboarding or payment. Returns firmographics (legal name, LEI, SEC CIK, industry, HQ, founded, employees), domain intelligence (age, email provider, SPF/DMARC), public role emails, socials, plus OFAC SDN and EU sanctions screening. Source-cited; unknowns null. Company data only, not personal contacts or compliance clearance. Unresolvable domains not charged. Pay 60000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "company_evidence_pack"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Company website domain or URL, e.g. "stripe.com" or "https://www.stripe.com/about".

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so: source-cited outputs, unknowns returned as null, unresolvable domains not charged, and the exact payment path (60000 atomic USDC on Base via exact x402) including the crucial caveat that the MCP does not pay and instead hands off a challenge. That is precisely the operational context an agent needs before invoking a paid endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose in the opening clause and follows with returns, boundaries, and payment terms — every element is load-bearing. It is dense, with returns and pricing packed into long clause chains, which slightly impedes scanning but wastes no sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description supplies both the return payload shape (firmographics, domain intel, role emails, socials, OFAC/EU sanctions) and the full commercial/authorization model. Nothing essential to correct invocation is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a single required parameter, so the schema already explains accepted domain/URL forms. The description adds only the phrase 'by domain,' which does not extend meaning beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-and-resource pair — company enrichment and KYB/sanctions screening by domain — and enumerates the returned data classes (firmographics, LEI/SEC CIK, domain intelligence, sanctions hits). It also draws its own boundary against the adjacent website_evidence_pack by declaring 'Company data only, not personal contacts or compliance clearance.' An agent can tell what this produces without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete triggering scenarios: 'verify a counterparty, supplier or vendor before outreach, onboarding or payment.' It also states a scope exclusion (not personal contacts, not compliance clearance). It stops short of naming a specific sibling alternative for the personal-contact or web-content cases, so routing is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All zFinia Intelligence tools Inspect

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

Need Help?