mcp-registry/io.github.rzere/mcpexplorer · v1.0.0
Also listed as mcp-registry/io.github.mcpexplorer/mcpexplorer
As of 2026-10-19 10:30 UTC, the Rzere Explorer MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
Claude Code
claude mcp add --transport http rzere-explorer-mcp-server https://mcpexplorer.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"rzere-explorer-mcp-server": {
"type": "http",
"url": "https://mcpexplorer.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
14 of 14 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 →
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 →
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. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.rzere%2Fmcpexplorer/fixes
{
"name": "check_trust",
"description": "Return the explainable trust score, label, scoring reasons, and verification history for an MCP server.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Server slug"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Check trust"
}{
"name": "compare_servers",
"description": "Compare two MCP servers side by side: trust, transport, tools, install, and links.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"a",
"b"
],
"properties": {
"a": {
"type": "string",
"description": "First server slug"
},
"b": {
"type": "string",
"description": "Second server slug"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Compare two MCP servers"
}{
"name": "generate_runtime_config",
"description": "Generate the install + client config for an MCP server in a given runtime (claude-desktop, cursor, vscode, windsurf, cline, continue, goose, openai-agents, langgraph, crewai).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"slug",
"runtime"
],
"properties": {
"slug": {
"type": "string",
"description": "Server slug"
},
"runtime": {
"type": "string",
"description": "Runtime slug, e.g. 'claude-desktop'"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": true
},
"title": "Generate MCP setup config"
}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.github.rzere/mcpexplorer"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.rzere/mcpexplorer"}) over MCP.
search_servers ~384 tokensplan_toolset ~275 tokensgenerate_runtime_config ~144 tokensget_loadout ~138 tokenslist_capabilities ~137 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.github.rzere%2Fmcpexplorer?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.rzere%2Fmcpexplorer?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.rzere%2Fmcpexplorer.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.rzere%2Fmcpexplorer.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.rzere%2Fmcpexplorer?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:d42f0c647aaaf42e…, first seen 2026-10-17, included at leaf 14408 of 26,188. Version history · verify what your client received.
Compare: most reliable security servers · most reliable devops servers · most reliable search servers · most reliable data servers · most reliable knowledge 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-19 10:30 UTC, the Rzere Explorer MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Rzere Explorer MCP server advertises 14 tools, including check_trust, compare_servers, generate_runtime_config, get_alternatives, get_capability.
Point your MCP client at this streamable-http endpoint: https://mcpexplorer.com/mcp
Glimind scanned all 14 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.