mcp-registry/dev.rateapi/mcp · v2.1.0
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.
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
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 →
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 →
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 →
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 →
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
{
"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 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.
compare_personal_access_catalogs ~6,200 tokenscompare_reachable_offers ~6,154 tokensfind_reachable_offers ~4,004 tokenscheck_membership_eligibility ~3,795 tokensfind_eligible_credit_unions ~3,561 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fdev.rateapi%2Fmcp?ref=badge)
<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>
.. 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
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.
Compare: most reliable email servers · most reliable finance servers · most reliable data servers · most reliable security servers · most reliable communication servers
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.
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"
}
}
}
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.
Rateapi MCP server advertises 89 tools, including add_campaign_recipients, analyze_rent_vs_buy, assess_buy_timing, assess_rate_lock, batch_decisions.
Point your MCP client at this streamable-http endpoint: https://mcp.rateapi.dev/mcp
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.
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.