ai.imaginode/imaginode
REMOTE · IMAGINODE.AI · SCANNED SEP 20
Generate AI images and videos from 89 models on one credit balance, refunds on failure.
Available components
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. 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 supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the ai.imaginode/imaginode MCP server?
ai.imaginode/imaginode is a hosted endpoint at https://imaginode.ai/api/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 · imaginode.ai
claude mcp add --transport http ai-imaginode-imaginode 'https://imaginode.ai/api/mcp'
{
"mcpServers": {
"ai-imaginode-imaginode": {
"url": "https://imaginode.ai/api/mcp"
}
}
} {
"servers": {
"ai-imaginode-imaginode": {
"type": "http",
"url": "https://imaginode.ai/api/mcp"
}
}
} [mcp_servers.ai-imaginode-imaginode] url = "https://imaginode.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-imaginode-imaginode": {
"type": "remote",
"url": "https://imaginode.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-imaginode-imaginode --url 'https://imaginode.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-imaginode-imaginode:
url: "https://imaginode.ai/api/mcp" {
"McpServers": {
"ai-imaginode-imaginode": {
"Transport": "http",
"Url": "https://imaginode.ai/api/mcp"
}
}
} assistant mcp add ai-imaginode-imaginode -t streamable-http -u 'https://imaginode.ai/api/mcp'
{
"mcpServers": {
"ai-imaginode-imaginode": {
"type": "http",
"url": "https://imaginode.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 14 Sept 26 −46
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 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.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 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.
- 30 Aug 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.
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 20 Sept 2026 · Probed https://imaginode.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=imaginode.ai | CN=YR1,O=Let's Encrypt,C=US | 7 Aug 2026 | 5 Nov 2026 | RSA 2048 | SHA256-RSA | 5de2c5a08cdcdb3e28e9dc7a3ee69f48628 |
| SANs: imaginode.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of imaginode.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| imaginode.ai. | 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 connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://imaginode.ai/.well-known/oauth-protected-resource", scope="generate"
Bearer resource_metadata="https://imaginode.ai/.well-known/oauth-protected-resource", scope="generate"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self) |
| www-authenticate | Bearer resource_metadata="https://imaginode.ai/.well-known/oauth-protected-resource", scope="generate" |
Protected resource metadata
| Document | https://imaginode.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://imaginode.ai/api/mcp |
| Authorisation server | https://imaginode.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://imaginode.ai/api/mcp | Auth required | 401 | |
| http (plaintext) | http://imaginode.ai/api/mcp | HTTPS enforced | 308 | https://imaginode.ai/api/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 →
generate_image Generate an image ~156
Generate an image from a text prompt (optionally with input images for editing or reference). Waits for the result and returns the image URL. Costs credits from the connected Imaginode account; failures are refunded.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | Optional aspect ratio like 16:9, 1:1, 9:16. |
| image_urls | array | – | Optional input image URLs (editing or reference). Must be media hosted on the Imaginode account (Firebase Storage URLs from the media library or previous generations). |
| model | string | – | Model key from list_models (kind image). Default: nano-banana-2. |
| prompt | string | yes | What to generate, in natural language. English works best. |
No output schema declared.
No examples provided.
generate_video Generate a video ~225
Start a video generation from a text prompt (optionally with a start image). Returns immediately with a request_id and the cost in credits: poll get_generation_status every 30 seconds until it completes (typically 1 to 5 minutes, up to 30 for long jobs). Failures are refunded.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | Aspect ratio like 16:9 or 9:16 (text-to-video only). |
| audio | boolean | – | Generate audio, for models that support it. |
| duration | string | – | Duration in seconds, among the model's durations (see list_models). |
| image_url | string | – | Optional start image URL (image-to-video). Must be media hosted on the Imaginode account (Firebase Storage URL from the media library or a previous generation). |
| model | string | – | Model key from list_models (kind video). Default: seedance-2. |
| prompt | string | yes | What to generate, in natural language. English works best. |
| resolution | string | – | Resolution among the model's resolutions (see list_models). |
No output schema declared.
No examples provided.
get_generation_status Get generation status ~56
Check a generation started with generate_video (or a generate_image that timed out). Returns running, completed (with output URLs) or failed (refunded).
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request_id returned by the generate tool. |
No output schema declared.
No examples provided.
list_models List Imaginode models ~79
List the available AI models with their kind (image, video), default cost in credits (1 credit = $0.012, or €0.01 when billed in euros) and billable options. Call this before generating if you need a specific model, otherwise sensible defaults are used.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only return models of this kind. |
No output schema declared.
No examples provided.
What is the ai.imaginode/imaginode MCP server?
ai.imaginode/imaginode is an MCP server listed in the public MCP registry as ai.imaginode/imaginode. Generate AI images and videos from 89 models on one credit balance, refunds on failure. This page covers its hosted endpoint (https://imaginode.ai/api/mcp).
Is the ai.imaginode/imaginode MCP server safe to use?
ai.imaginode/imaginode scores 39 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 ai.imaginode/imaginode MCP server expose?
ai.imaginode/imaginode exposes 4 tools: list_models, generate_image, generate_video, get_generation_status. Their descriptions and schemas cost roughly 516 tokens of context every time the server is loaded.
Does the ai.imaginode/imaginode MCP server require authentication?
Yes. ai.imaginode/imaginode 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 ai.imaginode/imaginode MCP server still maintained?
ai.imaginode/imaginode is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.