Is the Keyvex MCP server down?

mcp-registry/com.keyvex/keyvex · v0.102.0

healthy
Last checked 2026-10-17 04:52 UTC · handshake 169ms

As of 2026-10-17 04:52 UTC, the Keyvex MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
1,654
outages (90d)
0
tools
64

US public financial disclosures for AI agents: Congress trades, SEC filings, FEC, lobbying, more

Install Keyvex MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http keyvex-mcp-server https://mcp.keyvex.com

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "keyvex-mcp-server": {
      "type": "http",
      "url": "https://mcp.keyvex.com"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 3 warning(s) across 64 tool(s); ~44,826 tokens of tool definitions.
Scores higher than 37% of 15,171 MCP servers Glimind has audited.
Its tool list costs an agent ~44,826 tokens per session — more than 100% of servers.
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints89
Token cost22
Client compatibility70
Protocol100
Reliability100
Stability68

What to fix (6)

4 tool definition(s) exceed ~1,200 tokens each (largest: get_insider_transactions, ~3,784).

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 ~6,075 tokens every session.

Tools: get_insider_transactions, get_fund_holdings, get_congressional_trades, get_fec_contributions · saves ~6,075 tokens/session

64 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.

Loading this server's tool list costs an agent ~44,826 tokens before any work — more than 100% 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.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.

1 of 64 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.

Tools: get_alerts

In the last 30 days: 0 tool(s) removed and 8 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.keyvex%2Fkeyvex/fixes

get_alerts 1 change
{
  "name": "get_alerts",
  "description": "Your watchlist alerts, newest first: events matched to the tickers, members of Congress and federal-contract\nrecipients (UEIs) on YOUR watchlist, for the API key making the call. Kinds:\n  congress_trade: a congressional trade disclosed this week in a ticker or by a member on your watchlist.\n  initial_13d: an initial Schedule 13D (a new 5%+ activist stake) filed this week in a ticker on your watchlist.\n  federal_contract: federal awards at or above your threshold that KeyVex first reported this w",
  "inputSchema": {
    "type": "object",
    "properties": {
      "kind": {
        "enum": [
          "congress_trade",
          "initial_13d",
          "federal_contract"
        ],
        "type": "string",
        "description": "Only this kind."
      },
      "limit": {
        "type": "integer",
        "maximum": 200,
        "minimum": 1,
        "description": "Page size (default 50)."
      },
      "since": {
        "type": "string",
        "description": "Only alerts detected at or after this ISO date or date-time."
      },
      "cursor": {
        "type": "string",
        "description": "next_cursor from the previous page."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/com.keyvex/keyvex"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.keyvex/keyvex"}) 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%2Fcom.keyvex%2Fkeyvex.svg)](https://glimind.com/server/mcp-registry%2Fcom.keyvex%2Fkeyvex?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.keyvex%2Fkeyvex?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.keyvex%2Fkeyvex.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.keyvex%2Fkeyvex.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.keyvex%2Fkeyvex?ref=badge
   :alt: MCP agent-readiness

Tools (64)

Compare: most reliable data servers · most reliable retrieval servers · most reliable finance servers · most reliable search 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 Keyvex MCP server down right now?

As of 2026-10-17 04:52 UTC, the Keyvex MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Keyvex MCP server provide?

Keyvex MCP server advertises 64 tools, including get_activist_stakes, get_aircraft_registry, get_alerts, get_annual_financial_disclosures, get_bank_financials.

How do I install Keyvex MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.keyvex.com

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

Glimind scanned all 64 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 Keyvex MCP server?

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.

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.