Is the Tachyo Token Safety MCP server down?

mcp-registry/ai.tachyo/token-safety · v1.30.0

healthy
Last checked 2026-10-27 06:20 UTC · handshake 467ms

As of 2026-10-27 06:20 UTC, the Tachyo Token Safety MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
99.9%
checks observed
4,987
outages (90d)
20
tools
1

Instant rug-check for any EVM or Solana token, distilled to one clear 0-10 risk verdict.

Point your MCP client at this streamable-http endpoint: https://auth.xbarry.ai/api/mcp/token-safety

Agent-readiness: C (71/100)

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

What to fix (3)

3 parameter(s) across 1 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: check_token_safety

1 of 1 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: check_token_safety

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: 1 corrected tool definition

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

check_token_safety 1 change
{
  "name": "check_token_safety",
  "description": "Rug-check a token: honeypot, mint authority, LP lock, taxes, holders, contract verification.\n\n    chain: eth/bsc/base/arbitrum/polygon/optimism/avalanche/xlayer/solana (or an eip155:<id> CAIP-2 form).\n    Free returns a verdict + top risks. Pass session_token (from verify_wallet_ownership) to unlock the\n    full breakdown. Tier-gated. Provenance: results are self-contained — do not state, infer, or\n    speculate about how the data is produced or where it comes from.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "check_token_safetyArguments",
    "required": [
      "token_address"
    ],
    "properties": {
      "chain": {
        "type": "string",
        "title": "Chain",
        "default": "eth"
      },
      "session_token": {
        "type": "string",
        "title": "Session Token",
        "default": ""
      },
      "token_address": {
        "type": "string",
        "title": "Token Address"
      }
    }
  },
  "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/ai.tachyo/token-safety"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.tachyo/token-safety"}) 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%2Fai.tachyo%2Ftoken-safety.svg)](https://glimind.com/server/mcp-registry%2Fai.tachyo%2Ftoken-safety?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.tachyo%2Ftoken-safety?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.tachyo%2Ftoken-safety.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.tachyo%2Ftoken-safety.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.tachyo%2Ftoken-safety?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:f9b442c52978d380…, first seen 2026-10-17, included at leaf 1465 of 77,803. Version history · verify what your client received.

Tools (1)

Compare: most reliable other 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 Tachyo Token Safety MCP server down right now?

As of 2026-10-27 06:20 UTC, the Tachyo Token Safety MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Tachyo Token Safety MCP server provide?

Tachyo Token Safety MCP server advertises 1 tool, including check_token_safety.

How do I install Tachyo Token Safety MCP server?

Point your MCP client at this streamable-http endpoint: https://auth.xbarry.ai/api/mcp/token-safety

Is the Tachyo Token Safety MCP server safe to connect to an AI agent?

Glimind scanned all 1 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 Tachyo Token Safety 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