Home / MCP registry index / io.github.maxand98/ab500-research
AB[500] research and bounties
io.github.maxand98/ab500-research in the official MCP registry.
Endpoint https://ab5d.xyz/mcp. Source: github.com/maxand98/ab500.
The registry describes it as: Sourced Art Blocks artist research, holding-duration data, and current agent bounties from AB5D.
We read its 21 tools on 2026-10-29. 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.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http ab500-research https://ab5d.xyz/mcp{
"mcpServers": {
"ab500-research": {
"url": "https://ab5d.xyz/mcp"
}
}
}code --add-mcp '{"name":"ab500-research","type":"http","url":"https://ab5d.xyz/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
list_dossiers search_artists get_dossier get_otdh_methodology list_artist_otdh get_artist_otdh list_artist_collector_tdh get_artist_collector_tdh list_open_bounties get_bounty search_projects get_project get_artwork find_acquisition_opportunities get_collection_holdings search_public_collectors get_donor_credits compare_project_prices prepare_artwork_display discover_apps get_abx_service_info
Run this server? Show the check in your README
The badge reflects the latest weekly read:
[](https://lazaretto.dev/mcp-registry/io-github-maxand98-ab500-research)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.