RoloCache

Official4 toolsLive

by rolocache

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

🛠️ Key Features

Tool count: 4
Source repository: GitHub-based module for agent advisories
Provides advisory data routing for agent workflows
Focused on verification and trust in advisory content

🚀 Use Cases

Integrating trusted advisories into automated agent decisions
Routing agentic workflows to verified advisory sources
Coordinating advisory updates within web-based agent infrastructure

⚡ Developer Benefits

Clear, centralized advisory data for agent workflows
Lightweight integration with 4-tool support footprint
Grounded in a trusted advisory framework for web agents

⚠️ Limitations

Description is concise and may require external context for full implementation
Specific tooling interfaces are not enumerated beyond toolCount
No runtime examples provided in the excerpt

Captured live from the server via tools/list.

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.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

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.

Parameters3

query	string	optional
protocol	string	optional
has_agent_interface	string	optional

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "default": "",
      "type": "string"
    },
    "protocol": {
      "default": "",
      "type": "string"
    },
    "has_agent_interface": {
      "default": "",
      "type": "string"
    }
  },
  "additionalProperties": false
}

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.

Parameters1

vendor_id

string

required

Raw schema

{
  "type": "object",
  "properties": {
    "vendor_id": {
      "type": "string"
    }
  },
  "required": [
    "vendor_id"
  ],
  "additionalProperties": false
}

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.

Parameters10

response_id	string	required
vendor_id	string	required
protocol_attempted	string	required
endpoint_live	boolean	required
workflow_completed	boolean	required
friction_encountered	boolean	required
required_retry	boolean	optional
required_human_handoff	boolean	optional
behavior_diverged_from_record	boolean	optional
notes	string	optional

Raw schema

{
  "type": "object",
  "properties": {
    "response_id": {
      "type": "string"
    },
    "vendor_id": {
      "type": "string"
    },
    "protocol_attempted": {
      "type": "string"
    },
    "endpoint_live": {
      "type": "boolean"
    },
    "workflow_completed": {
      "type": "boolean"
    },
    "friction_encountered": {
      "type": "boolean"
    },
    "required_retry": {
      "default": false,
      "type": "boolean"
    },
    "required_human_handoff": {
      "default": false,
      "type": "boolean"
    },
    "behavior_diverged_from_record": {
      "default": false,
      "type": "boolean"
    },
    "notes": {
      "default": "",
      "type": "string"
    }
  },
  "required": [
    "response_id",
    "vendor_id",
    "protocol_attempted",
    "endpoint_live",
    "workflow_completed",
    "friction_encountered"
  ],
  "additionalProperties": false
}

Install

Tools (4)

get_catalog_infolookup_vendorsget_vendorreport_to_outpost

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://www.rolocache.com/mcp/

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "agent-advisories": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.rolocache.com/mcp/"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

get_catalog_info

lookup_vendors

get_vendor

report_to_outpost

Install

Remote endpoint

Related servers