io.orbator/orbator-mcp
REMOTE · API.ORBATOR.IO · SCANNED SEP 24
AI visibility checks, software recommendations and tool comparisons from measured AI answer data
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 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. 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 873 tokens (~218/item across 4 items; 4 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 io.orbator/orbator-mcp server?
io.orbator/orbator-mcp is a hosted endpoint at https://api.orbator.io/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 · api.orbator.io
claude mcp add --transport http io-orbator-orbator-mcp 'https://api.orbator.io/api/mcp'
{
"mcpServers": {
"io-orbator-orbator-mcp": {
"url": "https://api.orbator.io/api/mcp"
}
}
} {
"servers": {
"io-orbator-orbator-mcp": {
"type": "http",
"url": "https://api.orbator.io/api/mcp"
}
}
} [mcp_servers.io-orbator-orbator-mcp] url = "https://api.orbator.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-orbator-orbator-mcp": {
"type": "remote",
"url": "https://api.orbator.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add io-orbator-orbator-mcp --url 'https://api.orbator.io/api/mcp' --transport streamable-http
mcp_servers:
io-orbator-orbator-mcp:
url: "https://api.orbator.io/api/mcp" {
"McpServers": {
"io-orbator-orbator-mcp": {
"Transport": "http",
"Url": "https://api.orbator.io/api/mcp"
}
}
} assistant mcp add io-orbator-orbator-mcp -t streamable-http -u 'https://api.orbator.io/api/mcp'
{
"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.
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.
- 27 Aug 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 192 → 218 ▼ functional
- Server version: 0.1.0 → 0.1.1 functional
- 26 Aug 26 80
- 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
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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://api.orbator.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.orbator.io | CN=YR1,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | RSA 4096 | SHA256-RSA | 62d0b5ff7dd4048a2090a6b4f860424ed5f |
| SANs: api.orbator.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.orbator.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| orbator.io. | 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=15552000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| 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://api.orbator.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.orbator.io/api/mcp | HTTPS enforced | 302 | https://api.orbator.io/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 →
compare ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| product_a | string | yes | First product name or domain. |
| product_b | string | yes | Second product name or domain. |
No output schema declared.
No examples provided.
find_tools ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | 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). |
No output schema declared.
No examples provided.
get_ai_index ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_facts ~101
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").
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Product name or canonical domain, e.g. "hubspot.com". |
No output schema declared.
No examples provided.
What is the io.orbator/orbator-mcp server?
io.orbator/orbator-mcp is listed in the public MCP registry as io.orbator/orbator-mcp. AI visibility checks, software recommendations and tool comparisons from measured AI answer data. This page covers its hosted endpoint (https://api.orbator.io/api/mcp).
Is the io.orbator/orbator-mcp server safe to use?
io.orbator/orbator-mcp 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 io.orbator/orbator-mcp server expose?
io.orbator/orbator-mcp exposes 4 tools: find_tools, get_ai_index, get_facts, compare. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.
Does the io.orbator/orbator-mcp server require authentication?
No. We connected to io.orbator/orbator-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.orbator/orbator-mcp server still maintained?
io.orbator/orbator-mcp 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.