Home / MCP registry index / com.tabflows/site
Tabflows
com.tabflows/site in the official MCP registry.
Endpoint https://www.tabflows.com/api/mcp.
The registry describes it as: Tabflows facts: DPC Finder, price quotes, integrations, workflows, site search, demos, ask Tabflows
We read its 17 tools on 2026-10-27. 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_dpc_practices get_dpc_practice quote_tabflows_price list_integrations get_integration list_workflows search fetch get_page report_gap get_demo_booking_link dpc_break_even dpc_startup_cost get_demo_availability book_demo ask check_reply
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-tabflows-site)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.