sml-ticker-research
https://sml-ticker-research.onrender.com
Registry code: 17dbee6f29717026
One cheap, loopable answer per call for a US ticker: market regime, trend + strength, key levels, ne
from a public catalogue that lists it, not from the operator
- endpoint
- https://sml-ticker-research.onrender.com/mcp
- door code
- 464cc730bd0bb2b1
- 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 sml-ticker-research live?
- Yes — it answered the hub's last check (checked 52m ago). It answered 100% of checks over the last 30 days.
- Is sml-ticker-research free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does sml-ticker-research have?
- 7 tools: brief, catalog, flow, regime, trend, levels, setup.
- Is sml-ticker-research 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.
90 days 100%· all time 100%
last good check
of 7 tools
- unknown → live
- unknown → live
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 10 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-03
concentrated, shared-payto
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
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.
trend 0.003139 USDC paid never probed
Trend and strength ($0.004 via x402 at GET https://sml-ticker-research.onrender.com/v1/trend). Direction (uptrend/sideways/downtrend), strength (ADX), RSI state, % vs 20/50/200-day averages, 5/21/63-day returns, ATR%.
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "pattern": "^[A-Za-z]{1,5}([.-][A-Za-z])?$", "description": "US equity or ETF ticker" } } }arguments 13 lineslevels 0.003139 USDC paid never probed
Key levels ($0.004 via x402 at GET https://sml-ticker-research.onrender.com/v1/levels). Nearest level above/below and full sorted list: 20-day and 52-week extremes, pivot/R1/S1, 50/200-day averages, distances in % and ATR.
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "pattern": "^[A-Za-z]{1,5}([.-][A-Za-z])?$", "description": "US equity or ETF ticker" } } }arguments 13 linessetup 0.00157 USDC paid never probed
Shortlist setup status ($0.002 via x402 at GET https://sml-ticker-research.onrender.com/v1/setup). Is this ticker on today's Shortlist paper-research board, which setup, reference/invalidation/objective levels, evidence status.
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "pattern": "^[A-Za-z]{1,5}([.-][A-Za-z])?$", "description": "US equity or ETF ticker" } } }arguments 13 linesbrief unknown 52m ago
All-in-one brief ($0.009 via x402 at GET https://sml-ticker-research.onrender.com/v1/brief). Regime + trend + levels + options activity + Shortlist status in one answer (cheaper than the five pieces).
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "pattern": "^[A-Za-z]{1,5}([.-][A-Za-z])?$", "description": "US equity or ETF ticker" } } }arguments 13 linescatalog unknown never probed
Machine-readable catalog with prices and 402 terms
{ "type": "object", "properties": {} }arguments 4 linesflow unknown 52m ago
Options activity summary ($0.004 via x402 at GET https://sml-ticker-research.onrender.com/v1/flow). Nearest-expiry options activity: upside/downside lean, volume and open-interest ratios, max pain, largest open-interest strikes, median implied vol. Summary stats only.
{ "type": "object", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "pattern": "^[A-Za-z]{1,5}([.-][A-Za-z])?$", "description": "US equity or ETF ticker" } } }arguments 13 linesregime unknown 52m ago
Market regime (+ optional ticker context) ($0.004 via x402 at GET https://sml-ticker-research.onrender.com/v1/regime). Risk-on / mixed / risk-off score from SPY/QQQ/IWM/TLT trend and SPY realized volatility; with ?symbol= adds that ticker's trend and 21-day relative performance.
{ "type": "object", "properties": { "symbol": { "type": "string" } } }arguments 8 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id17dbee6f29717026.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/17dbee6f29717026/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/17dbee6f29717026?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 0
- failed
- 1
- success rate
- 0%
- median latency
- 357ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
1 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.