Revuo
REMOTE · WWW.REVUO.AI · SCANNED SEP 24
Agent-callable B2B SaaS directory: capability-structured, continuously verified listings.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4036 tokens (~288/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
How do I install the Revuo MCP server?
Revuo is a hosted endpoint at https://www.revuo.ai/api/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 · www.revuo.ai
claude mcp add --transport http ai-revuo-revuo 'https://www.revuo.ai/api/mcp'
{
"mcpServers": {
"ai-revuo-revuo": {
"url": "https://www.revuo.ai/api/mcp"
}
}
} {
"servers": {
"ai-revuo-revuo": {
"type": "http",
"url": "https://www.revuo.ai/api/mcp"
}
}
} [mcp_servers.ai-revuo-revuo] url = "https://www.revuo.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-revuo-revuo": {
"type": "remote",
"url": "https://www.revuo.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-revuo-revuo --url 'https://www.revuo.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-revuo-revuo:
url: "https://www.revuo.ai/api/mcp" {
"McpServers": {
"ai-revuo-revuo": {
"Transport": "http",
"Url": "https://www.revuo.ai/api/mcp"
}
}
} assistant mcp add ai-revuo-revuo -t streamable-http -u 'https://www.revuo.ai/api/mcp'
{
"mcpServers": {
"ai-revuo-revuo": {
"type": "http",
"url": "https://www.revuo.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 −1
- Stability: pass → 0.97 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 −1
- Stability: pass → 0.97 functional
- 30 Aug 26 0
- Tool “directory.overview” rewrote its description, which is the text the model reads security
- Tool “products.get” rewrote its description, which is the text the model reads security
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 16 Aug 26 0
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.70 ▲ functional
- MCP protocol: unverified → pass ▲ functional
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 24 Sept 2026 · Probed https://www.revuo.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=revuo.ai | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9d6435dd2e9f2bb0ed7f3869072a9a9 |
| SANs: revuo.ai, *.revuo.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.revuo.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| revuo.ai. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=315360000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.revuo.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.revuo.ai/api/mcp | HTTPS enforced | 301 | https://www.revuo.ai/api/mcp |
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 →
categories.list ~89
Lists all product categories in the directory. Use category slugs to filter product searches in products.search / products.find_by_capability. Response: { categories: [{ slug, name, description }] }. Note: this is a thin call. For a full directory briefing (subcategories, capability slugs per category, product counts, locked-vertical flags), prefer directory.overview as a single up-front call.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array|null | – | – |
| error | object|null | – | – |
No examples provided.
directory.overview ~203
Single 'call this first' entry-point that briefs an agent on the entire Revuo directory. Returns the taxonomy with subcategories, product counts per category, locked-vertical flags (the three verticals Revuo prioritizes), capability slugs valid per category, the canonical capability-kind taxonomy (integration/compliance/format/standard/workflow), and product-bound agent surfaces (mcpServer, agentSkill, grokBot). Surfaces are a property of a product — they are NOT category slugs. Use this once at the start of a session to ground every subsequent products.search / products.find_by_capability / tools.find_for_task call. Response: { directory: { name, tagline, url, policyUrl, capabilityKinds[] }, lockedVerticals[], categories[] (each with subcategories[], productCount, isLockedVertical, capabilitySlugs[]), surfaces[] (kind, description, listedOn=product), tools: { ...tool-name hints } }.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array|null | – | – |
| directory | object|null | – | – |
| error | object|null | – | – |
| lockedVerticals | array|null | – | – |
| surfaces | array|null | – | – |
| tools | object|null | – | – |
No examples provided.
mcp.score_server ~299
Score an MCP server against the Revuo quality rubric. Pass either a product slug (scored from cached probe data on the product's direct-probe MCP entry; fast) OR an endpoint URL (probed live). Returns: { target, server, summary { coreAwarded/Max/Percent, extensionAwarded/Max/Percent, probedAt }, categories[] (ServerMetadata, CapabilityQuality, ConfigurationUX, RevuoExtensions), checks[] (every rubric check with awarded/max/passed/evaluated/fixSuggestion/evidence), topFixes[] (failed checks ranked by points-at-stake), probe (probe diagnostics) }. Core score (max 100) is Smithery-comparable. Extension score covers Revuo-specific signals (response time today; freshness, error envelope, schema stability are not yet implemented and report evaluated=false — excluded from totals, never counted as a failure). A check with evaluated=false is a Revuo gap, not the server's fault. Errors: { error: { code: 'bad_input'|'not_found', ... } }.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | When passing slug, force a fresh probe instead of using cached probe data. Default false. |
| slug | string|null | – | Product slug whose direct-probe MCP server to score. Mutually exclusive with url. |
| url | string|null | – | MCP endpoint URL (HTTPS) to probe and score. Mutually exclusive with slug. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array|null | – | – |
| checks | array|null | – | – |
| error | object|null | – | – |
| probe | object|null | – | – |
| server | object|null | – | – |
| summary | object|null | – | – |
| target | object|null | – | – |
| topFixes | array|null | – | – |
No examples provided.
products.find_agent_ready ~331
Find products with the highest agent readiness scores — products that are easiest for AI agents to integrate with. Sorted by compositeScore desc; supports skip/limit pagination. All readiness scores are 0-100, higher better. Calibration: <30 = not agent-ready (default minimumScore filter), 30-49 = early/limited, 50-69 = decent, 70-89 = strong, 90+ = exceptional. Ranking basis: compositeScore desc. Tier is NOT a tiebreaker here — buyer intent is technical fit, not paid placement. Every result carries { position (1-based, within the returned page), rank (0..1; 1.0 = top of this page) } so callers can merge results across tools consistently. Response: { products: [{ position, rank, slug, name, tagline, websiteUrl, tier (free|verified|featured), unverified (true when no approved vendor claim), verifiedAt (ISO; nullable), agentReadiness: { compositeScore, apiScore, protocolScore, sdkScore, integrationScore, dxScore } (each 0-100), mcp?: { hasMcpSupport, totalToolCount, serverCount } }] }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results to return per page. Caps at 50. |
| minimumScore | integer | – | Minimum composite agent readiness score (0-100). Higher = more agent-ready. 0 returns everything; 50 is a usable threshold. |
| skip | integer | – | Number of results to skip (for pagination). Default 0. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object|null | – | – |
| products | array|null | – | – |
No examples provided.
products.find_by_capability ~341
Find B2B SaaS products that support a specific capability — an integration with a named service ('salesforce-integration'), a data format ('xrechnung-support'), an industry standard ('eclass-support'), or a compliance certification ('soc2'). Accepts either a canonical capability slug or natural language; resolves to a structured capability when possible. Ranking basis: currentScore desc (computed editorial score), then name. Paid tier is NOT a ranking input — it appears only as an annotation. Every result carries { position (1-based), rank (0..1; 1.0 = top, scales linearly down by ordinal position) } so callers can merge results across tools consistently. Response: { capability, matchType (none|exactSlug|canonicalSlug|nlpFallback — exactSlug & canonicalSlug are deterministic; nlpFallback is heuristic), resolvedFeatures[], products[] }. Each product: { position, rank, slug, name, tagline, websiteUrl, tier, unverified (true when no approved vendor claim), verifiedAt, evidence[] (per-claim: featureSlug, evidenceUrl, notes, source, confidence) }. Empty: { capability, matchType, message, suggestedSlugs[] } when no capability matched, or products: [] when capability matched but no products claim it yet.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | Capability slug ('salesforce-integration') OR natural-language description ('integrates with Salesforce') |
| category | string|null | – | Optional category slug to scope the search (e.g. 'pim', 'tender-management', 'billing') |
| limit | integer | – | Maximum number of results to return |
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string|null | – | – |
| error | object|null | – | – |
| matchType | string|null | – | – |
| message | string|null | – | – |
| products | array|null | – | – |
| resolvedFeatures | array|null | – | – |
| suggestedSlugs | array|null | – | – |
No examples provided.
products.get ~237
Get full details for a product by slug, including MCP integration data, product-bound agent artifacts (Agent Skills, Grok Bots), and agent readiness scores. Agent artifacts are a property of the product — not directory categories. Response: { product: { slug, name, tagline, description, websiteUrl, logoUrl, pricingModel, currentScore (0-100), tier (free|verified|featured), unverified (true when no approved vendor claim), verifiedAt (ISO; absent if never crawled), categories[], knownLimitations?[] (sourced weaknesses, each with evidenceUrl — weigh before recommending), alternatives?[] (neutral, score-ranked same-category options, self excluded, houseProduct disclosed) }, mcp?: { hasMcpSupport, totalToolCount, totalUseCount, servers[] }, agentArtifacts[] (kind agentSkill|grokBot, install URLs, related product slugs), agentReadiness?: { compositeScore (0-100), aiSummary } }. Errors: { error: { code: 'not_found', ... } }.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Product slug (URL-friendly identifier) |
| Name | Type | Req | Description |
|---|---|---|---|
| agentArtifacts | array|null | – | – |
| agentReadiness | object|null | – | – |
| error | object|null | – | – |
| mcp | object|null | – | – |
| product | object|null | – | – |
No examples provided.
products.get_mcp_setup ~269
Get MCP server setup instructions for a product. Returns available servers, their tools, connection details, and whether they support remote (hosted) access. Each server carries a machine-usable connect block: { transport ('http'|'local'), url, mcpJson (paste-ready snippet), claudeMcpAddCommand (`claude mcp add ...`), installLinkUrl (a tracked link that routes through Revuo for vendor attribution, then redirects to the product) }. For remote servers use mcpJson/claudeMcpAddCommand directly; for local servers follow repositoryUrl. Each server also carries schema { hash, stable, lastChangeAt } — cache the hash and pass it to tools.changes(knownHash) later to detect tool-schema drift (rug-pull / tool-poisoning). Response when MCP support exists: { product: { slug, name, websiteUrl, tier, unverified, verifiedAt }, hasMcpSupport: true, totalToolCount, servers[], agentReadiness? }. Response when product exists but lacks MCP: { product: {...}, hasMcpSupport: false, message }. Errors: { error: { code: 'not_found', ... } }.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Product slug (URL-friendly identifier) |
| Name | Type | Req | Description |
|---|---|---|---|
| agentReadiness | object|null | – | – |
| error | object|null | – | – |
| hasMcpSupport | boolean|null | – | – |
| message | string|null | – | – |
| product | object|null | – | – |
| servers | array|null | – | – |
| totalToolCount | integer|null | – | – |
No examples provided.
products.search ~354
Search for B2B SaaS products by name OR by capability. The query is first resolved against the canonical capability taxonomy (e.g. 'salesforce-integration', 'xrechnung-support', 'soc2'); on hit, products that claim that capability are returned. Falls back to name/slug/tagline substring search. Optional category scope. Ranking basis: currentScore desc (computed editorial score), then name. Paid tier is NOT a ranking input — tier appears only as an annotation on results. Every result carries { position (1-based), rank (0..1; 1.0 = top, scales linearly down by ordinal position) } so callers can merge results across tools consistently. Response: { query, matchType (none|exactSlug|canonicalSlug|nlpFallback), resolvedCapabilities[], products[] }. Each product carries { position, rank, tier (free|verified|featured — annotation only), houseProduct (true = built by Revuo's founder; conflict-of-interest disclosure), sponsored (true = paid Featured placement), unverified (true when the listing has no approved vendor claim; omitted otherwise — absence means an approved vendor claim, NOT crawl freshness; use verifiedAt for that), verifiedAt (ISO timestamp of last claim crawl; absent if never crawled), currentScore (0-100), compositeScore (agent-readiness 0-100, nullable), matchedCapability (true if surfaced by capability path) }. Errors: { error: { code: 'not_found'|'bad_input', ... } }.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string|null | – | Optional category slug to filter results |
| query | string | yes | Search query — capability slug or natural-language description; falls back to name match |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object|null | – | – |
| matchType | string|null | – | – |
| products | array|null | – | – |
| query | string|null | – | – |
| resolvedCapabilities | array|null | – | – |
No examples provided.
rankings.get ~273
Get the published editorial ranking ("Best {Category}") for a category. Ordering basis: computed editorial score ONLY (verified capability coverage, evidence verification rate & freshness, agent readiness, data completeness — weights published at /api/methodology). Tier is NOT a ranking input for this tool; positions are never sold. Rankings are published snapshots (monthly schedule; manual publishes are marked) — stable between recomputes and citable. Each entry carries { position, rank (0..1), slug, name, score (0-100), breakdown (raw 0-100 per dimension), tier (annotation only), houseProduct (true = built by Revuo's founder — same formula as everyone, disclosed machine-readably), unverified, verifiedAt }. unrankedCount + unranked[] name the category products that failed an eligibility gate, with reasons. Response: { category, computedAt, methodologyVersion, methodologyUrl, trigger, entries[], unranked[] }. Errors: { error: { code: 'not_found', ... } } — also returned when a category has no published ranking yet.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category slug (e.g. 'pim-software'). Use categories.list for valid slugs. |
| limit | integer | – | Max ranked entries to return (caps at 50) |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string|null | – | – |
| computedAt | string|null | – | – |
| entries | array|null | – | – |
| error | object|null | – | – |
| methodologyUrl | string|null | – | – |
| methodologyVersion | string|null | – | – |
| trigger | string|null | – | – |
| unranked | array|null | – | – |
No examples provided.
tools.changes ~370
Detect whether a product's MCP tool schema has DRIFTED since you cached it — rug-pull / tool-poisoning detection (a server silently changing a tool's description or input schema after you approved it; web search structurally cannot answer this). Pass the product slug and EITHER the schema hash you cached earlier (knownHash, from products.get_mcp_setup → server.schema.hash — the strongest signal: an exact mismatch means the tools changed) OR the ISO-8601 timestamp you cached at (since). With neither, it returns the current fingerprint to cache for next time. A product may expose MULTIPLE servers: knownHash is per-server, so pass `server` (a qualifiedName) with knownHash on a multi-server product — otherwise knownHash is applied only when there's exactly one server. Re-verify before trusting a previously-approved tool. Response: { product, hasMcpSupport, drifted (did ANY tracked server change vs your reference; null when no reference given), servers[] (each: qualifiedName, currentSchemaHash, schemaStable, lastSchemaChangeAt, toolCount, directlyProbed, driftedSinceKnownHash, driftedSince, advice) }. Errors: { error: { code: 'not_found'|'bad_input', ... } }.
| Name | Type | Req | Description |
|---|---|---|---|
| knownHash | string|null | – | The schema hash you cached earlier (products.get_mcp_setup → server.schema.hash). Exact-mismatch drift signal. |
| server | string|null | – | The server qualifiedName your knownHash belongs to. Required with knownHash on a multi-server product. |
| since | string|null | – | ISO-8601 timestamp you last cached at. Reports whether a schema change was recorded after it. |
| slug | string | yes | Product slug whose MCP tool schema to check. |
| Name | Type | Req | Description |
|---|---|---|---|
| drifted | boolean|null | – | – |
| error | object|null | – | – |
| hasMcpSupport | boolean|null | – | – |
| message | string|null | – | – |
| product | object|null | – | – |
| servers | array|null | – | – |
No examples provided.
tools.find_for_task ~526
Find the best MCP tools for a given task. Describe what you want to accomplish (e.g. 'manage github issues', 'send slack messages', 'query a database') and get ranked results — each result is one (product, tool) pair, since same-named tools across providers are NOT interchangeable. By default only shows tools available via remote (network-hosted) servers. Audience: agent builders looking for installable MCP tools — for B2B SaaS recommendations, prefer products.search or products.find_by_capability. Ranking basis: relevance score desc (+1 per term hit, +3 for full-phrase hit); within an equal relevance tier, callable-now (Open access) + remote + healthy tools are boosted ahead — never a hard filter (a product-bound tool stays in its own money query), then productName. Paid tier is NOT a ranking input — it appears only as an annotation. Every result carries { position (1-based), rank (0..1; 1.0 = top, scales linearly down by ordinal position) } plus preflight annotations { accessModel (open|keyed|account|commercial), healthScore (0-100, nullable), readOnly, destructive, callableNow (true = usable anonymously right now), setup (one-line 'how to get access' pointer for non-Open tools) }. Response: { task, matchType (none|exactSlug|canonicalSlug|nlpFallback), resolvedCapabilities[], capabilityProducts[] (B2B SaaS products that claim the same capability — empty when matchType=none), results[] (MCP-tool-level matches), buckets { callableNow, requiresSetup } }. Each result: { position, rank, normalizedName, displayName, description, inputSchema, relevance, accessModel, healthScore, readOnly, destructive, callableNow, setup, productSlug, productName, serverQualifiedName, isRemoteCapable, tier, unverified, verifiedAt }. Empty case: { task, matchType, message, suggestedQueries[], suggestedCapabilities[] }.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string|null | – | Optional access-class filter: 'open' (callable anonymously), 'keyed', 'account', 'commercial', or 'unknown'. Omit for all — Open tools are boosted, not required. |
| limit | integer | – | Maximum number of tool results to return |
| remoteOnly | boolean | – | If true (default), only return tools from remote-capable MCP servers |
| taskDescription | string | yes | Natural language description of the task you want to accomplish |
| Name | Type | Req | Description |
|---|---|---|---|
| buckets | object|null | – | – |
| capabilityProducts | array|null | – | – |
| error | object|null | – | – |
| matchType | string|null | – | – |
| message | string|null | – | – |
| resolvedCapabilities | array|null | – | – |
| results | array|null | – | – |
| suggestedCapabilities | array|null | – | – |
| suggestedQueries | array|null | – | – |
| task | string|null | – | – |
No examples provided.
tools.get ~173
Get detailed information about a specific MCP tool, scoped to one product. Pass both the productSlug and the tool name — same-named tools across products are distinct. Response: { tool: { normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt, position (always 1), rank (always 1.0) } }. Errors: { error: { code: 'not_found', ... } }.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Normalized tool name (e.g. 'search_issues', 'send_message') |
| productSlug | string | yes | Slug of the product that exposes this tool (e.g. 'linear', 'github') |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object|null | – | – |
| tool | object|null | – | – |
No examples provided.
tools.list_by_name ~177
List every (product, tool) pair that shares a normalized name. A disambiguation lookup — same name across providers does NOT mean the tools are interchangeable. Ranking basis: productName. Paid tier is NOT a ranking input — it appears only as an annotation. Every result carries { position (1-based), rank (0..1) } plus preflight annotations { accessModel, healthScore, readOnly, destructive }. Response: { normalizedName, total, tools[] (each: position, rank, productSlug, productName, displayName, description, inputSchema, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt) }.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Normalized tool name (e.g. 'search', 'create_issue') |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object|null | – | – |
| normalizedName | string|null | – | – |
| tools | array|null | – | – |
| total | integer|null | – | – |
No examples provided.
tools.search ~394
Search for MCP tools by capability. Each result is one (product, tool) pair — tools sharing a name across providers are NOT interchangeable, so each provider's tool is its own row with its own description and input schema. Ranking basis: semantic relevance to the query (embedding search); on the lexical fallback (searchMode='lexical') results are name-ordered and rank does NOT reflect relevance. Paid tier is NOT a ranking input — it appears only as an annotation. Every result carries { position (1-based), rank (0..1; 1.0 = top) } so callers can merge results across tools consistently, plus preflight annotations { accessModel (open|keyed|account|commercial; whether an agent can call it without becoming a customer first), healthScore (0-100, nullable), readOnly, destructive } so you can judge callability and safety BEFORE selecting. Optional access filter narrows to a single access class. Response: { searchMode ('semantic'|'lexical'), tools: [{ position, rank, normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified (true when no approved vendor claim), verifiedAt (ISO; nullable) }] }. Errors: { error: { code: 'bad_input', ... } }.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string|null | – | Optional access-class filter: 'open' (callable anonymously), 'keyed', 'account', 'commercial', or 'unknown'. Omit for all. |
| limit | integer | – | Maximum number of results to return |
| query | string | yes | Search query to find tools by name or capability. Natural-language phrases work best (semantic search). |
| remoteOnly | boolean | – | If true, only return tools available via remote (network-hosted) MCP servers |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object|null | – | – |
| searchMode | string|null | – | – |
| tools | array|null | – | – |
No examples provided.
What is the Revuo MCP server?
Revuo is an MCP server listed in the public MCP registry as ai.revuo/revuo. Agent-callable B2B SaaS directory: capability-structured, continuously verified listings. This page covers its hosted endpoint (https://www.revuo.ai/api/mcp).
Is the Revuo MCP server safe to use?
Revuo scores 79 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 Revuo MCP server expose?
Revuo exposes 14 tools: tools.get, categories.list, mcp.score_server, products.get_mcp_setup, products.get, and 9 more. Their descriptions and schemas cost roughly 4,036 tokens of context every time the server is loaded.
Does the Revuo MCP server require authentication?
No. We connected to Revuo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Revuo MCP server still maintained?
Revuo is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.