Is the HypePaper MCP server down?

mcp-registry/app.hypepaper/hypepaper · v2.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 16:00 UTC · handshake 249ms

As of 2026-11-22 16:00 UTC, the HypePaper MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
99.9%
checks observed
1,037
outages (90d)
1
tools
58

State of the art, trending papers, benchmarks, citations and topic experts from HypePaper.

Point your MCP client at this streamable-http endpoint: https://api.hypepaper.app/api/v1/mcp

Agent-readiness: D (69/100)

D (69/100): 0 error(s), 3 warning(s) across 58 tool(s); ~11,384 tokens of tool definitions.
Scores higher than 3% of 27,640 MCP servers Glimind has audited.
Its tool list costs an agent ~11,384 tokens per session — more than 85% of servers.
69 → 69 since 2026-11-15
no tool-poisoning patterns
Descriptions38
Safety hints30
Schemas100
Protocol100
Stability100
Token cost75
Reliability100
Client compatibility70

What to fix (4)

58 of 58 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: account, affiliation_profile, api_catalog, api_get, api_get_llm and 53 more

58 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

86 parameter(s) across 43 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: affiliation_profile, api_catalog, author_papers, benchmark_timeline, citation_graph and 38 more

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

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

api_get 1 change
{
  "name": "api_get",
  "description": "Call one read-only HypePaper API route from api_catalog as yourself and return its JSON. Free responses are cut at 24 KB. [Free · 1 credit]",
  "inputSchema": {
    "type": "object",
    "required": [
      "path"
    ],
    "properties": {
      "path": {
        "type": "string",
        "maxLength": 500,
        "minLength": 1,
        "description": "A route from api_catalog with its path params filled in, e.g. /api/v1/papers/<uuid>/results-arena (the /api/v1 prefix is optional)."
      },
      "params": {
        "type": "object",
        "description": "Query parameters: scalars or lists of scalars."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
api_get_llm 1 change
{
  "name": "api_get_llm",
  "description": "Call one LLM-backed HypePaper API route (explain, tldr, translate, lit-review, briefing, …) from api_catalog and return its JSON. [Free · 5 credits + AI credits]",
  "inputSchema": {
    "type": "object",
    "required": [
      "path"
    ],
    "properties": {
      "path": {
        "type": "string",
        "maxLength": 500,
        "minLength": 1,
        "description": "A route from api_catalog with its path params filled in, e.g. /api/v1/papers/<uuid>/results-arena (the /api/v1 prefix is optional)."
      },
      "params": {
        "type": "object",
        "description": "Query parameters: scalars or lists of scalars."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
compare_on_benchmark 1 change
{
  "name": "compare_on_benchmark",
  "description": "Compare 2–5 papers head-to-head on the datasets and metrics they share; returns wins, losses and the evidence rows. Only complete, matching experimental protocols are compared. coverage has one row per paper: comparison_status compared, no_shared_lane (its stored lanes are listed) or no_stored_result. A number not returned here is not stored; say so, never supply it. [Free · 8 credits]",
  "inputSchema": {
    "type": "object",
    "required": [
      "paper_ids"
    ],
    "properties": {
      "paper_ids": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 5,
        "minItems": 2
      },
      "dataset_key": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "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/app.hypepaper/hypepaper"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.hypepaper/hypepaper"}) 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fapp.hypepaper%2Fhypepaper.svg)](https://glimind.com/server/mcp-registry%2Fapp.hypepaper%2Fhypepaper?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fapp.hypepaper%2Fhypepaper?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fapp.hypepaper%2Fhypepaper.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1a8ed59af74be169…, first seen 2026-11-15, included at leaf 279014 of 384,527. Version history · verify what your client received.

Tools (58)

Compare: most reliable other servers · most reliable retrieval servers · most reliable knowledge servers · most reliable ml 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the HypePaper MCP server down right now?

As of 2026-11-22 16:00 UTC, the HypePaper MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.

How many tools does HypePaper MCP server provide?

HypePaper MCP server advertises 58 tools, including account, affiliation_profile, api_catalog, api_get, api_get_llm.

How do I install HypePaper MCP server?

Point your MCP client at this streamable-http endpoint: https://api.hypepaper.app/api/v1/mcp

Is the HypePaper MCP server safe to connect to an AI agent?

Glimind scanned all 58 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 HypePaper 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