Home / MCP registry index / com.solvscore/mcp
SolvScore
com.solvscore/mcp in the official MCP registry.
Endpoint https://solvscore.com/mcp. Source: github.com/shawnhvac/solvscore-mcp.
The registry describes it as: Credit scores for AI agents. Underwrite an unknown counterparty before extending credit.
We read its 20 tools on 2026-10-28. 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
get_solvscore_agent_dashboard get_agent_credit_score underwrite_agent_loan register_agent get_credit_improvement_path get_credit_market_stats get_credit_leaderboard get_agent_attestations get_scoring_weights get_solvscore_receipts verify_solvscore_receipt solv_program_info solv_register_wallet solv_buy_kit solv_snapshot_and_distribution get_solv_quote get_kya_credential solv_rebate_rounds solv_rebate_round_detail get_liquidity_stress_test
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-solvscore-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.