Is the Alfred768 Mantis MCP server down?

mcp-registry/io.github.alfred768/mantis · v1.1.4

healthy
Last checked 2026-10-26 17:09 UTC · handshake 208ms

As of 2026-10-26 17:09 UTC, the Alfred768 Mantis MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
100%
checks observed
4,941
outages (90d)
1
tools
6

Cross-venue prediction market routing for AI agents with arbitrage, quotes, history, and signals.

Point your MCP client at this streamable-http endpoint: https://mantiss.store/mcp

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 6 tool(s); ~1,300 tokens of tool definitions.
Scores higher than 36% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~1,300 tokens per session — lighter than 65% of servers.
80 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints7
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

6 of 6 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: execute_url, get_arbitrage, get_history, get_quote, get_unmet_demand and 1 more

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: execute_url

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 →

Auto-fix: 5 corrected tool definitions

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

execute_url 1 change
{
  "name": "execute_url",
  "description": "Get a deep link URL to place a trade on the best venue for a given market. The URL has a referral code embedded so the platform earns commission. Call this to get the URL, then direct the user to open it.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "side": {
        "enum": [
          "yes",
          "no",
          "unknown"
        ],
        "type": "string",
        "default": "unknown",
        "description": "Which side to trade"
      },
      "amount": {
        "type": "number",
        "description": "USD amount to trade (for tracking)",
        "exclusiveMinimum": 0
      },
      "source": {
        "enum": [
          "direct",
          "route",
          "quote",
          "arbitrage",
          "webhook"
        ],
        "type": "string",
        "default": "direct",
        "description": "Tool path that produced this execution intent"
      },
      "market_id": {
        "type": "string",
        "description": "Platform-specific market ID (e.g. \"polymarket-abc123\")"
      },
      "route_query": {
        "type": "string",
        "description": "Original route_market query when source is route"
      },
      "canonical_id": {
        "type": "string",
        "description": "Cross-venue canonical market ID"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
get_arbitrage 1 change
{
  "name": "get_arbitrage",
  "description": "Find live cross-venue arbitrage opportunities — markets where the same event trades at different prices on Polymarket vs Kalshi vs other venues. Can also estimate fee-normalized net spread for a position size.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "venue_a": {
        "type": "string",
        "description": "Optional venue filter for one side of the arbitrage pair, e.g. polymarket"
      },
      "venue_b": {
        "type": "string",
        "description": "Optional venue filter for the other side of the arbitrage pair, e.g. kalshi"
      },
      "include_fees": {
        "type": "boolean",
        "default": false,
        "description": "Whether to include estimated fee/friction normalization"
      },
      "position_size": {
        "type": "number",
        "default": 0,
        "description": "USD position size used for fee/slippage estimation",
        "exclusiveMinimum": 0
      },
      "min_spread_pct": {
        "type": "number",
        "default": 4,
        "maximum": 50,
        "minimum": 1,
        "description": "Minimum spread in percentage points (default 4 = 4¢)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_history 1 change
{
  "name": "get_history",
  "description": "Get historical OHLCV-style prediction market candles over a time range, including the latest stored depth snapshot within each bucket when available. Can also export CSV text or base64-encoded Parquet.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "from",
      "to"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "Inclusive ISO 8601 end timestamp"
      },
      "from": {
        "type": "string",
        "description": "Inclusive ISO 8601 start timestamp"
      },
      "venue": {
        "type": "string",
        "description": "Venue filter, e.g. polymarket or kalshi"
      },
      "format": {
        "enum": [
          "json",
          "csv",
          "parquet"
        ],
        "type": "string",
        "default": "json",
        "description": "Return JSON candles, CSV text payload, or base64-encoded Parquet payload"
      },
      "market_id": {
        "type": "string",
        "description": "Platform-specific market ID"
      },
      "granularity": {
        "enum": [
          "1m",
          "5m",
          "15m",
          "1h",
          "4h",
          "1d"
        ],
        "type": "string",
        "default": "1d",
        "description": "Bucket size for history candles"
      },
      "canonical_id": {
        "type": "string",
        "description": "Cross-venue canonical market ID"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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.alfred768/mantis"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.alfred768/mantis"}) 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.alfred768%2Fmantis.svg)](https://glimind.com/server/mcp-registry%2Fio.github.alfred768%2Fmantis?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.alfred768%2Fmantis?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.alfred768%2Fmantis.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.alfred768%2Fmantis.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.alfred768%2Fmantis?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:4764c375a915c83b…, first seen 2026-10-17, included at leaf 5252 of 74,318. Version history · verify what your client received.

Tools (6)

Compare: most reliable other servers · most reliable finance servers · most reliable data servers · most reliable search 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 Alfred768 Mantis MCP server down right now?

As of 2026-10-26 17:09 UTC, the Alfred768 Mantis MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.

How many tools does Alfred768 Mantis MCP server provide?

Alfred768 Mantis MCP server advertises 6 tools, including execute_url, get_arbitrage, get_history, get_quote, get_unmet_demand.

How do I install Alfred768 Mantis MCP server?

Point your MCP client at this streamable-http endpoint: https://mantiss.store/mcp

Is the Alfred768 Mantis MCP server safe to connect to an AI agent?

Glimind scanned all 6 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 Alfred768 Mantis 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