Is the Danelas Realask MCP server down?

mcp-registry/io.github.danelas/realask · v0.3.0

Also listed as github/danelas/realask-mcp

healthy
Last checked 2026-10-22 12:11 UTC · handshake 79ms

As of 2026-10-22 12:11 UTC, the Danelas Realask MCP server is up with a Glimind reliability score of 93/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 6 minutes.

uptime (30d checks)
100%
checks observed
4,263
outages (90d)
1
tools
5

Ask a US local business a current question by phone. Typed, timestamped answers for agents; x402.

Install Danelas Realask MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http danelas-realask-mcp-server https://realask.net/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "danelas-realask-mcp-server": {
      "type": "http",
      "url": "https://realask.net/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 2 warning(s) across 5 tool(s); ~1,694 tokens of tool definitions.
Scores higher than 12% of 15,512 MCP servers Glimind has audited.
Its tool list costs an agent ~1,694 tokens per session — lighter than 60% of servers.
73 → 75 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions48
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

5 of 5 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: get_verification_result, get_verification_status, purchase_quote, quote_real_world_action, quote_real_world_answer

7 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: purchase_quote, quote_real_world_action, quote_real_world_answer

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: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.danelas%2Frealask/fixes

get_verification_result 1 change
{
  "name": "get_verification_result",
  "description": "Read-only. The answer itself: typed facts, evidence excerpts, timestamps, confidence scores, freshness, and an explicit list of what could not be verified. Free, and safe to call repeatedly. If the job is not final yet the response is provisional (http_status 202) - poll until 200, or watch get_verification_status for a terminal state first. A completed job answers every required criterion; a partial one answers some and says so in limitations.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "job_id",
      "job_token"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "description": "job_id returned by purchase_quote, e.g. 'job_gf8t5wwfrtgpjcdc'"
      },
      "job_token": {
        "type": "string",
        "description": "job_token returned once by purchase_quote; the bearer token for this job. Not recoverable if lost - a new job would have to be purchased."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get verification result"
}
get_verification_status 1 change
{
  "name": "get_verification_status",
  "description": "Read-only progress check on a job bought with purchase_quote. Free, changes nothing, and safe to call repeatedly. Returns the state plus a progress object (businesses discovered, call attempts made). States are queued, discovering, calling or extracting while the job is still running, and completed, partial, failed, timed_out or canceled once it is final. Poll every 15-30 seconds; live calls take minutes. Use this to decide WHEN to read the answer; use get_verification_result to read the answer ",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "job_id",
      "job_token"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "description": "job_id returned by purchase_quote, e.g. 'job_gf8t5wwfrtgpjcdc'"
      },
      "job_token": {
        "type": "string",
        "description": "job_token returned once by purchase_quote; the bearer token for this job. Not recoverable if lost - a new job would have to be purchased."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get verification job status"
}

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

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

Tools (5)

Compare: most reliable other servers · most reliable payments 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 Danelas Realask MCP server down right now?

As of 2026-10-22 12:11 UTC, the Danelas Realask MCP server is up with a Glimind reliability score of 93/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 6 minutes.

How many tools does Danelas Realask MCP server provide?

Danelas Realask MCP server advertises 5 tools, including get_verification_result, get_verification_status, purchase_quote, quote_real_world_action, quote_real_world_answer.

How do I install Danelas Realask MCP server?

Point your MCP client at this streamable-http endpoint: https://realask.net/mcp

Is the Danelas Realask MCP server safe to connect to an AI agent?

Glimind scanned all 5 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 Danelas Realask 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