← Registry

Developer Tools

stackresolve.dev

Discovers, ranks, and compares software tools and APIs for a task, providing current best practices and recommendations for AI agents.

1 endpoint15 known toolsFirst detected August 25, 2026Last detected September 6, 2026

ENDPOINT 1

https://mcp.stackresolve.dev/mcp

No auth detected

MCP server metadata

Name
stackresolve
Version
0.1.0
Capabilities
tools.listChanged

Known tools 15

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.

Inferred read-only
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.

Inferred read-only
find_tools_for_task

Rank the software an agent should use for a task.

Inferred read-only
search_tools

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

Inferred read-only
compare_products

Compare products by slug.

Inferred read-only
get_profile

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

Inferred read-only
list_registry

List the registry, highest AgentReady Score first.

Inferred read-only
audit

Audit a product for agent-readiness.

Inferred read-only
generate_agent_interfaces

Make a product agent-native: from its OpenAPI, generate an MCP server (one tool per operation), a CLI, an llms.

Inferred read-only
get_company

Structured company record.

Inferred read-only
get_pricing

Normalized pricing.

Inferred read-only
research_company

Grounded, cited answer about a company.

Inferred read-only
find_competitors

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

Inferred read-only
compare_companies

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

Inferred read-only
get_usage

Your usage this billing period (read-only).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.stackresolve]
url = "https://mcp.stackresolve.dev/mcp"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: stackresolve
Remote MCP URL: https://mcp.stackresolve.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "stackresolve": {
      "url": "https://mcp.stackresolve.dev/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "stackresolve": {
      "type": "http",
      "url": "https://mcp.stackresolve.dev/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "stackresolve",
  "transport": "streamable-http",
  "url": "https://mcp.stackresolve.dev/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.