decixa-mcp
Allows AI agents to discover and resolve APIs for interacting with Reddit, such as summarizing posts or extracting data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@decixa-mcp find an API to summarize news articles"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
decixa-mcp
Find the right API for your AI agent. 30,000+ listings tracked. 5,500+ verified live as of April 2026.
MCP Server for Decixa — The decision layer for AI Agents.
v0.1.7: intent-driven update. New
resolve/discovertools replacesearch_apis/browse_apis(kept as deprecated aliases). See CHANGELOG.md for migration guide.
Quickstart
# Claude Code
npx decixa-mcp// Claude Desktop — claude_desktop_config.json
{
"mcpServers": {
"decixa": {
"command": "npx",
"args": ["-y", "decixa-mcp"]
}
}
}// Cursor / Windsurf — .cursor/mcp.json or .windsurf/mcp.json
{
"mcpServers": {
"decixa": {
"command": "npx",
"args": ["-y", "decixa-mcp"]
}
}
}Related MCP server: Frostbyte MCP
What you can do
resolve({ intent: "get real-time BTC price" })
→ Returns top recommendation + up to 2 alternatives, ranked by Phase 3 vector + scoring
resolve({ intent: "summarize Reddit posts", budget: 0.005 })
→ Filters by cost, returns trust_evidence and latency tier
discover({ intent: "transcribe audio", budget: 0.01, sort: "price_asc" })
→ Returns multiple x402-verified candidates so the agent can chooseWhy Decixa
Unlike x402.direct, Decixa verifies x402 compliance by actually probing each endpoint — not just metadata analysis.
Decixa | x402.direct | |
Listings tracked | 30,000+ | ~4,000 |
x402 verification | HTTP 402 probe (real) | Metadata scoring |
Capability classification | 9 verb-based axes | — |
Intent → API resolution |
| — |
MCP server |
| — |
Tools
resolve (recommended, replaces search_apis)
Find the best API for a task using natural language. Returns top recommendation + up to 2 alternatives. Decixa uses Phase 3 vector + scoring (vector 0.70 + latency 0.05 + price 0.05 + tiebreak 0.20). When no candidate clears the similarity threshold, returns recommendation_status='no_match' with up to 2 suggestions.
Parameter | Type | Description |
| string | What you want to do (e.g. |
| number | Max USDC per call (e.g. |
| string |
|
| number | Similarity threshold (0.2–0.9, default |
Response includes recommendation_status ("resolved" or "no_match").
discover (recommended, replaces browse_apis)
List APIs ranked by intent. Returns multiple candidates so the agent can choose. Verified-x402 only.
Parameter | Type | Description |
| string | Natural-language intent (mapped to server's |
| string | Filter by capability tag (e.g. |
| number | Max USDC per call |
| string |
|
| string |
|
| string |
|
| number | Similarity threshold (0.2–0.9, default |
| string |
|
| integer | Results per page (1–50, default 20) |
| integer | Pagination offset |
Response includes search_mode, min_similarity_applied, no_match_reason, top_candidates_below_threshold.
search_apis (deprecated alias for resolve)
DEPRECATED in v0.1.7. Will be removed in v1.0.0. Use
resolveinstead. Shares schema and handler withresolve.
browse_apis (deprecated alias for discover)
DEPRECATED in v0.1.7. Will be removed in v1.0.0. Use
discoverinstead. Shares schema and handler withdiscover.
get_api_detail
Get full details for a specific API by ID.
Parameter | Type | Description |
| string | API ID from |
Returns: endpoint URL, pricing, capability, tags, agent_compatibility, schema info, use_cases, trust_evidence (score / uptime_7d / p95_latency_ms / payment_req_parsed / last_checked / last_probed_at), provider, and verified_live flag. Prefer trust_evidence.score over legacy trust_score for new clients.
get_index
Entry point for agents new to Decixa. Returns platform overview, endpoints, and usage guidance.
No parameters required.
Migration from v0.1.6
Old | New | Notes |
|
| Drop |
|
|
|
| (removed) | Capability filtering is no longer needed. Pass intent text + optional |
Strict MCP clients note: if your MCP client validates additionalProperties: false, it will reject capability / agent_ready arguments at the client side. Tolerant clients let them through, but Decixa silently ignores them server-side. Either way, remove them.
See CHANGELOG.md for full details.
Claude Code setup
See docs/claude-code.md for step-by-step Claude Code integration.
Environment Variables
Variable | Default | Description |
|
| Decixa API base URL |
| (empty) | API key — reserved for future use |
License
MIT
Available Tools
6 toolsbrowse_apisA
DEPRECATED in v0.1.7. Use 'discover' instead. This alias will be removed in v1.0.0. [Original behavior preserved in this version: List APIs ranked by intent.]
Inputs: intent (required), tag, sort, limit, +8 more.
discoverA
List APIs ranked by intent. Returns multiple candidates so the agent can choose. Decixa uses Phase 3 vector + scoring to rank verified-x402 APIs. Use this when you want to see options — use resolve when you want a single recommendation.
Inputs: intent (required), tag, sort, limit, +8 more.
get_api_detailA
Get full details for a specific API by its ID. Returns endpoint URL, pricing, capability, tags, agent compatibility, schema info, use cases, trust signals (trust_evidence), and provider. Prefer trust_evidence.score (with uptime_7d / p95_latency_ms / payment_req_parsed) over legacy trust_score for new clients. The top-level verified_live boolean indicates whether this API is verified to accept x402 payments; unlike resolve/discover, detail also returns APIs that are not yet verified. Use this after resolve or discover to inspect a specific API before calling it.
Inputs: api_id (required).
get_indexA
Fetch the Decixa agent index — a machine-readable overview of the platform including available endpoints, total API count, and usage guidance for AI agents. Good starting point for agents new to Decixa.
Inputs: no named parameters.
resolveA
Find the best API for a task using natural language. Returns the top recommendation and up to 2 alternatives. Decixa uses Phase 3 vector + scoring to rank verified-x402 APIs by intent. When no candidate clears the similarity threshold, returns recommendation_status='no_match' with suggestions. Use this when you want Decixa to pick — use discover when you want to see the list.
Inputs: intent (required), budget, latency, min_similarity, +2 more.
search_apisA
DEPRECATED in v0.1.7. Use 'resolve' instead. This alias will be removed in v1.0.0. [Original behavior preserved in this version: Find the best API for a task using natural language.]
Inputs: intent (required), budget, latency, min_similarity, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
The core tools (discover, resolve, get_api_detail, get_index) have distinct purposes, but the presence of deprecated aliases (browse_apis, search_apis) that mirror functionalities introduces ambiguity. The deprecation notices help, but agents may still select the wrong tool without careful reading.
Tool names mix conventions: some are single verbs ('discover', 'resolve'), some use 'get_' prefix ('get_api_detail', 'get_index'), and others follow verb_noun pattern ('browse_apis', 'search_apis'). While still readable, the inconsistency could confuse agents expecting a uniform pattern.
With 6 tools (2 deprecated), the effective count is 4 core tools, which is appropriate for API discovery and details. The scope is well-focused, and the tools are not excessive.
The set covers key operations: listing (discover), best-match selection (resolve), detailed information (get_api_detail), and platform overview (get_index). There are no obvious gaps for the stated purpose of API discovery and inspection.
Maintenance
Related MCP Connectors
Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.
Find MCP servers, APIs, tools and skills by intent. Free key: POST /api/agents/register
MCP server for building and testing AI agents with multi-model experimentation and insights.
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to search, pay for, and call paid APIs using the x402 protocol, with automatic USDC settlement.2MIT- AlicenseNot gradedqualityCmaintenanceA unified MCP server providing AI agents with 40+ developer APIs including geolocation, crypto prices, DNS lookup, and web scraping. Enables natural language access to various tools through a single gateway.1MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for API discovery and execution with a token-efficient search -> execute workflow over OpenAPI, Google Discovery, and optional native GraphQL and gRPC sources.90 npm13Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to explore, search, and query API definitions from OpenAPI/Swagger JSON files.23 npmMIT