mcp-registry/io.autosophia/solana-lens · v1.29.0
As of 2026-10-26 20:03 UTC, the Autosophia Solana Lens MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
Screen tokens, inspect wallets, simulate transactions, price priority fees. $0.02 in USDC.
Point your MCP client at this streamable-http endpoint: https://chain.autosophia.io/mcp
8 of 8 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 →
8 parameter(s) across 5 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 →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.autosophia%2Fsolana-lens/fixes
{
"name": "health",
"description": "RPC connectivity check. Free. Use when diagnosing timeouts before paid calls.",
"inputSchema": {
"type": "object",
"title": "healthArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "payment_info",
"description": "How to pay, step by step. Read this if you got a 402 and are not sure what to do.",
"inputSchema": {
"type": "object",
"title": "payment_infoArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "service_info",
"description": "Start here. What this server sells, what it will not do, and the exact limits.",
"inputSchema": {
"type": "object",
"title": "service_infoArguments",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}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/io.autosophia/solana-lens"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.autosophia/solana-lens"}) over MCP.
screen_token ~190 tokenssimulate_transaction ~184 tokensrequest_capability ~182 tokenspriority_fee ~174 tokensinspect_wallet ~171 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fio.autosophia%2Fsolana-lens?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.autosophia%2Fsolana-lens?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.autosophia%2Fsolana-lens.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.autosophia%2Fsolana-lens.svg :target: https://glimind.com/server/mcp-registry%2Fio.autosophia%2Fsolana-lens?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:72fc59e3a072da1e…, first seen 2026-10-17, included at leaf 4303 of 75,178. Version history · verify what your client received.
Compare: most reliable devops servers · most reliable data servers · most reliable knowledge servers · most reliable other servers · most reliable security servers
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.
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"
}
}
}
As of 2026-10-26 20:03 UTC, the Autosophia Solana Lens MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
Autosophia Solana Lens MCP server advertises 8 tools, including health, inspect_wallet, payment_info, priority_fee, request_capability.
Point your MCP client at this streamable-http endpoint: https://chain.autosophia.io/mcp
Glimind scanned all 8 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.
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.