Is the Gosadu Loophole Tape MCP server down?

mcp-registry/io.github.gosadu/loophole-tape · v0.9.0

As of 2026-10-17 14:22 UTC, the Gosadu Loophole Tape MCP server is up with a Glimind reliability score of 96/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 5 minutes.

pump.fun & Robinhood Chain launch data: radar, risk checks, delta feed, datasets, keys. x402 USDC

claude mcp add --transport http gosadu-loophole-tape-mcp-server https://api.loopholetape.com/mcp

{
  "mcpServers": {
    "gosadu-loophole-tape-mcp-server": {
      "type": "http",
      "url": "https://api.loopholetape.com/mcp"
    }
  }
}

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

Agent-readiness: A (95/100)

What to fix (2)

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.gosadu/loophole-tape"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.gosadu/loophole-tape"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~6,665 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.

Largest tool definitions

• subscribe_alerts ~510 tokens
• rhc_swap_build_checked ~390 tokens
• rhc_recent_launches ~362 tokens
• swap_build_checked ~301 tokens
• token_check ~290 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gosadu%2Floophole-tape.svg)](https://glimind.com/server/mcp-registry%2Fio.github.gosadu%2Floophole-tape?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.gosadu%2Floophole-tape?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gosadu%2Floophole-tape.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gosadu%2Floophole-tape.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.gosadu%2Floophole-tape?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:eaa7ff2fcc8a23c4…, first seen 2026-10-17, included at leaf 109 of 17,720. Version history · verify what your client received.

Tools (34)

• buy_api_key
• buy_dataset
• buy_trial_key
• catalog
• check_batch_risk
• check_coverage
• check_pumpfun_risk
• check_watchlist_risk
• creator_reputation
• health
• launches_screened
• launches_since
• market_regime
• mint_flow
• mint_holders
• mint_outcome
• mint_outcome_batch
• mint_risk_card
• new_launches_free
• pumpfun_recent_launches
• recent_graduations
• recent_rugs
• rhc_curve_card
• rhc_curve_trades
• rhc_recent_launches
• rhc_regime
• rhc_swap_build_checked
• sample_mint
• subscribe_alerts
• swap_build_checked
• token_check
• verdict
• wallet_profile
• watchlist_updates

Compare: most reliable payments servers · most reliable data servers · most reliable other servers · most reliable ml servers · most reliable finance servers

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

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

FAQ

Is the Gosadu Loophole Tape MCP server down right now?

As of 2026-10-17 14:22 UTC, the Gosadu Loophole Tape MCP server is up with a Glimind reliability score of 96/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 5 minutes.

How many tools does Gosadu Loophole Tape MCP server provide?

Gosadu Loophole Tape MCP server advertises 34 tools, including buy_api_key, buy_dataset, buy_trial_key, catalog, check_batch_risk.

How do I install Gosadu Loophole Tape MCP server?

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

Is the Gosadu Loophole Tape MCP server safe to connect to an AI agent?

Glimind scanned all 34 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 Gosadu Loophole Tape 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.