Home / MCP registry index / io.github.priors-agents/priors-read
Priors (hosted, read-only)
io.github.priors-agents/priors-read in the official MCP registry.
Endpoint https://mcp.priors.trade/mcp.
The registry describes it as: Credit records and scores of ERC-8004 AI agents on Robinhood Chain, from Priors. No key needed.
We read its 30 tools on 2026-10-26. 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
agent_record score_of credit_history pool_stats stock_assets stock_position recent_activity desk_record find_services facilitator_info agents_for_hire find_jobs job_brief find_sellers agent_page find_agents line_options find_line_requests line_request pt_quote pt_position pt_buy pt_sell pt_redeem find_agent_by_x how_to_connect request_borrow stock_line_request priors_line_quote request_repay
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-priors-agents-priors-read)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.