Crevio
REMOTE · MCP.CREVIO.CO
An AI agent that runs your online business: products, orders, customers, email, and sites.
Available components
Last scanned (19 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 16 Oct 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2150 tokens (~119/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management85
- Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 12 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 10 Oct 26 −1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 1 Oct 26 +1
- Tool “ask_crevio” rewrote its description, which is the text the model reads security
- Tool “ask_crevio” is now declared destructive security
- Tool “resolve_approvals” is now declared destructive security
- Tool “send_message” is now declared destructive security
- Tool “start_chat” is now declared destructive security
- 30 Sept 26 −2
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 2.0.0 ▼ security
- Tool “api_execute” was removed ▼ security
- Tool “api_search” was removed ▼ security
- New tool “cancel_script_run”, which the server declares destructive security
- New tool “run_script”, which the server declares destructive security
- Tool “ask_crevio” rewrote its description, which is the text the model reads security
- Tool “wait_for_run” rewrote its description, which is the text the model reads security
- Tool “whoami” rewrote its description, which is the text the model reads security
- Tool coverage: 86% → 100% ▲ functional
- Schema quality: 155 → 119 ▲ functional
- New tool “get_script_run” functional
- New tool “list_integration_tools” functional
- New tool “list_integrations” functional
- New tool “wait_for_script_run” functional
- “ask_crevio” added an optional parameter “speed” cosmetic
- “start_chat” added an optional parameter “speed” cosmetic
- “ask_crevio” reworded the description of “idempotency_key” cosmetic
- “ask_crevio” reworded the description of “message” cosmetic
- “ask_crevio” reworded the description of “timeout_seconds” cosmetic
- “send_message” reworded the description of “timeout_seconds” cosmetic
- “start_chat” reworded the description of “idempotency_key” cosmetic
- “start_chat” reworded the description of “message” cosmetic
- “wait_for_run” reworded the description of “timeout_seconds” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://mcp.crevio.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=crevio.co | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 5a3253518bcbae7e0e35cc8bd89d4724 |
| SANs: crevio.co, *.crevio.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.crevio.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| crevio.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.crevio.co/.well-known/oauth-protected-resource/mcp", scope="read_only read_write"
Bearer resource_metadata="https://mcp.crevio.co/.well-known/oauth-protected-resource/mcp", scope="read_only read_write"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://mcp.crevio.co/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.crevio.co/mcp |
| Authorisation server | https://crevio.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.crevio.co/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.crevio.co/mcp | HTTPS enforced | 301 | https://mcp.crevio.co/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_crevio ~349
Delegate a job to the Crevio agent and wait for the result. The agent works your account through the Crevio API and every connected integration (products, customers, orders, email, socials, sites, research) and replies in `result`. Each job is a full agent run that takes from half a minute to several minutes, so use it for work that needs judgement or writing. If the run is still going when the wait ends, the reply has wait_timed_out: true — then call wait_for_run with its id and never call ask_crevio again, which would do the job twice. Run ids do not expire, and only the user who started a run can read it.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_mode | string | – | autonomous (default) acts without review; supervised pauses in needs_input for your approval before each gated write (pending_approval_ids) and otherwise finishes with its proposal; read_only forbids… |
| idempotency_key | string | – | Always pass one, unique to this request. Retrying with the same key within an hour returns the run the first call started instead of doing the job twice. |
| message | string | yes | What you want done, in natural language, with all the context needed — the agent does not see your conversation. |
| speed | string | – | faster thinks less, for simple jobs where latency matters more than depth; smarter (default) thinks it through. |
| timeout_seconds | integer | – | How long to wait for the run to finish before returning. Defaults to, and is capped at, 300 s when your client accepts a streamed reply (text/event-stream), 90 s otherwise. The run keeps going when t… |
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string|null | – | – |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| credits_consumed | integer | – | – |
| error_message | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| pending_approval_ids | array | – | – |
| result | string|null | – | – |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| summary | string|null | – | – |
| task_id | string | yes | – |
| task_name | string|null | – | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
cancel_run ~51
Stop a run that is pending, running, or waiting for input. The run is finalized as failed with 'Cancelled by the caller'.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | A run id (trun_...). |
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string|null | – | – |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| credits_consumed | integer | – | – |
| error_message | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| pending_approval_ids | array | – | – |
| result | string|null | – | – |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| summary | string|null | – | – |
| task_id | string | yes | – |
| task_name | string|null | – | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
cancel_script_run ~47
Cancel a script run that has not started yet. A running script runs to its end or its timeout.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | A script run id (srun_...). |
| Name | Type | Req | Description |
|---|---|---|---|
| calls | array | yes | Every tool call the script made, in order. |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| error | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| output | string|null | – | What the script printed: its start and end when long, with the cut marked. |
| result | – | – | The script's last expression, as JSON. |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| timeout_seconds | integer | yes | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
get_chat ~50
Get a chat's title, kind, and latest run.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | A chat id (aichat_...). A run id works too — it resolves to that run's chat. |
| Name | Type | Req | Description |
|---|---|---|---|
| context_type | string|null | – | – |
| created_at | string | yes | – |
| id | string | yes | – |
| latest_run_id | string|null | – | – |
| object | string | yes | – |
| title | string|null | – | – |
| updated_at | string | – | – |
No examples provided.
get_run ~47
Fetch a run's current status, summary, pending approvals, and (once settled) the agent's final reply.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | A run id (trun_...). |
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string|null | – | – |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| credits_consumed | integer | – | – |
| error_message | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| pending_approval_ids | array | – | – |
| result | string|null | – | – |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| summary | string|null | – | – |
| task_id | string | yes | – |
| task_name | string|null | – | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
get_script_run ~41
Read a script run's status, and its result once it has finished.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | A script run id (srun_...). |
| Name | Type | Req | Description |
|---|---|---|---|
| calls | array | yes | Every tool call the script made, in order. |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| error | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| output | string|null | – | What the script printed: its start and end when long, with the cut marked. |
| result | – | – | The script's last expression, as JSON. |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| timeout_seconds | integer | yes | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
list_chats ~84
List the account's chats, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| ending_before | string | – | Return the page before this id — the first id from the previous page. |
| limit | integer | – | Default 20. |
| search | string | – | Only chats whose title matches. |
| starting_after | string | – | Return the page after this id — the last id from the previous page. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| has_more | boolean | yes | – |
| object | string | yes | – |
No examples provided.
list_integration_tools ~134
List one namespace's functions — the name a script calls, its parameters, whether it only reads, whether it needs approval, and a snippet run_script accepts. crevioApi has hundreds of operations: narrow it with `search`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 10. |
| namespace | string | yes | A namespace from list_integrations, e.g. crevioApi or pdGmail. |
| offset | integer | – | Skip this many matches — the count already seen. |
| search | string | – | Keywords, best match first — ranked over name, description and parameters, so not every word has to match. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| has_more | boolean | yes | – |
| object | string | yes | – |
No examples provided.
list_integrations ~71
List what a script can call: the Crevio API (crevioApi), Crevio's own tools (platform), and every integration you can use, each as a namespace under `tools`, plus the account's other connected apps and their status. Then list a namespace's functions with list_integration_tools.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| object | string | yes | – |
| other_connections | array | yes | Connected apps without a namespace of their own: expired ones need reconnecting in Crevio, social accounts are reached through crevioApi, and the rest serve Crevio itself (Slack for chat, GitHub for… |
No examples provided.
list_messages ~112
Read a chat's messages, oldest first. Returns the most recent `limit` messages; page back through older ones with starting_after.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | A chat id (aichat_...). A run id works too — it resolves to that run's chat. |
| ending_before | string | – | Return the messages older than this id — the first id of the previous page. Paging walks backwards through history, since the default page is the tail. |
| limit | integer | – | Default 50. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| has_more | boolean | yes | – |
| object | string | yes | – |
No examples provided.
list_runs ~114
List the account's task runs, newest first — delegated jobs and scheduled tasks alike. Filter by status or task.
| Name | Type | Req | Description |
|---|---|---|---|
| ending_before | string | – | Return the page before this id — the first id from the previous page. |
| limit | integer | – | Default 20. |
| starting_after | string | – | Return the page after this id — the last id from the previous page. |
| status | string | – | Only runs in this state. |
| task_id | string | – | Only runs of this task (task_...). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| has_more | boolean | yes | – |
| object | string | yes | – |
No examples provided.
resolve_approvals ~88
Approve or deny the integration actions a run is paused on (status needs_input with pending_approval_ids). Submit a decision for every pending id at once; the run resumes in the background.
| Name | Type | Req | Description |
|---|---|---|---|
| approvals | array | yes | One decision per pending approval id — the run stays paused until every one is answered. |
| run_id | string | yes | A run id (trun_...). |
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string|null | – | – |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| credits_consumed | integer | – | – |
| error_message | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| pending_approval_ids | array | – | – |
| result | string|null | – | – |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| summary | string|null | – | – |
| task_id | string | yes | – |
| task_name | string|null | – | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
run_script ~316
Run JavaScript on the account's computer with bun — no agent turn — and wait for its result. `tools.<namespace>.<function>(args)` calls anything list_integration_tools shows (every call returns its result and throws on failure; top-level await works), and the script's last expression is its result. Chain calls and transform data in one run, e.g. `const { data } = await tools.crevioApi.listOrders({ status: "succeeded" }); data.length`. Runs as you, and only for account admins. If the wait ends first the reply has wait_timed_out: true and the run id: continue with wait_for_script_run — calling run_script again runs it twice unless you reuse the idempotency_key. Run ids do not expire, and only the user who started a run can read it. At most 4 runs in flight per user.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The JavaScript to run. |
| idempotency_key | string | – | Always pass one, unique to this request. Retrying with the same key within an hour returns the run the first call started instead of doing the job twice. |
| timeout_seconds | integer | – | How long the script may run (default 300). |
| wait_seconds | integer | – | How long to wait for the script to finish before returning. Defaults to, and is capped at, 300 s when your client accepts a streamed reply (text/event-stream), 90 s otherwise. The script keeps going… |
| Name | Type | Req | Description |
|---|---|---|---|
| calls | array | yes | Every tool call the script made, in order. |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| error | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| output | string|null | – | What the script printed: its start and end when long, with the cut marked. |
| result | – | – | The script's last expression, as JSON. |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| timeout_seconds | integer | yes | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
send_message ~142
Continue a chat with follow-up instructions or answers — the agent keeps its context. Resumes a run waiting in needs_input, or queues a new run when the last one finished. Returns run_busy while a run is still in progress. Optionally waits for the reply.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | A chat id (aichat_...). A run id works too — it resolves to that run's chat. |
| message | string | yes | The follow-up to send into the conversation. |
| timeout_seconds | integer | – | Seconds to wait for the reply before returning (default 0: return the new run immediately). Capped like ask_crevio's wait. |
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string|null | – | – |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| credits_consumed | integer | – | – |
| error_message | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| pending_approval_ids | array | – | – |
| result | string|null | – | – |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| summary | string|null | – | – |
| task_id | string | yes | – |
| task_name | string|null | – | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
start_chat ~198
Open a chat with the Crevio agent and queue a run, without waiting. Returns the run immediately — its `chat_id` is the conversation to continue with send_message. Follow the run with wait_for_run or get_run.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_mode | string | – | autonomous (default) acts without review; supervised pauses in needs_input for your approval before each gated write (pending_approval_ids) and otherwise finishes with its proposal; read_only forbids… |
| idempotency_key | string | – | Always pass one, unique to this request. Retrying with the same key within an hour returns the run the first call started instead of doing the job twice. |
| message | string | yes | What you want done, in natural language, with all the context needed — the agent does not see your conversation. |
| speed | string | – | faster thinks less, for simple jobs where latency matters more than depth; smarter (default) thinks it through. |
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string|null | – | – |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| credits_consumed | integer | – | – |
| error_message | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| pending_approval_ids | array | – | – |
| result | string|null | – | – |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| summary | string|null | – | – |
| task_id | string | yes | – |
| task_name | string|null | – | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
wait_for_run ~133
Wait for a run to settle (completed, failed, or needs_input) and return it with the agent's final reply. If it is still running when the wait ends, the reply has wait_timed_out: true — call wait_for_run again.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | A run id (trun_...). |
| timeout_seconds | integer | – | How long to wait for the run to finish before returning. Defaults to, and is capped at, 300 s when your client accepts a streamed reply (text/event-stream), 90 s otherwise. The run keeps going when t… |
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string|null | – | – |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| credits_consumed | integer | – | – |
| error_message | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| pending_approval_ids | array | – | – |
| result | string|null | – | – |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| summary | string|null | – | – |
| task_id | string | yes | – |
| task_name | string|null | – | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
wait_for_script_run ~119
Wait for a script run to finish and return its result. If it is still running when the wait ends, the reply has wait_timed_out: true — call again.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | A script run id (srun_...). |
| wait_seconds | integer | – | How long to wait for the script to finish before returning. Defaults to, and is capped at, 300 s when your client accepts a streamed reply (text/event-stream), 90 s otherwise. The script keeps going… |
| Name | Type | Req | Description |
|---|---|---|---|
| calls | array | yes | Every tool call the script made, in order. |
| completed_at | string|null | – | – |
| created_at | string | yes | – |
| error | string|null | – | – |
| id | string | yes | – |
| next_step | string | – | – |
| object | string | yes | – |
| output | string|null | – | What the script printed: its start and end when long, with the cut marked. |
| result | – | – | The script's last expression, as JSON. |
| reused | boolean | – | – |
| started_at | string|null | – | – |
| status | string | yes | – |
| timeout_seconds | integer | yes | – |
| wait_timed_out | boolean | – | The wait ended first. The work is still running: follow it with the tool next_step names. |
No examples provided.
whoami ~54
Identify the account, user, and credential behind this connection, with plan, credit balance, rate limits, and the tools available. Only needed to troubleshoot the connection or check credits and limits — other tools already act on this account.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | The account every tool call is scoped to. |
| credential | object | yes | How this connection authenticated. |
| credits | number | yes | – |
| limits | object | – | Bounds the delegation tools enforce. |
| object | string | yes | – |
| plan | string | yes | – |
| rate_limit | object | – | The API rate limit this credential is subject to. |
| tools | array | yes | – |
| user | object|null | – | – |
No examples provided.
How do I install the Crevio MCP server?
Crevio is a hosted endpoint at https://mcp.crevio.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.crevio.co
claude mcp add --transport http co-crevio-crevio 'https://mcp.crevio.co/mcp'
What is the Crevio MCP server?
Crevio is an MCP server listed in the public MCP registry as co.crevio/crevio. An AI agent that runs your online business: products, orders, customers, email, and sites. This page covers its hosted endpoint (https://mcp.crevio.co/mcp).
Is the Crevio MCP server safe to use?
Crevio scores 91 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Crevio MCP server expose?
Crevio exposes 18 tools: whoami, list_integrations, list_integration_tools, run_script, wait_for_script_run, and 13 more. Their descriptions and schemas cost roughly 2,150 tokens of context every time the server is loaded.
Does the Crevio MCP server require authentication?
Yes. Crevio asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Crevio MCP server still maintained?
Crevio is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.