_ registry / mcp + a2a http-sse · checked 4h ago

spectre-markets

https://spectre.markets

Registry code: 4117dbbe1a369a94

api record

Daily session levels and session scenarios from SPECTRE Markets (spectre.markets), each board a stored snapshot published once per session, not a live quote. Levels are options-gamma-derived where the instrument has an options source; GC carries no options source, so its board is structure levels only. Free tier only: the named free levels, the regime and a read excerpt where the board carries them, and today's ranked paths with their trade ideas. Research/education only, not financial advice. Levels, not calls.

endpoint
https://spectre.markets/mcp/
door code
f6d9a2f87c801208
protocol
http-sse ·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 spectre-markets live?
Yes — it answered the hub's last check (checked 4h ago). It answered 99% of checks over the last 30 days.
Is spectre-markets free to use?
Yes — the hub reached it with no key and no payment.
What tools does spectre-markets have?
3 tools: get_levels, get_paths, list_symbols.
Is spectre-markets 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
98.5%

90 days 96.4%· all time 96%

latency
376ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 334 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
finance & markets stock & market data
used for
  • get index options levels for a symbol
  • get ranked session paths and trade ideas
  • list covered instruments
takes → gives
text → data
tools
3 reads
_ 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 3 tools
1 open 2 never probed 1 of 3 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 reads open 4h ago

    List the instruments SPECTRE Markets publishes a levels board for, with the session each board is for and a link to the full board.

    mcp-tool

    {
  "type": "object",
  "title": "list_symbolsArguments",
  "properties": {}
}
    arguments 5 lines
  • get_levels reads unknown 4h ago

    The newest published free levels for one instrument (e.g. "NQ", "ES"); its session_date says which session, and it may be older than today. The named free levels with their prices, the market regime and a short excerpt of the desk read where the board carries them, and how many further levels the full board holds. Research/education only.

    mcp-tool

    {
  "type": "object",
  "title": "get_levelsArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol"
    }
  }
}
    arguments 13 lines
  • get_paths reads unknown 4h ago

    Today's ranked possible session paths for one instrument, each with its waypoints and a trade idea (entry zone, invalidation, target). Research/education only.

    mcp-tool

    {
  "type": "object",
  "title": "get_pathsArguments",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol"
    }
  }
}
    arguments 13 lines
_ try it over mcp 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 4117dbbe1a369a94.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4117dbbe1a369a94/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/4117dbbe1a369a94/badge.svg)](https://brick.blue/agent/4117dbbe1a369a94?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 knowoff the mcp door
card completeness
70%

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.