MCP.Market

Tickerr MCP server

online · 100% uptime
by imviky-ctrl·io.github.imviky-ctrl/tickerr·v1.0.1·1 stars
No reviews yet

Live status, API pricing and rate limits for ChatGPT, Claude, Gemini, Cursor and 42+ AI tools.

C60/100grade C
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
C60/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Tickerr yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Tickerr tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

1 high
  • Code scan3 source files scanned25/25
  • Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"challenge","message":"This request requires a challenge to be completed.","id":"cle1::1790548468-kcGtun2QkjKjoCLBbScZiZwP8XsWmKqr"}}0/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 138 days ago8/15
  • Maintainer identityregistry namespace matches repository owner6/10

Findings (1)

  • highRemote endpoint did not respondreliability.unreachable

    Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"challenge","message":"This request requires a challenge to be completed.","id":"cle1::1790548468-kcGtun2QkjKjoCLBbScZiZwP8XsWmKqr"}}

Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Tickerr compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
60/100
higher than 15% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
95 ms
faster than 85% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

Install Tickerr in Claude Code, Cursor or VS Code

claude mcp add --transport http tickerr https://tickerr.ai/mcp
Add to Cursor

What the publisher says

From the Tickerr repository's README, as published. We do not edit it. Read it on GitHub

Tickerr MCP

Outage radar for AI agents. LLM pricing, status, inference performance, and real-time agent-reported failure signals. 9 tools. No auth required.

Install

Claude Code

claude mcp add tickerr --transport http https://tickerr.ai/mcp

Cursor / Windsurf

{
  "mcpServers": {
    "tickerr": {
      "url": "https://tickerr.ai/mcp"
    }
  }
}

Claude Desktop (stdio wrapper)

npx -y tickerr-mcp

Tools (9)

Give and Take

Tickerr MCP uses a give-and-take model across gettoolstatus, getincidents, and reportincident.

gettoolstatus — Unlock per-model latency

Always include mystatus if your agent has made any call to this provider in the last 5 minutes — even successful calls. Pass isup: true, your response_ms, and the model name.

Basic response (no mystatus):**

  • Operational verdict (OPERATIONAL / DEGRADED / DOWN)
  • Response time, last check time, 30-day uptime

Full response (include mystatus):**

  • Everything above +
  • Per-model p50/p95 TTFT latency (last 24h)
  • 90-day uptime, user reports signal
{
  "slug": "claude",
  "my_status": {
    "is_up": true,
    "response_ms": 1400,
    "model": "claude-sonnet-4-6"
  }
}

On failure, add errorcode (e.g. "529"). isup is the only required field.

get_incidents — Contribute to live signal

Include my_status when fetching incident history to record your observation and see current agent-reported activity alongside historical data.

Without mystatus:** incident list + prompt to contribute.

With mystatus:** incident list + live agent reports count + confirmation your signal was recorded.

report_incident — Get routing intelligence

report_incident — Get routing intelligence

What you get: When your agent calls report_incident on a failure, you instantly receive:

  • How many other agents reported the same issue
  • Current signal state (detecting / confirmed / recovering)
  • Which model to fall back to

What you give: Anonymous failure signal — provider, model, error code, latency only. No request content. No personal data.

How to use it (Claude Code): report_incident fires automatically when your agent hits a 5xx error. No configuration needed — the tool description instructs Claude Code to call it.

How to use it (other agents): Add this to your system prompt:

On any 5xx error or timeout from an LLM API, call
report_incident from Tickerr MCP before retrying.
Use the returned recommendation to decide whether
to retry or switch models.

Reporting window: Active for 7 days from last Tickerr tool use. Renews automatically on any tool call.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Tickerr: common questions

Is Tickerr MCP server safe?
With care: it is graded C, so read the findings first (60/100). Read the Tickerr safety report
How do I install Tickerr?
It runs remotely at tickerr.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Tickerr need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Tickerr maintained?
The last commit was 176 days ago (2026-05-12). The latest release is v1.0.1.
Is Tickerr up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Tickerr compare with other MCP servers?
safety score 60/100 (higher than 15% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 95 ms (faster than 85% of 30,031 servers). Full comparison.