Skip to main content
Glama

token-oracle — Token Trust Oracle

Server Details

Flags fake/mismatched token contract addresses and hallucinated supply figures before you trade.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

Score is being calculated.

Available Tools

1 tool
verify_tokenVerify TokenInspect

Token Trust Oracle. Call this BEFORE trading against, writing code that references, or reporting figures about any token contract address you were not given directly by the user (one you generated, recalled, or inferred). This closes two separate failure modes: address-poisoning/impersonation (an address that doesn't actually match the token name everyone assumes it is), and tokenomics hallucination (LLMs are documented to get total supply, circulating supply, and other figures wrong more often than almost any other crypto data point). Checks the address has real contract bytecode, cross-references CoinGecko for an independent listing, and compares on-chain totalSupply() against CoinGecko's reported figures. Pass expectedSymbol when you believe you know what token this is — a mismatch is the strongest possible signal something is wrong. Returns a synthetic verdict: ALLOW (no issues found), WARN (proceed with caution — read the findings), or BLOCK (do not trust this address — likely not a contract at all, or doesn't match the token it claims to be). First 5 calls per caller are free; after that this tool requires x402 payment (USDC on Base) and will return a payment-required error with the amount and address to pay.

ParametersJSON Schema
NameRequiredDescriptionDefault
chainYesWhich chain the contract lives on.
addressYesThe token contract address to verify.
expectedSymbolNoOptional — the ticker symbol you believe this address corresponds to (e.g. "USDC"). A mismatch is the strongest fraud signal this tool can give.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedverify_token

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Token safety oracle for AI agents. Honeypot detection, 17 scam pattern checks, LP lock verification across 6 EVM chains. Score 0-100 with risk flags. ERC Token Safety Score standard.
    1
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Pre-trade token safety check for AI agents. Simulates a sell before you buy, then reports honeypot, tax, liquidity, pair age, same-ticker impersonation and owner powers as one low/medium/high/unknown verdict. Fail-closed: when a critical check cannot run it answers unknown rather than guessing low. Publishes its own measured error rate with the benchmark harness in the repo.
    3
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI assistants to check whether a crypto token, link, or forwarded "gem" message is a scam by running contract rules, live test trades, creator history, and market data across 64 networks, returning plain-English or Pidgin verdicts. Also supports scanning messages, reviewing a token's past checks, and explaining individual findings.
    5
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources