Home / MCP registry index / io.github.assetfare/assetfare
AssetFare
io.github.assetfare/assetfare in the official MCP registry.
Endpoint https://api.assetfare.dev/mcp. Source: github.com/assetfare/assetfare-mcp.
The registry describes it as: Exact-amount top-two routing for six pilots; caller signs; AssetFare never signs or submits
We read its 11 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
assetfare_manifest assetfare_v2_capabilities assetfare_v2_route_selection assetfare_v2_quote_selected_candidate assetfare_v2_quote assetfare_v2_prepare assetfare_v2_session_create assetfare_v2_session_get assetfare_v2_session_observe_source assetfare_v2_session_observe_output assetfare_v2_session_refresh_action
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-assetfare-assetfare)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.