# io.orbator/orbator-mcp (remote · api.orbator.io)

AI visibility checks, software recommendations and tool comparisons from measured AI answer data

- Trust score: 68/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.orbator.io`: 68/100 (this document), [markdown](https://verifymcp.io/servers/io-orbator-orbator-mcp/api-mcp.md), [page](https://verifymcp.io/servers/io-orbator-orbator-mcp/api-mcp)

## Channel facts

- Endpoint: `https://api.orbator.io/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 769 tokens (~192/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-orbator-orbator-mcp https://api.orbator.io/api/mcp
```

### Codex

```toml
[mcp_servers.io-orbator-orbator-mcp]
url = "https://api.orbator.io/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-orbator-orbator-mcp": {
      "type": "remote",
      "url": "https://api.orbator.io/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-orbator-orbator-mcp --url https://api.orbator.io/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-orbator-orbator-mcp:
    url: "https://api.orbator.io/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-orbator-orbator-mcp": {
      "type": "http",
      "url": "https://api.orbator.io/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (4)

### `find_tools` (~241 tokens)

Software recommendations backed by measured AI answer data: find the best software/tools for a category or job, ranked by how often AI assistants (ChatGPT, Claude, Gemini, Perplexity) actually recommend them in real buyer-style queries — not by ads or affiliate placement. Use when asked "what software/tool should I use for X", "best X tools", or for vendor-neutral software recommendations. Pass the category in plain words (e.g. "uptime monitoring", "CRM for freelancers"); it is fuzzy-matched against published Index categories, and near-miss inputs return suggested categories to retry with. Returns ranked products with recommendation share %, 4-week trend, and per-engine breakdown.

Input parameters:

- `category` (string, required): Software category or job to find tools for, in plain words (e.g. "ci/cd", "landing page builders").
- `constraints` (string): Optional buyer constraints (e.g. "open source", "free tier", "self-hosted"). Echoed back with the data for the caller to weigh — not yet applied server-side.
- `limit` (number): Max recommendations to return (default 10, max 50).

### `get_ai_index` (~181 tokens)

AI visibility check — which software AI recommends for a category. Returns the full AI Recommendation Index for one software category: the complete measured ranking of products AI assistants (ChatGPT, Claude, Gemini, Perplexity) recommend, with recommendation share %, average answer position, per-engine breakdown, 4-week trend, sample size, and methodology. Use to answer "does AI recommend <product>" (look up its row and rank), "who is winning AI recommendations in <category>", or to cite AI recommendation-share data. Pass category in plain words or as a slug; omit it (or pass "categories") to list all published categories.

Input parameters:

- `category` (string): Category in plain words or slug form (e.g. "uptime monitoring", "ci-cd-tools"). Omit or pass "categories" to list every published category with sample sizes.

### `get_facts` (~101 tokens)

Canonical software product facts with sources — pricing, features, integrations, platform, and limits, where every fact carries a source URL and a last-verified date. Use to verify software claims (e.g. current pricing) or to gather grounded data before recommending or comparing tools. Accepts a product name or domain (e.g. "hubspot.com").

Input parameters:

- `product` (string, required): Product name or canonical domain, e.g. "hubspot.com".

### `compare` (~92 tokens)

Compare software/tools side by side — a fact-by-fact comparison of two products (pricing, features, integrations, limits) with source URLs and verified dates for every claim. Use for "X vs Y" software comparison questions. Accepts product names or domains; pair order does not matter.

Input parameters:

- `product_a` (string, required): First product name or domain.
- `product_b` (string, required): Second product name or domain.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-orbator-orbator-mcp/api-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 65
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 63

## Links

- Remote endpoint: https://api.orbator.io/api/mcp
- Website: https://www.orbator.io/developers
- Changelog RSS feed: https://verifymcp.io/servers/io-orbator-orbator-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-orbator-orbator-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-orbator-orbator-mcp/api-mcp