SolvScore vs MCP Installer
A side-by-side look at the SolvScore and MCP Installer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SolvScore for developer tools work over a hosted endpoint; choose MCP Installer for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SolvScore when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
SOLVSCORE_API. - You want tools like
get_solvscore_agent_dashboard, get_agent_credit_score, underwrite_agent_loan.
Choose MCP Installer when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
install_repo_mcp_server, install_local_mcp_server.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 55/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | SOLVSCORE_API | None listed |
Tools & capabilities
SolvScore tools 20
get_solvscore_agent_dashboard[FREE] SolvScore Agent Credit Dashboard (inv #4345): browse scored AI agents with filters — trust score range (0-100), reputation bond status (active|slashed), job, and sort (trust_score|credit|apr|name). Returns trust score, credit limit, APR, badges, bond status and profile links per agent. Snapshot re-scored every 6h.get_agent_credit_score[FREE] Look up an AI agent's SolvScore credit file before you transact with it. Accepts an agent name, id, or Base L2 wallet address. Returns trust_score (0-100), badges (reputation bonds held), a nested credit object carrying credit_limit and apr_bps, plus two counterparty red flags worth checking before you extend anything: sybil_flagged and cooling. Free and unauthenticated - no API key, no payment header.underwrite_agent_loan[FREE] Get a real underwriting decision on a loan to an AI agent. principal = requested loan size in USDC. tier1_value = optional collateral pledged in USDC (Coinbase B20 tokenized stocks or USDC on Base). Posting collateral moves the agent from the reputation tier to the hard tier: higher limit, lower APR. Returns approved (true/false), credit_limit_usdc, apr_pct, tier and a plain-language reason. Roughly half of all requests are declined, so treat a decline as real signal.register_agent[FREE] Open a SolvScore credit file for your own agent so it can be underwritten. Call this once before requesting credit, or whenever a score lookup returns no_such_agent: an agent must hold a credit file before the bureau will rate it. agent_name = the name your agent is known by (2-64 chars: letters, digits, space, dot, dash, underscore). wallet = optional Base L2 address as 0x followed by 40 hex characters. Supplying a wallet that already matches an agent with verified AgentWorld work history links that history to the new file immediately, so the file opens with real capacity instead of zero. harness = the framework running the agent: claude, chatgpt, codex, cursor, langchain, crewai, autogen, mcp, custom or other. contact = optional email or URL the bureau can reach you at. Returns credit_file_id, which you then pass as `agent` to get_agent_credit_score and underwrite_agent_loan, plus the opening state and next steps. Registration is idempotent: the same name or wallet returns the existing file rather than creating a duplicate. Expect a thin file. With no verified history a new agent opens at a 0 USDC reputation limit and the maximum APR, exactly as a credit bureau treats a borrower with no record. Two paths raise it: post collateral through underwrite_agent_loan's tier1_value to borrow on day one, and accrue verified completed work to earn reputation capacity. Free and unauthenticated - no API key, no payment header.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SolvScore
{
"mcpServers": {
"solvscore": {
"url": "https://solvscore.com/mcp"
}
}
}
MCP Installer
{
"mcpServers": {
"anaisbetts-mcp-installer": {
"command": "npx",
"args": [
"@anaisbetts/mcp-installer"
]
}
}
}
Frequently asked questions
SolvScore is categorized under Developer Tools and uses a remote HTTP/SSE transport. MCP Installer belongs to Developer Tools and uses a local stdio subprocess. Pick SolvScore for developer tools work and MCP Installer for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SolvScore has no declared pricing — check the project's own site. MCP Installer is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add solvscore and anaisbetts-mcp-installer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SolvScore has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. MCP Installer has 63/100 (Good) with 3 views, 0 installs and 1,531 GitHub stars.