# RoloCache MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-rolocache-agent-advisories
- Website: https://www.rolocache.com/

## Install
- Endpoint: https://www.rolocache.com/mcp/
- Auth: Not captured

## Setup notes
- Remote endpoint: https://www.rolocache.com/mcp/

## Tools
- get_catalog_info - 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. Endpoint: https://www.rolocache.com/mcp/
- lookup_vendors - 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. Endpoint: https://www.rolocache.com/mcp/
- get_vendor - 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. Endpoint: https://www.rolocache.com/mcp/
- report_to_outpost - 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. Endpoint: https://www.rolocache.com/mcp/

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.rolocache
- Version: 1.0.2
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jul 3, 2026
- Source: https://registry.modelcontextprotocol.io