Is the Unmark Unmarking MCP server down?

mcp-registry/ing.unmark/unmarking · v0.1.0

unknown
Last checked 2026-10-24 17:36 UTC · handshake 468ms

As of 2026-10-24 17:36 UTC, the Unmark Unmarking MCP server is unknown with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.7%
checks observed
3,615
outages (90d)
1
tools
2

Inspect and remove C2PA content credentials from AI-generated images, video and audio. Free, no key.

Point your MCP client at this streamable-http endpoint: https://api.unmark.ing/mcp

Agent-readiness: C (71/100)

C (71/100): 1 error(s), 1 warning(s) across 2 tool(s); ~262 tokens of tool definitions.
Scores higher than 5% of 15,748 MCP servers Glimind has audited.
Its tool list costs an agent ~262 tokens per session — lighter than 99% of servers.
80 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints5
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (4)

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(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: strip_file

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

1 of 2 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: strip_file

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fing.unmark%2Funmarking/fixes

strip_file 1 change
{
  "name": "strip_file",
  "description": "Removes the C2PA content credential from a file and returns a download link for the cleaned copy. Pixels, frames and samples stay untouched.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "format": "uri",
        "description": "Publicly reachable http(s) URL of an image, video or audio file. Local paths do not work with this hosted server."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  },
  "title": "Remove content credential"
}

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/ing.unmark/unmarking"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ing.unmark/unmarking"}) 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%2Fing.unmark%2Funmarking.svg)](https://glimind.com/server/mcp-registry%2Fing.unmark%2Funmarking?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fing.unmark%2Funmarking?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fing.unmark%2Funmarking.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fing.unmark%2Funmarking.svg
   :target: https://glimind.com/server/mcp-registry%2Fing.unmark%2Funmarking?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:b18eb278b609a79b…, first seen 2026-10-17, included at leaf 3339 of 72,708. Version history · verify what your client received.

Tools (2)

Compare: most reliable files 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 Unmark Unmarking MCP server down right now?

As of 2026-10-24 17:36 UTC, the Unmark Unmarking MCP server is unknown with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Unmark Unmarking MCP server provide?

Unmark Unmarking MCP server advertises 2 tools, including inspect_file, strip_file.

How do I install Unmark Unmarking MCP server?

Point your MCP client at this streamable-http endpoint: https://api.unmark.ing/mcp

Is the Unmark Unmarking MCP server safe to connect to an AI agent?

Glimind scanned all 2 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 Unmark Unmarking 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