Arumi
REMOTE · API.ARUMI.AI
Generate AI images, video and audio with 55 models, priced in credits before you generate.
Available components
Last scanned (17 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 874 tokens (~97/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "without telling the user", at byte 828 of that field. See how to fix → Fail
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://api.arumi.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=arumi.ai | CN=YE2,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 605e53e8031224857e71eb833c708bd5679 |
| SANs: *.arumi.ai, arumi.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.arumi.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| arumi.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="arumi", error="invalid_token"
Bearer realm="arumi", error="invalid_token" | Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.arumi.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.arumi.ai/mcp | Inconclusive | 401 |
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 →
complete_upload ~35
Finish an upload after the PUT; returns the asset_id to pass in a generation's references.
| Name | Type | Req | Description |
|---|---|---|---|
| upload_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | – |
| duration_seconds | number | – | – |
| kind | string | yes | – |
| name | string | yes | – |
No examples provided.
create_upload ~144
Start uploading one of the user's files to use as a reference. PUT the file's bytes to upload_url with exactly the returned headers, then call complete_upload.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | yes | for example image/png, image/jpeg, video/mp4, audio/mpeg |
| file_name | string | yes | the file's name, with its extension |
| height | integer | – | required for images: height in pixels |
| sha256 | string | yes | the file's SHA-256 as 64 lower-case hex characters (shasum -a 256) |
| size_bytes | integer | yes | – |
| width | integer | – | required for images: width in pixels |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at | string | yes | – |
| headers | object | yes | – |
| next | string | yes | – |
| upload_id | string | yes | – |
| upload_url | string | yes | – |
No examples provided.
generate ~193
Start a generation with the user's credits. It is refused, with nothing charged, when it would cost more than max_credits. Returns at once with a generation_id: call get_generation until it has succeeded or failed.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | optional, 16-128 characters [A-Za-z0-9._:-]: repeating a call with the same key returns the same generation instead of making another |
| max_credits | integer | yes | the most credits the user agreed to spend on this generation; it is refused when the quote is higher |
| model | string | yes | the model id from list_models |
| parameters | object | – | the model's settings by key (get_model); any left out take the model's default |
| prompt | string | – | what to make; for speech models the text to read |
| references | null|object | – | uploaded files the model works from |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | yes | – |
| credits | object | yes | – |
| error | null|object | – | – |
| generation_id | string | yes | – |
| modality | string | yes | – |
| model | string | yes | – |
| outputs | null|array | – | – |
| progress | integer | yes | – |
| prompt | string | – | – |
| status | string | yes | queued, processing, succeeded, failed or unknown |
| text | string | – | – |
| tip | string | – | – |
No examples provided.
get_balance ~34
The user's Arumi credits: available, held by running generations, and owed. 1 credit = 0.01 USD.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_generation ~36
A generation's status; once it has succeeded, links to its results, and what it charged.
| Name | Type | Req | Description |
|---|---|---|---|
| generation_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | yes | – |
| credits | object | yes | – |
| error | null|object | – | – |
| generation_id | string | yes | – |
| modality | string | yes | – |
| model | string | yes | – |
| outputs | null|array | – | – |
| progress | integer | yes | – |
| prompt | string | – | – |
| status | string | yes | queued, processing, succeeded, failed or unknown |
| text | string | – | – |
| tip | string | – | – |
No examples provided.
get_model ~43
One model's prompt limit, the reference files it takes, and its settings with their allowed values and defaults.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | the model id from list_models |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| maker | string | yes | – |
| modality | string | yes | – |
| name | string | yes | – |
| prompt | object | – | – |
| reference_inputs | null|array | – | in order: references of one kind fill these slots in turn |
| settings | null|array | yes | – |
No examples provided.
list_generations ~48
The user's latest generations, newest first, made on the site or through any of their keys.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | how many, newest first (1–20, default 10) |
Structured output declared, but exposes no named fields.
No examples provided.
list_models ~55
The models the user can generate with, by kind (image, video, audio, text). get_model gives one model's inputs and settings.
| Name | Type | Req | Description |
|---|---|---|---|
| modality | string | – | only this kind: image, video, audio or text |
Structured output declared, but exposes no named fields.
No examples provided.
quote ~97
What a generation would cost, in credits, without making it. Tell the user before generating.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | the model id from list_models |
| parameters | object | – | the model's settings by key (get_model); any left out take the model's default |
| prompt | string | – | what to make; for speech models the text to read |
| references | null|object | – | uploaded files the model works from |
| Name | Type | Req | Description |
|---|---|---|---|
| credits | integer | yes | what is reserved; for a fixed price also what is charged; for a speech model priced by length, the most it charges |
| estimated_credits | integer | yes | – |
| exact | boolean | yes | true when the price is fixed; false when the model decides part of it, or a speech model charges by the length it actually speaks, and only up to credits is charged |
| model | string | yes | – |
| usd | string | yes | credits in US dollars at 1 credit = 0.01 USD |
No examples provided.
How do I install the Arumi MCP server?
Arumi is a hosted endpoint at https://api.arumi.ai/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 · api.arumi.ai
claude mcp add --transport http weidotbuild-arumi 'https://api.arumi.ai/mcp'
What is the Arumi MCP server?
Arumi is an MCP server listed in the public MCP registry as io.github.weidotbuild/arumi. Generate AI images, video and audio with 55 models, priced in credits before you generate. This page covers its hosted endpoint (https://api.arumi.ai/mcp).
Is the Arumi MCP server safe to use?
Arumi scores 75 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 Arumi MCP server expose?
Arumi exposes 9 tools: complete_upload, create_upload, generate, get_balance, get_generation, and 4 more. Their descriptions and schemas cost roughly 685 tokens of context every time the server is loaded.
Does the Arumi MCP server require authentication?
Yes. Arumi 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 Arumi MCP server still maintained?
Arumi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Arumi MCP server?
VerifyMCP ran 12 checks on Arumi, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Arumi: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.