dev.stackresolvePublished by stackresolve.devOfficial publisherv0.4.0Updated Oct 24, 2026
Find, compare, and audit software for AI agents. Scored registry of tools and MCP servers.
Remote MCP server for finding, comparing and auditing software and MCP servers for AI agents, plus structured company research.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.stackresolve%2Fstackresolve/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"stackresolve": {
"type": "http",
"url": "https://mcp.stackresolve.dev/mcp"
}
}
}Official TypeScript/Node SDK for the StackResolve API.
StackResolve helps agents discover, evaluate, select, install, and use software (AgentReady), and compresses web research into structured company data calls (CompanyData). This SDK is a thin, typed wrapper over the live REST API.
That mints an API key if you have none, registers the hosted MCP server for every coding
agent on the machine (Claude Code, Cursor, Codex, Windsurf, VS Code), writes the
StackResolve skill to ~/.claude/skills/stackresolve/SKILL.md, and verifies the key
against the API. It is safe to re-run, and it backs up every file it changes.
The hosted server needs no install. The handshake and the registry reads (search_tools,
get_profile, compare_products, list_registry) work without a key. Metered tools
(resolve, how_to, audit, research_company, get_company, get_pricing) need a free
key from https://stackresolve.dev/developers, sent as the x-api-key header.
Claude Code:
Cursor (~/.cursor/mcp.json):
Codex (~/.codex/config.toml):
Tools: resolve, how_to, find_tools_for_task, search_tools, compare_products,
get_profile, list_registry, audit, generate_agent_interfaces, get_company,
get_pricing, research_company, find_competitors, compare_companies, get_usage.
Requires Node 18+ (uses the built-in global fetch). No runtime dependencies.
Get an API key at stackresolve.dev. Pass it to the
constructor, or set the STACKRESOLVE_API_KEY environment variable:
The key is sent as the x-api-key header on every request. Public endpoints
(audit, search, profiles, company data, ...) work without a key, subject to an
anonymous rate limit. Gated endpoints (monitors, usage, discovery runs) need one.
You can point the client at a different host with baseUrl or the
STACKRESOLVE_BASE_URL environment variable:
Any non-2xx response throws a StackResolveError carrying the HTTP status and
the parsed body:
AgentReady:
audit(domain), findTools(task), search(query, requirements?),
compare(slugs), getProfile(slug), listRegistry(opts?), getCategories(),
getCategory(slug), getDiscovery(slug), runDiscovery(slug),
getScoreHistory(slug), generate(domain, openapiUrl?), deploy(domain, openapiUrl?).
CompanyData:
getCompany(domain), getPricing(domain), getCompetitors(domain),
research(domain, question?), compareCompanies(domains).
Monitors + account (API key required):
listMonitors(), addMonitor(slug, opts?), runMonitorNow(slug),
getUsage(), getMyProfile().
Python SDK:
LangChain tools, so an agent can pick software and research companies without a search-and-scrape loop:
REST directly: https://api.stackresolve.dev, OpenAPI at /openapi.json, llms.txt at
/llms.txt.
MIT
Source: README.md at commit 3b3a585
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).
apiclimcptaskrequiredopenapidiscoverself_serveBEFORE 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 }.
taskrequiredRank the software an agent should use for a task.
taskrequiredSearch the registry by query + requirements (api/mcp/self_serve/openapi/cli).
apiclimcpqueryrequiredopenapiself_serveCompare products by slug.
slugsrequiredFull registry profile (AgentReady Score, capabilities, sources).
slugrequiredList the registry, highest AgentReady Score first.
limitcategoryminScoreAudit a product for agent-readiness.
domainrequiredMake 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.
domainrequiredopenapiUrlStructured company record.
domainrequiredNormalized pricing.
domainrequiredGrounded, cited answer about a company.
domainrequiredquestionReal competitors and alternatives for a company, extracted from live research and returned as structured rows.
limitdomainrequiredStructured side-by-side of companies across fields (description, products, categories, funding, technology).
fieldsdomainsrequiredYour usage this billing period (read-only).
Takes no parameters.
100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
npx stackresolve@latest installnpx stackresolve@latest install --dry-run # show what would changenpx stackresolve@latest install --cursor # one agent onlynpx stackresolve@latest install --project --rules # also wire up the current repoclaude mcp add --transport http stackresolve https://mcp.stackresolve.dev/mcp{ "mcpServers": { "stackresolve": { "url": "https://mcp.stackresolve.dev/mcp", "headers": { "x-api-key": "ar_..." } } }}[mcp_servers.stackresolve]url = "https://mcp.stackresolve.dev/mcp"
[mcp_servers.stackresolve.headers]x-api-key = "ar_..."npm i -g stackresolvestackresolve find "scrape javascript-heavy sites from claude code"stackresolve audit stripe.comstackresolve company vercel.comstackresolve --helpnpm install stackresolve # SDKnpm i -g stackresolve # CLIimport { StackResolve } from 'stackresolve'
const sr = new StackResolve({ apiKey: process.env.STACKRESOLVE_API_KEY })
// 1. Audit a domain: AgentReady scores, facts, and issues.const report = await sr.audit('stripe.com')console.log(report.scores.agentready, report.issues)
// 2. Structured company data.const company = await sr.getCompany('vercel.com')console.log(company.name, company.description)
// 3. Task -> ranked, agent-ready tools.const tools = await sr.findTools('send transactional email from a Node service')console.log(tools.results)
// 4. Run an Agent Discovery check (needs an API key).const discovery = await sr.runDiscovery('firecrawl')console.log(discovery)const sr = new StackResolve({ apiKey: 'ar_...' })// or, reading STACKRESOLVE_API_KEY from the environment:const sr2 = new StackResolve()const sr = new StackResolve({ apiKey, baseUrl: 'https://api.stackresolve.dev' })import { StackResolve, StackResolveError } from 'stackresolve'
try { await sr.getUsage()} catch (err) { if (err instanceof StackResolveError) { console.error(err.status, err.body) }}pip install stackresolvepip install langchain-stackresolvefrom langchain_stackresolve import StackResolveToolkittools = StackResolveToolkit().get_tools()