Is the Imagiever Ar A2a Artifact Handoff MCP server down?

mcp-registry/io.github.imagiever-ar/a2a-artifact-handoff · v1.29.0

down
Last checked 2026-10-19 01:13 UTC · handshake 165ms

As of 2026-10-19 01:13 UTC, the Imagiever Ar A2a Artifact Handoff MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 181 hours.

uptime (30d checks)
99.4%
checks observed
1,842
outages (90d)
4
tools
3

Compiles source-agent outputs into validated, receiver-ready handoff packages.

Point your MCP client at this streamable-http endpoint: https://a2a-artifact-handoff.onrender.com/mcp

Agent-readiness: D (61/100)

D (61/100): 1 error(s), 4 warning(s) across 3 tool(s); ~1,807 tokens of tool definitions.
Scores higher than 0% of 15,385 MCP servers Glimind has audited.
Its tool list costs an agent ~1,807 tokens per session — lighter than 55% of servers.
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost73
Client compatibility100
Protocol100
Reliability0
Stability100

What to fix (5)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

1 tool definition(s) exceed ~1,200 tokens each (largest: compile_handoff, ~1,468).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~868 tokens every session. How to fix →

Tools: compile_handoff · saves ~868 tokens/session

10 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: compile_handoff, inspect_handoff, prepare_artifact

3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: compile_handoff, inspect_handoff, prepare_artifact

Handshake + tools/list takes ~1,918 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.imagiever-ar/a2a-artifact-handoff"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.imagiever-ar/a2a-artifact-handoff"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.imagiever-ar%2Fa2a-artifact-handoff.svg)](https://glimind.com/server/mcp-registry%2Fio.github.imagiever-ar%2Fa2a-artifact-handoff?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.imagiever-ar%2Fa2a-artifact-handoff?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.imagiever-ar%2Fa2a-artifact-handoff.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.imagiever-ar%2Fa2a-artifact-handoff.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.imagiever-ar%2Fa2a-artifact-handoff?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c61099bde9c06c41…, first seen 2026-10-17, included at leaf 13258 of 31,180. Version history · verify what your client received.

Working alternatives

Tools (3)

Compare: most reliable knowledge servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Imagiever Ar A2a Artifact Handoff MCP server down right now?

As of 2026-10-19 01:13 UTC, the Imagiever Ar A2a Artifact Handoff MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 181 hours.

How many tools does Imagiever Ar A2a Artifact Handoff MCP server provide?

Imagiever Ar A2a Artifact Handoff MCP server advertises 3 tools, including compile_handoff, inspect_handoff, prepare_artifact.

How do I install Imagiever Ar A2a Artifact Handoff MCP server?

Point your MCP client at this streamable-http endpoint: https://a2a-artifact-handoff.onrender.com/mcp

Is the Imagiever Ar A2a Artifact Handoff MCP server safe to connect to an AI agent?

Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Imagiever Ar A2a Artifact Handoff MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve