RoloCache

endpoint

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

door code

c89bf51634885ae4

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is RoloCache live?

Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.

Is RoloCache free to use?

Yes — the hub reached it with no key and no payment.

What tools does RoloCache have?

4 tools: report_to_outpost, get_vendor, get_catalog_info, lookup_vendors.

Is RoloCache safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_catalog_info reads open 13h ago

  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.

  mcp-tool

  12345

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

  arguments 5 lines copy
• lookup_vendors reads open 13h ago

  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.

  mcp-tool

  123456789101112131415161718

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

  arguments 18 lines copy
• report_to_outpost changes data unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748

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

  arguments 48 lines copy
• get_vendor reads unknown 13h ago

  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.

  mcp-tool

  123456789101112

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

  arguments 12 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.