Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EquiReason

REMOTE · API.EQUIREASON.COM

US stock research: filed records, filing events, insider trades, 13F; plan research when signed in.

73 Trust /100

Last scanned (10 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 703 tokens (~87/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Tool coverage: 67% → 75% ▲ functional
    • “list_filing_events” added an optional parameter “limit” cosmetic
    • “list_filing_events” added an optional parameter “offset” cosmetic
    • “list_filing_events” added an optional parameter “snapshot” cosmetic
  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Nov 26 72

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://api.equireason.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=equireason.com CN=YE2,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA384 6a8aeed54d8d522700c16c76efc143a9ef0
SANs: *.equireason.com, equireason.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.equireason.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
equireason.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.equireason.com/mcp Verified 200
http (plaintext) http://api.equireason.com/mcp HTTPS enforced 302 https://api.equireason.com/mcp
MCP tools · 8 exposed · ~544 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_company ~116

A company's filed record: annual income, balance-sheet and cash-flow lines from SEC XBRL, revenue mix by reported segment, the latest filings with plain-language summaries and links, Form 4 insider trades (planned vs unplanned), 13F holder counts by quarter, risk-factor changes and earnings-call dates. Signed in, it adds the research the user's plan includes: the verdict and its reasons, what would change it, valuation, prices and analyst estimates.

NameTypeReqDescription
tickerstringyesUS ticker, e.g. AAPL

No output schema declared.

No examples provided.

get_fund_holdings ~56

A tracked fund's latest 13F: positions with shares and reported value, what changed against the prior quarter, and positions it exited.

NameTypeReqDescription
fundstringyesFund name or slug, e.g. Berkshire Hathaway

No output schema declared.

No examples provided.

get_opportunities ~66

Companies ranked by EquiReason's verdict, with band, score, the matched trend and the evidence count — optionally for one trend. Requires signing in; depth follows the plan.

NameTypeReqDescription
limitinteger––
trendstring–Optional trend_id from list_trends

No output schema declared.

No examples provided.

get_trend ~55

One trend: the industries it supports, its knock-on effects with their expected lag, the evidence count by source type, and the conditions that would end it.

NameTypeReqDescription
trend_idstringyestrend_id from list_trends

No output schema declared.

No examples provided.

list_filing_events ~138

Companies with a given event in the last 7 days (or an earlier ISO week): guidance raised or cut, unplanned insider buying, executive changes, acquisitions, buybacks, layoffs. Each row quotes the filing or call.

NameTypeReqDescription
kindstringyes–
limitinteger–Rows per page (default 50)
offsetinteger–Zero-based row offset; use `next` from the previous page
snapshotstring–Snapshot from the first page; detects changed lists
weekstring–Optional ISO week such as 2026-w44; omit for the last 7 days

No output schema declared.

No examples provided.

list_funds ~31

The institutional investors EquiReason tracks, with their latest 13F period, position count and reported value.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_trends ~27

The market trends EquiReason is following, with how many companies' filings describe each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_companies ~55

Find US-listed companies covered by EquiReason by ticker or name. Returns ticker, name, sector and the company page.

NameTypeReqDescription
limitinteger––
querystringyesTicker or part of the name

No output schema declared.

No examples provided.

Install

How do I install the EquiReason MCP server?

EquiReason is a hosted endpoint at https://api.equireason.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.equireason.com

# add to Claude Code
claude mcp add --transport http com-equireason-equireason 'https://api.equireason.com/mcp'
Common questions

What is the EquiReason MCP server?

EquiReason is an MCP server listed in the public MCP registry as com.equireason/equireason. US stock research: filed records, filing events, insider trades, 13F; plan research when signed in. This page covers its hosted endpoint (https://api.equireason.com/mcp).

Is the EquiReason MCP server safe to use?

EquiReason scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the EquiReason MCP server expose?

EquiReason exposes 8 tools: search_companies, get_company, list_filing_events, list_funds, get_fund_holdings, and 3 more. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.

Does the EquiReason MCP server require authentication?

No. We connected to EquiReason without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the EquiReason MCP server still maintained?

EquiReason is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.