Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

StackResolve

REMOTE · MCP.STACKRESOLVE.DEV

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

0 this week 74 Trust /100

Last scanned (16 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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
Transport & Reachability100
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 28 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
  • 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 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 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=api.stackresolve.dev CN=Amazon RSA 2048 M04,O=Amazon,C=US 22 Oct 2026 7 May 2027 RSA 2048 SHA256-RSA e9c7c273ddde4df7c45d142e3814f4a
SANs: api.stackresolve.dev, mcp.stackresolve.dev
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

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. DS published 60074 8 Verified
stackresolve.dev. No DS 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:443/mcp
MCP tools · 15 exposed · ~671 tokens

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 →

Tool Tokens
audit ~22

Audit a product for agent-readiness.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

compare_companies ~42

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

NameTypeReqDescription
domainsarrayyes–
fieldsarray––

No output schema declared.

No examples provided.

compare_products ~21

Compare products by slug.

NameTypeReqDescription
slugsarrayyes–

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.

NameTypeReqDescription
domainstringyes–
limitnumber––

No output schema declared.

No examples provided.

find_tools_for_task ~28

Rank the software an agent should use for a task.

NameTypeReqDescription
taskstringyes–

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.

NameTypeReqDescription
domainstringyes–
openapiUrlstring––

No output schema declared.

No examples provided.

get_company ~19

Structured company record.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

get_pricing ~20

Normalized pricing.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

get_profile ~27

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

NameTypeReqDescription
slugstringyes–

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 }.

NameTypeReqDescription
taskstringyes–

No output schema declared.

No examples provided.

list_registry ~40

List the registry, highest AgentReady Score first.

NameTypeReqDescription
categorystring––
limitnumber––
minScorenumber––

No output schema declared.

No examples provided.

research_company ~31

Grounded, cited answer about a company.

NameTypeReqDescription
domainstringyes–
questionstring––

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).

NameTypeReqDescription
apiboolean––
cliboolean––
discoverboolean––
mcpboolean––
openapiboolean––
self_serveboolean––
taskstringyes–

No output schema declared.

No examples provided.

search_tools ~73

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

NameTypeReqDescription
apiboolean––
cliboolean––
mcpboolean––
openapiboolean––
querystringyes–
self_serveboolean––

No output schema declared.

No examples provided.

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.

remote · mcp.stackresolve.dev

# add to Claude Code
claude mcp add --transport http dev-stackresolve-stackresolve 'https://mcp.stackresolve.dev/mcp'
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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the StackResolve MCP server?

VerifyMCP ran 12 checks on StackResolve, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about StackResolve: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.