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

isitdeprecated

https://isitdeprecated.com

Registry code: 65ece8d7cc6876cd

api record

Ask before writing a model identifier into code. check_model accepts any provider spelling.

endpoint
https://isitdeprecated.com/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 isitdeprecated live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is isitdeprecated free to use?
Yes — the hub reached it with no key and no payment.
What tools does isitdeprecated have?
4 tools: upcoming_retirements, recent_changes, check_model, check_models.
Is isitdeprecated 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.7%

90 days 99.1%· all time 99.1%

latency
161ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 437 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
ai & agents llm access & routing
used for
  • check if an ai model id is deprecated
  • audit model ids in a codebase
  • list recent ai model api changes
  • list upcoming model retirements
takes → gives
text → data
tools
4 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 4 tools
2 open 2 never probed 2 of 4 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.

  • check_model reads open 11h ago

    Check whether an AI model identifier is deprecated, retiring, or has silently changed (price, context window, capabilities). Accepts any spelling a provider or SDK uses, e.g. 'gpt-4-turbo', 'azure/gpt-4.1-mini', 'claude-opus-4-1-20250805'. Call this before writing a model identifier into code.

    mcp-tool

    {
  "type": "object",
  "required": [
    "model"
  ],
  "properties": {
    "model": {
      "type": "string",
      "description": "Model identifier to check"
    }
  }
}
    arguments 12 lines
  • check_models reads open 11h ago

    Check many model identifiers at once and report which are retired or scheduled for retirement. Use when auditing a codebase or config.

    mcp-tool

    {
  "type": "object",
  "required": [
    "models"
  ],
  "properties": {
    "models": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Up to 100 identifiers"
    }
  }
}
    arguments 15 lines
  • upcoming_retirements reads unknown never probed

    List models with an announced retirement date inside a horizon, soonest first.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "within_days": {
      "type": "integer",
      "default": 90
    }
  }
}
    arguments 9 lines
  • recent_changes reads unknown never probed

    Recent breaking changes across AI model APIs: price moves, context-window cuts, removed capabilities, removals. One entry per real upstream change.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 30
    },
    "min_severity": {
      "enum": [
        "critical",
        "high",
        "medium",
        "low",
        "info"
      ],
      "type": "string",
      "default": "medium"
    }
  }
}
    arguments 20 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 65ece8d7cc6876cd.

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

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.