StackResolve
REMOTE · MCP.STACKRESOLVE.DEV · SCANNED SEP 26
Find, compare, and audit software for AI agents. Scored registry of tools and MCP servers.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 671 tokens (~44/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcp.stackresolve.dev
claude mcp add --transport http dev-stackresolve-stackresolve 'https://mcp.stackresolve.dev/mcp'
{
"mcpServers": {
"dev-stackresolve-stackresolve": {
"url": "https://mcp.stackresolve.dev/mcp"
}
}
} {
"servers": {
"dev-stackresolve-stackresolve": {
"type": "http",
"url": "https://mcp.stackresolve.dev/mcp"
}
}
} [mcp_servers.dev-stackresolve-stackresolve] url = "https://mcp.stackresolve.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-stackresolve-stackresolve": {
"type": "remote",
"url": "https://mcp.stackresolve.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-stackresolve-stackresolve --url 'https://mcp.stackresolve.dev/mcp' --transport streamable-http
mcp_servers:
dev-stackresolve-stackresolve:
url: "https://mcp.stackresolve.dev/mcp" {
"McpServers": {
"dev-stackresolve-stackresolve": {
"Transport": "http",
"Url": "https://mcp.stackresolve.dev/mcp"
}
}
} assistant mcp add dev-stackresolve-stackresolve -t streamable-http -u 'https://mcp.stackresolve.dev/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: 0.97 → pass security
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://mcp.stackresolve.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.stackresolve.dev | CN=YE2,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 69cbb2aa214d3d834880d172f2c814c6f29 |
| SANs: mcp.stackresolve.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.stackresolve.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| stackresolve.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.stackresolve.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.stackresolve.dev/mcp | HTTPS enforced | 301 | https://mcp.stackresolve.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit ~22
Audit a product for agent-readiness.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
compare_companies ~42
Structured side-by-side of companies across fields (description, products, categories, funding, technology).
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | – |
| fields | array | – | – |
No output schema declared.
No examples provided.
compare_products ~21
Compare products by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | – |
No output schema declared.
No examples provided.
find_competitors ~42
Real competitors and alternatives for a company, extracted from live research and returned as structured rows.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
find_tools_for_task ~28
Rank the software an agent should use for a task.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | – |
No output schema declared.
No examples provided.
generate_agent_interfaces ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| openapiUrl | string | – | – |
No output schema declared.
No examples provided.
get_company ~19
Structured company record.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_pricing ~20
Normalized pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_profile ~27
Full registry profile (AgentReady Score, capabilities, sources).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_usage ~17
Your usage this billing period (read-only).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
how_to ~87
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | – |
No output schema declared.
No examples provided.
list_registry ~40
List the registry, highest AgentReady Score first.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | number | – | – |
| minScore | number | – | – |
No output schema declared.
No examples provided.
research_company ~31
Grounded, cited answer about a company.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| question | string | – | – |
No output schema declared.
No examples provided.
resolve ~137
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).
| Name | Type | Req | Description |
|---|---|---|---|
| api | boolean | – | – |
| cli | boolean | – | – |
| discover | boolean | – | – |
| mcp | boolean | – | – |
| openapi | boolean | – | – |
| self_serve | boolean | – | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
search_tools ~73
Search the registry by query + requirements (api/mcp/self_serve/openapi/cli).
| Name | Type | Req | Description |
|---|---|---|---|
| api | boolean | – | – |
| cli | boolean | – | – |
| mcp | boolean | – | – |
| openapi | boolean | – | – |
| query | string | yes | – |
| self_serve | boolean | – | – |
No output schema declared.
No examples provided.
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.