_ registry / mcp streamable-http · checked 29m ago

OwlX

https://owlx.app

Registry code: 40df7f7935a01c69

api record

OwlX crypto structure reads, MemeSniper and token financials. Free tools: owlx_structure_read (BTC/ETH), owlx_token_profile, owlx_memestats. Pro tools need an OwlX key from owlx.app/account sent as Authorization: Bearer. All output is educational information, not financial advice.

endpoint
https://owlx.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is OwlX live?
Yes — it answered the hub's last check (checked 29m ago). It answered 100% of checks over the last 30 days.
Is OwlX free to use?
Yes — the hub reached it with no key and no payment.
What tools does OwlX have?
5 tools: owlx_memesniper, owlx_memestats, owlx_token_profile, owlx_structure_read, owlx_stock_profile.
Is OwlX safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.5%· all time 99.5%

latency
420ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 193 checks · signed record
_ what it is for
topic
crypto & onchain prices & market data
used for
  • get a structure score for a crypto symbol
  • filter meme coins for momentum
  • get token protocol financials
  • get a us stock snapshot
  • check hit rate of past signals
takes → gives
text → data
tools
5 reads
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • owlx_memesniper reads unknown never probed

    OwlX MemeSniper: 5-gate meme/altcoin pre-filter (volume/buy pressure/sustain/chase/BTC) + conviction grade A/B/C + play type + full Cat-Hunter read. Requires an OwlX Pro key. Real hit-rate of past signals is public via owlx_memestats. Educational info, not financial advice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Base symbol, e.g. WIF, PEPE, DOGE"
    }
  }
}
    arguments 12 lines
  • owlx_memestats reads unknown never probed

    Real recorded hit-rate of OwlX MemeSniper signals (free): every signal is logged at fire time and graded against actual prices 4h/24h later — wins AND losses. No cherry-picking.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • owlx_token_profile reads unknown never probed

    Token financial statement (free): DefiLlama protocol/chain TVL, fees & revenue (30d + annualized). Protocol assets get P/F-style income data; L1s get network gas; meme assets honestly report "no on-chain revenue".

    mcp-tool

    {
  "type": "object",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Token symbol, e.g. UNI, ETH, PEPE"
    }
  }
}
    arguments 12 lines
  • owlx_structure_read reads unknown 12h ago

    OwlX structure-score read of a crypto symbol: 0-10 score, LONG/SHORT/WAIT direction, trigger & defense levels, confirmation checks. Free for BTC/ETH; other symbols need an OwlX Pro key (Authorization: Bearer). Educational info, not financial advice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Base symbol, e.g. BTC, SOL, WIF"
    },
    "timeframe": {
      "enum": [
        "15m",
        "1h",
        "4h",
        "1d"
      ],
      "type": "string",
      "description": "Candle timeframe (default 4h)"
    }
  }
}
    arguments 22 lines
  • owlx_stock_profile reads unknown never probed

    US stock snapshot (free): live quote + financial metrics — P/E, P/S, EPS, margins, ROE, revenue growth, 52-week range, dividend yield, beta (Finnhub, TTM). Educational info, not financial advice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Ticker, e.g. AAPL, TSLA, NVDA"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 40df7f7935a01c69.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/40df7f7935a01c69/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/40df7f7935a01c69/badge.svg)](https://brick.blue/agent/40df7f7935a01c69?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.