Skip to content

GL1TCH Token Safety MCP server

io.github.gl1tchbased-pixel/gl1tchgl1tchbased-pixelstreamable-httpv1.0.0Scanned

Token rug-risk scans, Know Your Agent wallet checks and deployer reputation for AI agents.

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the GL1TCH Token Safety MCP server can do

The GL1TCH Token Safety MCP server is published by the GitHub account gl1tchbased-pixel. It has 4 tools. It can create or change data (3 tools: scan_token, check_agent_wallet and deployer_reputation), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • check_agent_walletTrust score and level for an AI-agent wallet (or any wallet) before you transact with it: signature-verified identity plus its on-chain track record in GL1TCH scans.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Trust score and level for an AI-agent wallet (or any wallet) before you transact with it: signature-verified identity plus its on-chain track record in GL1TCH scans.
  • deployer_reputationHow many tokens a deployer wallet launched and how many scanned as high risk or rug-shaped (serial rugger check), from the GL1TCH Signal Graph.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    How many tokens a deployer wallet launched and how many scanned as high risk or rug-shaped (serial rugger check), from the GL1TCH Signal Graph.
  • scan_tokenPre-trade token safety check (Solana and EVM): rug-pull and honeypot verdict, 0-100 safety score, mint/freeze authority, LP lock, buy/sell tax, holder concentration, deployer histo…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Pre-trade token safety check (Solana and EVM): rug-pull and honeypot verdict, 0-100 safety score, mint/freeze authority, LP lock, buy/sell tax, holder concentration, deployer history and bot-volume flags.
Only reads 1Show 1 read-only tool
  • xray_yieldRead verified on-chain APY, TVL, withdrawable idle liquidity and explainable risk scores (0-100) for 30 DeFi pools across Solana, Ethereum, Base, Arbitrum, BSC, Tron and Robinhood …No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read verified on-chain APY, TVL, withdrawable idle liquidity and explainable risk scores (0-100) for 30 DeFi pools across Solana, Ethereum, Base, Arbitrum, BSC, Tron and Robinhood Chain.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Oct 28, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://gl1tchbased.xyz/api/mcp: tools/list returned 4 tools to an anonymous client, including scan_token (write), check_agent_wallet (write), deployer_reputation (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added.+1 addedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http gl1tch https://gl1tchbased.xyz/api/mcp
claude mcp add --transport http gl1tch https://gl1tchbased.xyz/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gl1tch__xray_yield"
    ],
    "ask": [
      "mcp__gl1tch__scan_token",
      "mcp__gl1tch__check_agent_wallet",
      "mcp__gl1tch__deployer_reputation"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gl1tch. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.gl1tchbased-pixel/gl1tch/verify?hash=f5510d718567bcdfbdfb45874f9ce366ea7ab78652a31dd4e6f2557b7635f31b" | jq -e '.changed == false'

Pinned hash f5510d718567, from Nov 10, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.gl1tchbased-pixel/gl1tch/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.gl1tchbased-pixel/gl1tch
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.gl1tchbased-pixel/gl1tch.svg)](https://radar.anlyon.com/servers/io.github.gl1tchbased-pixel/gl1tch)

Source: MCP Registry · repository. Synced Oct 28, 2026, 17:17 UTC.

GL1TCH Token Safety MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the GL1TCH Token Safety MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the GL1TCH Token Safety MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the GL1TCH Token Safety MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the GL1TCH Token Safety MCP server have?

4 tools: 3 write, 1 read. scan_token, check_agent_wallet, deployer_reputation and xray_yield.

Does the GL1TCH Token Safety MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the GL1TCH Token Safety MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the GL1TCH Token Safety MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.