Orbilo
REMOTE · ORBILO.CO
Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites.
Available components
Last scanned (13 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 854 tokens (~122/item across 7 items; 5 tools + 2 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 8 Oct 26 +1
- Stability: 0.90 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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
- 25 Sept 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
- 8 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 7 Sept 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 5 Nov 2026 · Probed https://orbilo.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=orbilo.co | CN=YE2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 384 | ECDSA-SHA384 | 6b8b0c71b504876e3289841360a6422871e |
| SANs: *.orbilo.co, orbilo.co | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of orbilo.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| orbilo.co. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://orbilo.co/.well-known/oauth-protected-resource/mcp"
Bearer realm="mcp", resource_metadata="https://orbilo.co/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Protected resource metadata
| Document | https://orbilo.co/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://orbilo.co/mcp |
| Authorisation server | https://orbilo.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://orbilo.co/mcp | Verified | 200 | |
| http (plaintext) | http://orbilo.co/mcp | HTTPS enforced | 301 | https://orbilo.co/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 →
add_monitored_site Add a Monitored Site ~124
Start monitoring a site: Orbilo checks it against UCP, WebMCP and Access now and on a schedule, and alerts the team when readiness changes. Use this when someone wants ongoing monitoring rather than a one-off check, or asks to be told when their site breaks for agents. Uses one of the plan's site slots. Requires a connected Orbilo account.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site to monitor, as a domain or URL, e.g. shop.example.com. Monitoring is per site; WebMCP pages can be added on the dashboard. |
No output schema declared.
No examples provided.
check_site Check a Site ~211
Check whether a website is ready for AI agents against the UCP, WebMCP and Access specs. Use this when someone asks "can agents use my site", whether a site supports UCP or WebMCP, or why an agent cannot buy from or act on a page. Returns a score and grade per spec, every check that passed, warned or failed with a fix for each, and a shareable report link. Runs live and can take up to a minute for all three specs. Works without signing in; signed-in users get a higher daily limit.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Skip the 10 minute result cache and check the site again now. |
| spec | string | – | Which spec to check: ucp, webmcp, access, or all (default). WebMCP checks are page-specific, so pass the page that registers tools. |
| url | string | yes | The page to check, e.g. https://shop.example.com. A bare domain is checked over https. |
No output schema declared.
No examples provided.
get_report Get a Shared Report ~91
Fetch a check report by its share token, the 16 character code at the end of an orbilo.co/check/r/... link. Use this when someone pastes a report link or asks about a check that was already run, instead of checking the site again. Reports expire 30 days after the check. Works without signing in.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The share token, or the full report URL |
No output schema declared.
No examples provided.
get_site_status Get Site Status ~127
The current standing of one monitored site: the latest stored check per spec (UCP and Access for the site, WebMCP per monitored page) and every open issue with its fix. Use this when someone asks what is wrong with a site they monitor, what to fix first, or when it was last checked. Pass the domain or the site id from list_monitored_sites. For a site that is not monitored, use check_site instead. Requires a connected Orbilo account.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The site domain (e.g. shop.example.com) or its id |
No output schema declared.
No examples provided.
list_monitored_sites List Monitored Sites ~83
List the sites your Orbilo team monitors, with the latest grade per spec (UCP, WebMCP, Access), how many issues are open on each, and how many sites the plan still allows. Use this when someone asks what they are monitoring, how their sites are doing, or whether they can add another site. Requires a connected Orbilo account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Orbilo MCP server?
Orbilo is a hosted endpoint at https://orbilo.co/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 · orbilo.co
claude mcp add --transport http co-orbilo-orbilo 'https://orbilo.co/mcp'
What is the Orbilo MCP server?
Orbilo is an MCP server listed in the public MCP registry as co.orbilo/orbilo. Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites. This page covers its hosted endpoint (https://orbilo.co/mcp).
Is the Orbilo MCP server safe to use?
Orbilo scores 93 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 Orbilo MCP server expose?
Orbilo exposes 5 tools: check_site, get_report, list_monitored_sites, get_site_status, add_monitored_site. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.
Does the Orbilo MCP server require authentication?
Yes. Orbilo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Orbilo MCP server still maintained?
Orbilo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Orbilo MCP server?
VerifyMCP ran 13 checks on Orbilo, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.