mcp-registry/com.xoomar/xoomar-mcp · v0.1.11
As of 2026-10-25 13:42 UTC, the Xoomar 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. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Free US market data as tools: SEC filings, insiders, short interest, 13F, COT, ETF flows, liquidity.
Claude Code
claude mcp add --transport http xoomar-mcp-server https://xoomar.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"xoomar-mcp-server": {
"type": "http",
"url": "https://xoomar.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
26 of 26 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. How to fix →
28 parameter(s) across 17 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) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
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. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 17 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.xoomar%2Fxoomar-mcp/fixes
{
"name": "insider_clusters",
"description": "Companies where several different insiders bought their own stock on the open market within a window (Form 4 transaction code P only): distinct buyers with titles, trades, combined value, first and latest trade dates. Default: three or more insiders in 30 days, sorted by number of insiders then value. Use ticker to check one company.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"days": {
"type": "integer",
"maximum": 365,
"minimum": 1,
"description": "Window in days (default 30)"
},
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1
},
"minUsd": {
"type": "number",
"minimum": 0,
"description": "Combined purchases at or above this, USD"
},
"ticker": {
"type": "string",
"maxLength": 12,
"minLength": 1,
"description": "US ticker symbol, e.g. GME. Class shares as on the SEC list, e.g. BRK-B."
},
"minInsiders": {
"type": "integer",
"maximum": 20,
"minimum": 2,
"description": "Distinct buyers required (default 3)"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Insider cluster buying"
}{
"name": "large_holders",
"description": "Holders above 5% from Schedule 13D (active) and 13G (passive) cover pages: holder, shares, percent of class, filing date. For a symbol or the latest filings.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"days": {
"type": "integer",
"maximum": 365,
"minimum": 1
},
"form": {
"enum": [
"13D",
"13G"
],
"type": "string"
},
"sort": {
"enum": [
"filed",
"percent"
],
"type": "string"
},
"symbol": {
"type": "string",
"maxLength": 12,
"minLength": 1,
"description": "US ticker symbol, e.g. GME. Class shares as on the SEC list, e.g. BRK-B."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Schedule 13D and 13G holders"
}{
"name": "threshold_list",
"description": "Reg SHO threshold lists from the Nasdaq and Cboe daily files since 2022: securities whose fails to deliver stayed above the threshold for five settlement days. One date (default the newest), one symbol's days on the list, or one listing market.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"date": {
"type": "string",
"maxLength": 10,
"description": "YYYY-MM-DD"
},
"limit": {
"type": "integer",
"maximum": 5000,
"minimum": 1
},
"market": {
"enum": [
"nasdaq",
"cboe"
],
"type": "string"
},
"symbol": {
"type": "string",
"maxLength": 12,
"minLength": 1,
"description": "US ticker symbol, e.g. GME. Class shares as on the SEC list, e.g. BRK-B."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Regulation SHO threshold securities"
}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.xoomar/xoomar-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.xoomar/xoomar-mcp"}) over MCP.
insider_trades ~292 tokensinsider_clusters ~272 tokensearnings_calendar ~246 tokenstreasury_auctions ~234 tokensshort_volume ~222 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%2Fcom.xoomar%2Fxoomar-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.xoomar%2Fxoomar-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.xoomar%2Fxoomar-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.xoomar%2Fxoomar-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.xoomar%2Fxoomar-mcp?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:de57c7fca9dd2253…, first seen 2026-10-17, included at leaf 12073 of 66,478. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable finance 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-25 13:42 UTC, the Xoomar 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. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Xoomar MCP server advertises 26 tools, including api_reference, bitcoin_treasuries, company_financials, corporate_events, cot_positioning.
Point your MCP client at this streamable-http endpoint: https://xoomar.com/mcp
Glimind scanned all 26 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.