Is com.holdingsintel/mcp up? Live MCP status
Yes, it is up. It answered an MCP server/discover with no credential and negotiated protocol 2026-07-28.
A stock client connected with no credential and negotiated 2026-07-28. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2026-07-28 |
| Server says it is | holdingsintel 2.0.0 |
| Answered in | 193 ms |
| Endpoint checked | https://mcp.holdingsintel.com/sse |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Could not tell (HTTP 429)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Could not tell (HTTP 429).https://mcp.holdingsintel.com/sse/server-card |
| MCP server card (SEP-1649 location) | Could not tell (HTTP 429)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Could not tell (HTTP 429)./.well-known/http-message-signatures-directory |
Read at https://mcp.holdingsintel.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 24 tools: add_saved_list_item, analyze_fund, analyze_politician, analyze_stock, clone_fund, compare_funds, create_saved_list, delete_saved_list, find_signals, get_13f_activity, get_activist_stakes, get_congress_trades, get_fund_holdings, get_insider_trades, get_my_mcp_status, get_saved_list, get_stock_holders, list_quarters, list_saved_lists, remove_saved_list_item, rename_saved_list, search_filers, search_securities, update_saved_list_item_notes.
Its tools changed between 2026-09 and 2026-10:
create_saved_list: output schema changedget_13f_activity: description, input schema, output schema changedget_fund_holdings: output schema changedget_insider_trades: description, output schema changedget_saved_list: description, output schema changedget_stock_holders: output schema changedlist_saved_lists: output schema changedrename_saved_list: output schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.holdingsintel/mcp |
|---|---|
| Title | HoldingsIntel |
| Description | Smart Money Verdict per stock & fund from SEC 13F, insider, activist & congressional filings. |
| Endpoint | https://mcp.holdingsintel.com/sse |
| Publisher repository | none listed |
| Version | 1.1.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt