_ registry / mcp streamable-http · checked 1h ago

tickfeed

https://tickfeed.pro

Registry code: b1567f23eaa7a9ae

api record

Read-only market data from TickFeed for 60 forex pairs (majors, crosses, exotics such as EURUSD,

USDJPY, GBPJPY, USDMXN) and 11 metals (XAUUSD gold, XAGUSD silver, XPTUSD, XPDUSD, gold in EUR/GBP/AUD/CHF/JPY).

endpoint
https://tickfeed.pro/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 tickfeed live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is tickfeed free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does tickfeed have?
6 tools: list_symbols, get_feed_health, find_gaps, get_price, get_prices, get_candles.
Is tickfeed 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
100%

90 days 100%· all time 100%

latency
274ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 auth-required 6 of 6 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.

  • list_symbols auth-required 1h ago

    List supported symbols (public names such as XAUUSD), their trading session schedule, price precision (digits, point size) and the available candle timeframes.

    mcp-tool

    {
      "type": "object",
      "title": "list_symbolsArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_feed_health auth-required 1h ago

    Feed health: overall status (ok / degraded / down) and, per symbol, freshness and whether its market is open. Use it to judge whether data is current.

    mcp-tool

    {
      "type": "object",
      "title": "get_feed_healthArguments",
      "properties": {}
    }
    arguments 5 lines
  • find_gaps auth-required 1h ago

    Missing intervals in the stored candle history. `expected: true` gaps are scheduled market closures; others are holidays, minutes without ticks, or missing data.

    mcp-tool

    {
      "type": "object",
      "title": "find_gapsArguments",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "title": "Symbol",
          "description": "Public symbol, e.g. XAUUSD, EURUSD or USDJPY (see list_symbols)"
        },
        "end_time": {
          "anyOf": [
            {
              "type": "string",
              "format": "date-time"
            },
            {
              "type": "null"
            }
          ],
          "title": "End Time",
          "default": null,
          "description": "Optional ISO 8601 UTC end"
        },
        "timeframe": {
          "enum": [
            "M1",
            "M5",
            "M15",
            "M30",
            "H1",
            "H4",
            "D1"
          ],
          "type": "string",
          "title": "Timeframe",
          "default": "M5",
          "description": "Bar size"
        },
        "start_time": {
          "anyOf": [
            {
              "type": "string",
              "format": "date-time"
            },
            {
              "type": "null"
            }
          ],
          "title": "Start Time",
          "default": null,
          "description": "Optional ISO 8601 UTC start"
        }
      }
    }
    arguments 57 lines
  • get_price auth-required never probed

    Latest bid/ask for a symbol, with spread (price units and points), tick time (UTC), tick age and a freshness label (fresh / market_closed / stale). Always check `freshness`.

    mcp-tool

    {
      "type": "object",
      "title": "get_priceArguments",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "title": "Symbol",
          "description": "Public symbol, e.g. XAUUSD, EURUSD or USDJPY (see list_symbols)"
        }
      }
    }
    arguments 14 lines
  • get_prices auth-required never probed

    Latest bid/ask for several symbols at once (up to 30), each with its own freshness label. Prefer this over calling get_price repeatedly. Costs one unit per symbol.

    mcp-tool

    {
      "type": "object",
      "title": "get_pricesArguments",
      "required": [
        "symbols"
      ],
      "properties": {
        "symbols": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "title": "Symbols",
          "maxItems": 30,
          "minItems": 1,
          "description": "Symbols, e.g. [\"EURUSD\", \"GBPUSD\"]"
        }
      }
    }
    arguments 19 lines
  • get_candles auth-required never probed

    Historical OHLC candles in chronological order (oldest first). Each bar has open-time (UTC), open/high/low/close, tick volume, spread in points and `complete` (false = still forming). If `truncated` is true, request the next page with start_time = `next_start_time`.

    mcp-tool

    {
      "type": "object",
      "title": "get_candlesArguments",
      "required": [
        "symbol"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 100,
          "maximum": 1000,
          "minimum": 1,
          "description": "Number of bars (max 1000 via MCP)"
        },
        "symbol": {
          "type": "string",
          "title": "Symbol",
          "description": "Public symbol, e.g. XAUUSD, EURUSD or USDJPY (see list_symbols)"
        },
        "end_time": {
          "anyOf": [
            {
              "type": "string",
              "format": "date-time"
            },
            {
              "type": "null"
            }
          ],
          "title": "End Time",
          "default": null,
          "description": "Optional ISO 8601 UTC end; without start_time returns the latest `limit` bars up to here"
        },
        "timeframe": {
          "enum": [
            "M1",
            "M5",
            "M15",
            "M30",
            "H1",
            "H4",
            "D1"
          ],
          "type": "string",
          "title": "Timeframe",
          "default": "M5",
          "description": "Bar size"
        },
        "start_time": {
          "anyOf": [
            {
              "type": "string",
              "format": "date-time"
            },
            {
              "type": "null"
            }
          ],
          "title": "Start Time",
          "default": null,
          "description": "Optional ISO 8601 UTC start; returns the first `limit` bars from here"
        }
      }
    }
    arguments 65 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 b1567f23eaa7a9ae.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b1567f23eaa7a9ae/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/b1567f23eaa7a9ae/badge.svg)](https://brick.blue/agent/b1567f23eaa7a9ae?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
100%

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.