Assistant tool

coprsetr_find_guides

Read-only tool that finds Coprsetr's source-linked compliance, privacy, security and trust guides by words, topic or region. No account needed.

Updated November 17, 2026

Website
OneLifeVibe hub
Class
Read · no account needed
Returns
count, guides[]: slug, title, name, type, topic, region, summary, steps, url; note, url

Find Coprsetr's source-linked guides to compliance, privacy, security and trust (no account needed), by words, topic or region: SOC 2, ISO 27001, GDPR, FedRAMP, PCI DSS, HIPAA and more. Returns the guide's name, what it is, how many steps it has and a link. Not legal advice.

Where you can call it

Inputs

ArgumentTypeNotes
query optionalstring ≤120Words to find a guide by, e.g. SOC 2 or customer security questionnaire.
topic optionalstring ≤40Only one topic, e.g. privacy or security.
region optionalstring ≤40Only one region or country.
limit optionalinteger 1-20How many (default 8).

Example request

POST https://onelifevibe.com/mcp/free

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "coprsetr_find_guides",
    "arguments": {
      "limit": 10
    }
  }
}

Other hub tools

What it does

coprsetr_find_guides searches Coprsetr's guides to compliance, privacy, security and trust. You can search by words, narrow to one topic, narrow to one region, or set how many results come back. It covers frameworks such as SOC 2, ISO 27001, GDPR, FedRAMP, PCI DSS and HIPAA, and it works without an account. The tool is a Read tool: it changes nothing and is safe to repeat. It returns guide summaries and links, not legal advice.

Each result helps someone pick a guide before opening it. The response gives the guide's name, a short summary, the topic and region, the number of steps and a URL. It also returns a slug and type. On the account connector at https://onelifevibe.com/mcp the tool is served with no token or identity, so it never returns account data.

When an assistant should call it

Call it when someone asks what Coprsetr has on a framework, a compliance question, a privacy or security topic, or a region. It is a good first call when you need a shortlist. A question about SOC 2 or a customer security questionnaire can go in query. If the request is broad, use topic or region to keep the results focused.

Use it before coprsetr_get_guide, the other tool on Coprsetr, so you can point to the right guide and link. Keep the response framed as guides and sources, not legal advice. If someone needs advice about their own obligations, point them to the guide and the site's own material rather than giving a conclusion.

Inputs and an example call

All inputs are optional. query takes words up to 120 characters, such as SOC 2 or customer security questionnaire. topic takes one topic up to 40 characters, for example privacy or security. region takes one region or country up to 40 characters. limit is an integer from 1 to 20 and defaults to 8.

Call the free connector at https://onelifevibe.com/mcp/free. A request with limit 10 looks like this:

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"coprsetr_find_guides","arguments":{"limit":10}}}

Add query, topic or region inside arguments when you need a narrower search.

What comes back

The result contains count, guides and a note, plus a url. count is the number of guides in this response. guides is a list, and each entry has slug, title, name, type, topic, region, summary, steps and url. steps is the number of steps in the guide. summary is a short description you can show before someone opens it.

Use title and name for display, summary for context, and url for the link. The note and top-level url are returned alongside the list. There is no account data in the response, including when the call goes through the account connector.

Errors, limits and safety

Keep query within 120 characters and topic and region within 40. Use a limit between 1 and 20; the default is 8. The free connector is rate-limited, so if you send many calls, pace them and retry after a pause if needed.

coprsetr_find_guides is read-only and idempotent: repeating the same call does not change anything. It never returns account data. It switches itself on when Coprsetr lists it as an anonymous tool; until then the connectors do not offer it. If your client does not show the tool, that listing has not happened yet. If a call fails, read the error the connector returns and correct the request. The guides are not legal advice.

Questions

Do I need an account to use coprsetr_find_guides?

No. It is available on the free connector at https://onelifevibe.com/mcp/free with no sign-in, read-only and rate-limited. It is also served on the account connector, still without account data.

What does the steps field tell me?

It is how many steps the guide has. Use it to judge the size of a guide before you open it, along with summary, topic and region.

Why is coprsetr_find_guides missing from my MCP client?

The tool switches itself on when Coprsetr lists it as an anonymous tool. Until then the connectors do not offer it. Once listed, it appears on the free connector and the account connector.

Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.

Get a free key Connector guide

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.