StackResolve MCP server

Which servers in the official MCP registry are StackResolve's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to StackResolve

Whose server it is

Registry namedev.stackresolve/stackresolveverified in the MCP registry

The registry name sits under stackresolve.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19

Stateanswerschecked 2026-10-19
Tools15
Server calls itselfstackresolve
Server version0.1.0
Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 86 ms.

Measured dailydaily checks: 1, the first on 2026-10-19

Answeredmeasuring1 of the 7 daily checks it takes to print a share
Median first answer115 ms
Space in an agent's context≈ 1,311 tokensthe definitions of all its tools (15), which an agent carries on every turn
Tool definitionsC · 67 of 100

No description an agent can choose by: 1 of 15
Parameters without a description: in 14 of 15
Not saying whether it only reads or can destroy: 15 of 15

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers15 tools · read 2026-10-19

resolve
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)…
how_to
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…
find_tools_for_task
Rank the software an agent should use for a task.
search_tools
Search the registry by query + requirements (api/mcp/self_serve/openapi/cli).
compare_products
Compare products by slug.
get_profile
Full registry profile (AgentReady Score, capabilities, sources).
list_registry
List the registry, highest AgentReady Score first.
audit
Audit a product for agent-readiness.
generate_agent_interfaces
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.
get_company
Structured company record.
get_pricing
Normalized pricing.
research_company
Grounded, cited answer about a company.
find_competitors
Real competitors and alternatives for a company, extracted from live research and returned as structured rows.
compare_companies
Structured side-by-side of companies across fields (description, products, categories, funding, technology).
get_usage
Your usage this billing period (read-only).

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.