Is the Rateapi MCP server down?

mcp-registry/dev.rateapi/mcp · v2.1.0

healthy
Last checked 2026-10-26 17:10 UTC · handshake 1s

As of 2026-10-26 17:10 UTC, the Rateapi MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
100%
checks observed
4,957
outages (90d)
1
tools
89

Live US mortgage, auto, HELOC, personal & deposit rates with evidence, plus who can join each lender

Point your MCP client at this streamable-http endpoint: https://mcp.rateapi.dev/mcp

Agent-readiness: C (77/100)

C (77/100): 1 error(s), 5 warning(s) across 89 tool(s); ~54,605 tokens of tool definitions.
Scores higher than 13% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~54,605 tokens per session — more than 99% of servers.
77 → 77 since 2026-10-17
no tool-poisoning patterns
Schemas89
Descriptions84
Safety hints100
Token cost0
Client compatibility100
Protocol40
Reliability100
Stability100

What to fix (6)

Loading this server's tool list costs an agent ~54,605 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

8 tool definition(s) exceed ~1,200 tokens each (largest: compare_personal_access_catalogs, ~6,200).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~27,644 tokens every session. How to fix →

Tools: compare_personal_access_catalogs, compare_reachable_offers, find_reachable_offers, check_membership_eligibility, find_eligible_credit_unions and 3 more · saves ~27,644 tokens/session

89 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

24 parameter(s) across 7 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: assess_rate_lock, compare_personal_access_catalogs, compare_total_cost, get_deposit_beta, list_rates and 2 more

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: save_scenario

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.rateapi%2Fmcp/fixes

save_scenario 1 change
{
  "name": "save_scenario",
  "description": "Save a rate comparison for a named client so it can be recalled later (a lightweight CRM for loan officers). Pass the client label and the inputs/results you want to keep.",
  "inputSchema": {
    "type": "object",
    "required": [
      "client_name",
      "input",
      "result_snapshot"
    ],
    "properties": {
      "input": {
        "type": "object",
        "description": "The scenario inputs (product, amount, state, term, etc.)"
      },
      "client_name": {
        "type": "string",
        "description": "Client/scenario label, e.g. \"Smith — $400k purchase, CA\""
      },
      "result_snapshot": {
        "description": "The comparison result to store (object from get_financing_decision/compare_products)",
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.rateapi/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.rateapi/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.rateapi%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fdev.rateapi%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.rateapi%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.rateapi%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.rateapi%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.rateapi%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:31af88b09acd868e…, first seen 2026-10-17, included at leaf 5926 of 74,305. Version history · verify what your client received.

Tools (89)

Compare: most reliable email servers · most reliable finance servers · most reliable data servers · most reliable security servers · most reliable communication servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Rateapi MCP server down right now?

As of 2026-10-26 17:10 UTC, the Rateapi MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.

How many tools does Rateapi MCP server provide?

Rateapi MCP server advertises 89 tools, including add_campaign_recipients, analyze_rent_vs_buy, assess_buy_timing, assess_rate_lock, batch_decisions.

How do I install Rateapi MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.rateapi.dev/mcp

Is the Rateapi MCP server safe to connect to an AI agent?

Glimind scanned all 89 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Rateapi MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve