Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.imviky-ctrl/tickerr

NPM · TICKERR-MCP · 2 COMPONENTS · SCANNED SEP 20

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

0 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 524 tokens (~74/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.imviky-ctrl/tickerr MCP server?

io.github.imviky-ctrl/tickerr runs locally as an npm package, launched with npx -y tickerr-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · tickerr-mcp

# add to Claude Code
claude mcp add imviky-ctrl-tickerr -- npx -y tickerr-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "imviky-ctrl-tickerr": {
      "command": "npx",
      "args": [
        "-y",
        "tickerr-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "imviky-ctrl-tickerr": {
      "command": "npx",
      "args": [
        "-y",
        "tickerr-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add imviky-ctrl-tickerr -- npx -y tickerr-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "imviky-ctrl-tickerr": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tickerr-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add imviky-ctrl-tickerr --command npx --arg -y --arg tickerr-mcp
# ~/.hermes/config.yaml
mcp_servers:
  imviky-ctrl-tickerr:
    command: "npx"
    args: ["-y", "tickerr-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "imviky-ctrl-tickerr": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tickerr-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add imviky-ctrl-tickerr -t stdio -c npx -a -y tickerr-mcp
// mcp.json
{
  "mcpServers": {
    "imviky-ctrl-tickerr": {
      "command": "npx",
      "args": [
        "-y",
        "tickerr-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 8 Sept 26 0
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/tickerr-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~524 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_pricing ~106

Rank AI models by total cost for a given token workload. Useful for finding the cheapest model for your use case.

NameTypeReqDescription
filterstringNarrow to a provider or model family — e.g. "claude", "gpt", "gemini"
input_tokensintegeryesNumber of input tokens per request
output_tokensintegerNumber of output tokens per request
topintegerShow only the N cheapest models (default 10)

No output schema declared.

No examples provided.

get_api_pricing ~86

Get current API pricing (input/output cost per 1M tokens) for AI models tracked by tickerr.ai. Filter by model or provider name.

NameTypeReqDescription
filterstringFilter by model or tool name — e.g. "claude", "gpt-4o", "gemini"
limitintegerMax models to return (default 50)

No output schema declared.

No examples provided.

get_free_tier ~62

Find the best free plans across AI tools, grouped by category (LLM APIs, coding assistants, image generation, etc.).

NameTypeReqDescription
categorystringFilter by category slug — e.g. "llm", "coding", "image", "video"

No output schema declared.

No examples provided.

get_incidents ~83

Get historical incidents (outages, degradations) for any AI tool from the last 90 days. Sourced from 26 official provider status pages.

NameTypeReqDescription
limitintegerNumber of incidents (default 10, max 50)
slugstringyesTool slug — e.g. "chatgpt", "claude", "gemini"

No output schema declared.

No examples provided.

get_rate_limits ~67

Get rate limits and plan details for any AI tool — requests per minute, tokens per day, context window, and more by plan tier.

NameTypeReqDescription
slugstringyesTool slug — e.g. "cursor", "github-copilot", "chatgpt", "claude"

No output schema declared.

No examples provided.

get_tool_status ~68

Get live operational status, uptime percentage, and response time for any AI tool. Checks every 5 minutes from independent infrastructure.

NameTypeReqDescription
slugstringyesTool slug — e.g. "chatgpt", "claude", "cursor", "github-copilot", "gemini"

No output schema declared.

No examples provided.

list_tools ~52

List all 42+ AI tools monitored by tickerr.ai — ChatGPT, Claude, Gemini, Cursor, GitHub Copilot, Perplexity, DeepSeek, Groq, Fireworks AI, and more.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.imviky-ctrl/tickerr MCP server?

io.github.imviky-ctrl/tickerr is an MCP server listed in the public MCP registry as io.github.imviky-ctrl/tickerr. Live status, API pricing and rate limits for ChatGPT, Claude, Gemini, Cursor and 42+ AI tools. This page covers its npm package (tickerr-mcp).

Is the io.github.imviky-ctrl/tickerr MCP server safe to use?

io.github.imviky-ctrl/tickerr scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.imviky-ctrl/tickerr MCP server expose?

io.github.imviky-ctrl/tickerr exposes 7 tools: list_tools, get_tool_status, get_incidents, get_api_pricing, get_rate_limits, and 2 more. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.

Is the io.github.imviky-ctrl/tickerr MCP server still maintained?

io.github.imviky-ctrl/tickerr is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.imviky-ctrl/tickerr MCP server under?

io.github.imviky-ctrl/tickerr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.