Is the Stackresolve MCP server down?

mcp-registry/dev.stackresolve/stackresolve · v0.1.0

Also listed as github/autorevai/stackresolve

healthy
Last checked 2026-10-20 17:20 UTC · handshake 156ms

As of 2026-10-20 17:20 UTC, the Stackresolve MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

uptime (30d checks)
100%
checks observed
3,991
outages (90d)
1
tools
15

Find, compare, and audit software for AI agents. Scored registry of tools and MCP servers.

Install Stackresolve MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http stackresolve-mcp-server https://mcp.stackresolve.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "stackresolve-mcp-server": {
      "type": "http",
      "url": "https://mcp.stackresolve.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (67/100)

D (67/100): 0 error(s), 4 warning(s) across 15 tool(s); ~1,455 tokens of tool definitions.
Scores higher than 2% of 15,413 MCP servers Glimind has audited.
Its tool list costs an agent ~1,455 tokens per session — lighter than 60% of servers.
67 → 67 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions17
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

15 of 15 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: audit, compare_companies, compare_products, find_competitors, find_tools_for_task and 10 more

31 parameter(s) across 14 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: audit, compare_companies, compare_products, find_competitors, find_tools_for_task and 9 more

1 tool(s) have descriptions under 20 characters.

Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →

Tools: get_pricing

Handshake + tools/list takes ~1,774 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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 →

Auto-fix: 11 corrected tool definitions

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

compare_companies 1 change
{
  "name": "compare_companies",
  "description": "Structured side-by-side of companies across fields (description, products, categories, funding, technology).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "domains"
    ],
    "properties": {
      "fields": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "domains": {
        "type": "array",
        "items": {
          "type": "string"
        }
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
compare_products 1 change
{
  "name": "compare_products",
  "description": "Compare products by slug.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "slugs"
    ],
    "properties": {
      "slugs": {
        "type": "array",
        "items": {
          "type": "string"
        }
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
find_competitors 1 change
{
  "name": "find_competitors",
  "description": "Real competitors and alternatives for a company, extracted from live research and returned as structured rows.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "domain"
    ],
    "properties": {
      "limit": {
        "type": "number"
      },
      "domain": {
        "type": "string"
      }
    },
    "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/dev.stackresolve/stackresolve"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.stackresolve/stackresolve"}) 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%2Fdev.stackresolve%2Fstackresolve.svg)](https://glimind.com/server/mcp-registry%2Fdev.stackresolve%2Fstackresolve?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.stackresolve%2Fstackresolve?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.stackresolve%2Fstackresolve.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.stackresolve%2Fstackresolve.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.stackresolve%2Fstackresolve?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:35542604989462bf…, first seen 2026-10-17, included at leaf 11912 of 34,093. Version history · verify what your client received.

Tools (15)

Compare: most reliable security servers · most reliable research servers · most reliable data servers · most reliable search servers · most reliable code 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 Stackresolve MCP server down right now?

As of 2026-10-20 17:20 UTC, the Stackresolve MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

How many tools does Stackresolve MCP server provide?

Stackresolve MCP server advertises 15 tools, including audit, compare_companies, compare_products, find_competitors, find_tools_for_task.

How do I install Stackresolve MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.stackresolve.dev/mcp

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

Glimind scanned all 15 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 Stackresolve 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