Home / MCP registry index / io.github.Bahamas1717/aibvf-mcp
io.github.Bahamas1717/aibvf-mcp
io.github.Bahamas1717/aibvf-mcp in the official MCP registry.
Endpoint https://mcp.aibvf.com/api/mcp. Source: github.com/Bahamas1717/ai-bvf.
The registry describes it as: AI BVF: score AI portfolios Stop/Fix/Accelerate with decision confidence and pace-layer drag.
We read its 13 tools on 2026-10-26. 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
assess_ai_initiative score_initiative score_portfolio recommend_improvements calculate_pace_layer_drag validate_portfolio get_benchmark list_taxonomy diagnose_process infer_readiness sequence_portfolio map_to_taxonomy assemble_portfolio
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-bahamas1717-aibvf-mcp)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.