Is the Solvscore MCP server down?

mcp-registry/com.solvscore/mcp · v3.2.4

Also listed as github/shawnhvac/solvscore-mcp, glama/shawnhvac/solvscore-mcp

healthy
Last checked 2026-10-27 07:00 UTC · handshake 55ms

As of 2026-10-27 07:00 UTC, the Solvscore MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
99.7%
checks observed
4,968
outages (90d)
13
tools
20

Credit scores for AI agents. Underwrite an unknown counterparty before extending credit.

Point your MCP client at this streamable-http endpoint: https://solvscore.com/mcp

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 3 warning(s) across 20 tool(s); ~2,958 tokens of tool definitions.
Scores higher than 10% of 15,779 MCP servers Glimind has audited.
Its tool list costs an agent ~2,958 tokens per session — more than 50% of servers.
74 → 75 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions38
Safety hints16
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (3)

20 of 20 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_agent_attestations, get_agent_credit_score, get_credit_improvement_path, get_credit_leaderboard, get_credit_market_stats and 15 more

29 parameter(s) across 15 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_agent_attestations, get_agent_credit_score, get_credit_improvement_path, get_credit_leaderboard, get_kya_credential and 10 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: solv_buy_kit

Auto-fix: 13 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 15 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.solvscore%2Fmcp/fixes

get_agent_attestations 1 change
{
  "name": "get_agent_attestations",
  "description": "[FREE] Read the onchain attestations naming an AI agent's wallet on Base, and what they\nare worth in SolvScore's underwriting. Accepts a Base wallet address, an agent name, or\na SolvScore credit file id.\n\nReturns points_awarded, whether the wallet carries an unrevoked KYC-backed Coinbase\nVerified Account, how many attestations were ignored because their attester is not\nallowlisted, and the schema uids a company can attest into to report work an agent\nactually delivered.\n\nCheck this before extend",
  "inputSchema": {
    "type": "object",
    "required": [
      "agent_or_wallet"
    ],
    "properties": {
      "agent_or_wallet": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_agent_credit_score 1 change
{
  "name": "get_agent_credit_score",
  "description": "[FREE] Look up an AI agent's SolvScore credit file before you transact with it.\nAccepts an agent name, id, or Base L2 wallet address.\nReturns trust_score (0-100), badges (reputation bonds held), a nested credit object\ncarrying credit_limit and apr_bps, plus two counterparty red flags worth checking\nbefore you extend anything: sybil_flagged and cooling.\nFree and unauthenticated - no API key, no payment header.",
  "inputSchema": {
    "type": "object",
    "required": [
      "agent"
    ],
    "properties": {
      "agent": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_credit_improvement_path 1 change
{
  "name": "get_credit_improvement_path",
  "description": "Counterfactual credit explanation: the minimal quantified actions an agent\ncan take to improve its SolvScore status. Free. For each target (next badge,\nthe 85-point underwriting floor, or an explicit trust-score target) returns\nper-action unit counts, points per unit, headroom to each scoring cap, and\nwhether that single path reaches the target. Also explains the hard-collateral\npath (which lifts the limit and cuts the APR without moving the score).",
  "inputSchema": {
    "type": "object",
    "required": [
      "agent"
    ],
    "properties": {
      "agent": {
        "type": "string"
      },
      "target": {
        "type": "number",
        "default": 0
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.solvscore/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.solvscore/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.solvscore%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.solvscore%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.solvscore%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.solvscore%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.solvscore%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.solvscore%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a8452426002752f7…, first seen 2026-10-17, included at leaf 9812 of 77,973. Version history · verify what your client received.

Tools (20)

Compare: most reliable finance servers · most reliable retrieval servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Solvscore MCP server down right now?

As of 2026-10-27 07:00 UTC, the Solvscore MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Solvscore MCP server provide?

Solvscore MCP server advertises 20 tools, including get_agent_attestations, get_agent_credit_score, get_credit_improvement_path, get_credit_leaderboard, get_credit_market_stats.

How do I install Solvscore MCP server?

Point your MCP client at this streamable-http endpoint: https://solvscore.com/mcp

Is the Solvscore MCP server safe to connect to an AI agent?

Glimind scanned all 20 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Solvscore MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve