Home / MCP registry index / io.github.snefhew/factline-kyc

Factline KYC, KYB and agent payments

io.github.snefhew/factline-kyc in the official MCP registry. Endpoint https://factline.dev/mcp/kyc.

The registry describes it as: Supplier, company, sanctions, PEP, VAT and IBAN checks for agents. 5 checks a day free, no key.

We read its 31 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

x402_pay_guard x402_sellers get_trial_key eu_exchange_rates eu_law_lookup eu_vat_check eu_sanctions_screen eu_sanctions_batch us_trade_screen china_supplier_check us_company_lookup company_lookup eu_sanctions_wallet eu_tenders_search nl_insolvency_check pep_screen pep_batch domain_check iban_check peppol_lookup supplier_invoice_check eu_eori_check email_verify phone_verify self_hosted_wallet_evidence watch_30_days x402_payee_check company_dossier company_health eu_company_check kyc_check

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-snefhew-factline-kyc/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-snefhew-factline-kyc)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.