# StackResolve (remote · mcp.stackresolve.dev)

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

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `mcp.stackresolve.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/dev-stackresolve-stackresolve/mcp.md), [page](https://verifymcp.io/servers/dev-stackresolve-stackresolve/mcp)

## Channel facts

- Endpoint: `https://mcp.stackresolve.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 671 tokens (~44/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the StackResolve MCP server?

StackResolve is a hosted endpoint at https://mcp.stackresolve.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-stackresolve-stackresolve 'https://mcp.stackresolve.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-stackresolve-stackresolve": {
      "url": "https://mcp.stackresolve.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-stackresolve-stackresolve": {
      "type": "http",
      "url": "https://mcp.stackresolve.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-stackresolve-stackresolve]
url = "https://mcp.stackresolve.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-stackresolve-stackresolve": {
      "type": "remote",
      "url": "https://mcp.stackresolve.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-stackresolve-stackresolve --url 'https://mcp.stackresolve.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-stackresolve-stackresolve:
    url: "https://mcp.stackresolve.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-stackresolve-stackresolve": {
      "Transport": "http",
      "Url": "https://mcp.stackresolve.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-stackresolve-stackresolve -t streamable-http -u 'https://mcp.stackresolve.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 74, +1)

- [security] Stability: 0.97 → pass

### 2026-09-22 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (15)

### `resolve` (~137 tokens)

Best tools for a natural-language task: resolves the task to the capabilities it needs, returns products that expose them ranked by fit and AgentReady score, each with a reason. Optional requirements (api/mcp/self_serve/openapi/cli) filter candidates. Set discover:true to search the web and audit new products into the registry when coverage is thin (slower, costs more).

Input parameters:

- `api` (boolean)
- `cli` (boolean)
- `discover` (boolean)
- `mcp` (boolean)
- `openapi` (boolean)
- `self_serve` (boolean)
- `task` (string, required)

### `how_to` (~87 tokens)

BEFORE building something, call this: returns the CURRENT (date-stamped), cited, tool-aware way to do a task, so you build from today's best practice instead of training-cutoff memory. Composes live web research + the tool resolver + one synthesis pass into { approach, recommendedTools, steps, gotchas, deprecated, sources, asOf }.

Input parameters:

- `task` (string, required)

### `find_tools_for_task` (~28 tokens)

Rank the software an agent should use for a task.

Input parameters:

- `task` (string, required)

### `search_tools` (~73 tokens)

Search the registry by query + requirements (api/mcp/self_serve/openapi/cli).

Input parameters:

- `api` (boolean)
- `cli` (boolean)
- `mcp` (boolean)
- `openapi` (boolean)
- `query` (string, required)
- `self_serve` (boolean)

### `compare_products` (~21 tokens)

Compare products by slug.

Input parameters:

- `slugs` (array, required)

### `get_profile` (~27 tokens)

Full registry profile (AgentReady Score, capabilities, sources).

Input parameters:

- `slug` (string, required)

### `list_registry` (~40 tokens)

List the registry, highest AgentReady Score first.

Input parameters:

- `category` (string)
- `limit` (number)
- `minScore` (number)

### `audit` (~22 tokens)

Audit a product for agent-readiness.

Input parameters:

- `domain` (string, required)

### `generate_agent_interfaces` (~65 tokens)

Make a product agent-native: from its OpenAPI, generate an MCP server (one tool per operation), a CLI, an llms.txt, and Claude Code/Codex/Cursor install snippets.

Input parameters:

- `domain` (string, required)
- `openapiUrl` (string)

### `get_company` (~19 tokens)

Structured company record.

Input parameters:

- `domain` (string, required)

### `get_pricing` (~20 tokens)

Normalized pricing.

Input parameters:

- `domain` (string, required)

### `research_company` (~31 tokens)

Grounded, cited answer about a company.

Input parameters:

- `domain` (string, required)
- `question` (string)

### `find_competitors` (~42 tokens)

Real competitors and alternatives for a company, extracted from live research and returned as structured rows.

Input parameters:

- `domain` (string, required)
- `limit` (number)

### `compare_companies` (~42 tokens)

Structured side-by-side of companies across fields (description, products, categories, funding, technology).

Input parameters:

- `domains` (array, required)
- `fields` (array)

### `get_usage` (~17 tokens)

Your usage this billing period (read-only).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-stackresolve-stackresolve/mcp#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 72
- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 69
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 66
- 2026-09-07: 66
- 2026-09-06: 65
- 2026-09-05: 65
- 2026-09-04: 64
- 2026-09-03: 64
- 2026-09-02: 63
- 2026-09-01: 63
- 2026-08-31: 62
- 2026-08-30: 62
- 2026-08-29: 62
- 2026-08-28: 61

## Common questions

### What is the StackResolve MCP server?

StackResolve is an MCP server listed in the public MCP registry as dev.stackresolve/stackresolve. Find, compare, and audit software for AI agents. Scored registry of tools and MCP servers. This page covers its hosted endpoint (https://mcp.stackresolve.dev/mcp).

### Is the StackResolve MCP server safe to use?

StackResolve scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the StackResolve MCP server expose?

StackResolve exposes 15 tools: resolve, how_to, find_tools_for_task, search_tools, compare_products, and 10 more. Their descriptions and schemas cost roughly 671 tokens of context every time the server is loaded.

### Does the StackResolve MCP server require authentication?

No. We connected to StackResolve without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the StackResolve MCP server still maintained?

StackResolve is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.stackresolve.dev/mcp
- Repository: https://github.com/autorevai/stackresolve
- Website: https://stackresolve.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-stackresolve-stackresolve/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-stackresolve-stackresolve/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-stackresolve-stackresolve/mcp