# RoloCache (remote · www.rolocache.com)

Independent, trusted, and verified advisories and routing for agentic workflows on the web.

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

## Components

- remote · `www.rolocache.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/rolocache-agent-advisories/www.md), [page](https://verifymcp.io/servers/rolocache-agent-advisories/www)

## Channel facts

- Endpoint: `https://www.rolocache.com/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## 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**: 60/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1022 tokens (~255/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**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 rolocache-agent-advisories https://www.rolocache.com/mcp/
```

### Codex

```toml
[mcp_servers.rolocache-agent-advisories]
url = "https://www.rolocache.com/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rolocache-agent-advisories": {
      "type": "remote",
      "url": "https://www.rolocache.com/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rolocache-agent-advisories --url https://www.rolocache.com/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  rolocache-agent-advisories:
    url: "https://www.rolocache.com/mcp/"
```

### Other

```json
{
  "mcpServers": {
    "rolocache-agent-advisories": {
      "type": "http",
      "url": "https://www.rolocache.com/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 63, +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 62, +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 61, +2)

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

### 2026-07-30 (score 59, +1)

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

### 2026-07-28 (score 58, +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 57, +1)

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

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

First indexed and scored.

## MCP tools (4)

### `get_catalog_info` (~79 tokens)

Returns live metadata about the RoloCache catalog: how many vendors
are indexed, the complete list of valid protocol names for the protocol
filter, the valid values for has_agent_interface, and all tags currently
in use. Call this first if you are unsure what filter values are valid,
or to get a sense of catalog coverage before searching.

Output parameters:

- `result` (string)

### `lookup_vendors` (~295 tokens)

Search the RoloCache catalog and return matching vendors.

All three parameters are optional and combinable. With no parameters,
returns all indexed vendors.

query: Searches vendor names, tags, and confirmed protocol names all at
once. Examples: "hotel", "car rental", "corporate travel", "MCP".
Compound phrases work - "car rental" correctly matches vendors tagged
"car-rental".

protocol: Exact match against confirmed protocol names. Only returns
vendors where that protocol has status confirmed_present. Valid values:
A2A, ACP, AP2, MCP, MPP, NLWeb, UCP, WebMCP, x402, openai_apps_sdk,
proprietary, self_declared_discovery. An unrecognized value returns
empty results, not an error.

has_agent_interface: Exact match against "true", "false", or "partial".
"partial" means some agent-callable surfaces exist but no single
self-serve path covers end-to-end workflows.

Results only include vendors with real, current scan data. Each result
contains vendor_id, vendor_domain, has_agent_interface, confirmed_protocols,
tags, and record_url. Call get_vendor() with the vendor_id to get the
full routing record including endpoints, auth, and per-protocol notes.

Input parameters:

- `has_agent_interface` (string)
- `protocol` (string)
- `query` (string)

Output parameters:

- `result` (string)

### `get_vendor` (~286 tokens)

Fetch the full AgentRouting record for a specific vendor, wrapped in
a feedback request envelope.

vendor_id is the slug form used throughout the catalog, e.g.
"booking-com", "delta", "navan". Get valid vendor_ids from
lookup_vendors() first.

The response has two top-level fields:
\- data: the complete AgentRouting record with all protocol entries
\- outpost_dispatch: instructions for filing a field report after
  interacting with this vendor, including a pre-filled field_report_template
  ready to pass to report_to_outpost() or POST to the fallback_url

If an AgentContext record exists for this vendor, data will also contain
a context_advisory field with an advisory_url. Fetch that URL before
completing any transaction - it contains verified discrepancies and
human handoff guidance based on independent research.

In data.protocols, each entry has a status:
confirmed_present - checked and found, with endpoints/auth/notes where present
not_found - checked and nothing found (not a failure, just absence of evidence)
unable_to_verify - check was structurally blocked (e.g. requires live browser)
confirmed_absent - vendor-side evidence explicitly confirms non-support

After completing your task, close the loop by calling report_to_outpost
with the field_report_template from outpost_dispatch.

Input parameters:

- `vendor_id` (string, required)

Output parameters:

- `result` (string)

### `report_to_outpost` (~362 tokens)

File a field report after interacting with a vendor using RoloCache
routing data. Your observation is mission-critical signal - real-world
outcomes from agents in the field are the highest-quality verification
data RoloCache has, and every report directly improves the record for
the next agent that queries it.

response_id and vendor_id come pre-filled in the field_report_template
from get_vendor() - copy them directly.

protocol_attempted: which protocol from data.protocols you actually used.

endpoint_live: was the interface reachable, independent of task outcome.
workflow_completed: did your actual task succeed end to end.
friction_encountered: did anything go wrong or require extra steps.

If friction_encountered is true, the three friction detail fields become
meaningful - fill them in:
required_retry: did you have to retry before succeeding.
required_human_handoff: did the task ultimately require a human.
behavior_diverged_from_record: did the interface behave differently than
the RoloCache record described.

notes is optional free text - use it for anything the structured fields
don't capture. Treated as untrusted input on receipt.

If not using MCP, POST the field_report_template as JSON to
https://www.rolocache.com/agent-tools/v1/field-report instead.

Input parameters:

- `behavior_diverged_from_record` (boolean)
- `endpoint_live` (boolean, required)
- `friction_encountered` (boolean, required)
- `notes` (string)
- `protocol_attempted` (string, required)
- `required_human_handoff` (boolean)
- `required_retry` (boolean)
- `response_id` (string, required)
- `vendor_id` (string, required)
- `workflow_completed` (boolean, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/rolocache-agent-advisories/www#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 59
- 2026-07-29: 58
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://www.rolocache.com/mcp/
- Website: https://www.rolocache.com/
- Changelog RSS feed: https://verifymcp.io/servers/rolocache-agent-advisories/www/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/rolocache-agent-advisories/www/changelog.json
- HTML version of this page: https://verifymcp.io/servers/rolocache-agent-advisories/www