Home / MCP registry index / ai.buildersinfintech/fintech-data

Builders in Fintech

ai.buildersinfintech/fintech-data in the official MCP registry. Endpoint https://buildersinfintech.ai/mcp.

The registry describes it as: Fintech companies, products, investors, funding rounds, news, podcast. Free, keyless, CC BY 4.0.

We read its 23 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

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

search_organizations get_organization search_people get_person list_funding_rounds largest_rounds most_active_investors funding_summary get_funding_index get_investor_scorecard search_products get_product find_providers list_provider_filters search_content get_content search_podcast_knowledge list_events list_topics list_countries get_daily_digest list_raising about

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/ai-buildersinfintech-fintech-data/badge.svg)](https://lazaretto.dev/mcp-registry/ai-buildersinfintech-fintech-data)

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.