Home / MCP registry index / io.github.tonyback0101-cmyk/buyer-intelligence

io.github.tonyback0101-cmyk/buyer-intelligence

io.github.tonyback0101-cmyk/buyer-intelligence in the official MCP registry. Endpoint https://www.procureradar.com/api/mcp. Source: github.com/tonyback0101-cmyk/procureradar-mcp-server.

The registry describes it as: Find verified global B2B buyers by category & country. Free anonymous discovery. SGX-listed.

We read its 13 tools on 2026-10-22. 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

find_buyers enrich_buyer_contact analyze_buyer_intelligence submit_discovery_job check_discovery_task list_group_buy_pools search_products search_stores request_quote list_quotes place_order create_payment_mandate list_payment_mandates

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-tonyback0101-cmyk-buyer-intelligence/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-tonyback0101-cmyk-buyer-intelligence)

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.