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

global.rootz.origin/filings

REMOTE · ORIGIN.ROOTZ.GLOBAL · SCANNED AUG 3

SEC-signed profiles for 8,000+ US public companies from EDGAR filings. Token-efficient.

61 Trust /100
Trust breakdown (6 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 →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 515 tokens (~57/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · origin.rootz.global

# add to Claude Code
claude mcp add --transport http global-rootz-origin-filings https://origin.rootz.global/mcp
# ~/.codex/config.toml
[mcp_servers.global-rootz-origin-filings]
url = "https://origin.rootz.global/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "global-rootz-origin-filings": {
      "type": "remote",
      "url": "https://origin.rootz.global/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add global-rootz-origin-filings --url https://origin.rootz.global/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  global-rootz-origin-filings:
    url: "https://origin.rootz.global/mcp"
// mcp.json
{
  "mcpServers": {
    "global-rootz-origin-filings": {
      "type": "http",
      "url": "https://origin.rootz.global/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 2 Aug 26 +1

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

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 59

    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 3 Aug 2026 · Probed https://origin.rootz.global/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=origin.rootz.global CN=YE1,O=Let's Encrypt,C=US 6 Jun 2026 4 Sept 2026 ECDSA 256 ECDSA-SHA384 692a4cd311f8155b712838ca3e7dcf76cc0
SANs: origin.rootz.global
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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
DNSSEC secure

Validation of origin.rootz.global. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
global. present 13060 8 Verified
rootz.global. present 40948, 52524 13, 13 Verified
origin.rootz.global. Verified address RRset verified with the apex keys
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
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://origin.rootz.global/mcp Verified 200
http (plaintext) http://origin.rootz.global/mcp HTTPS enforced 301 https://origin.rootz.global/mcp
MCP tools — 9 exposed · ~515 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.

Tool Tokens
origin_company ~59

Look up a US public company by ticker. SEC-verified, ~200 tokens. Use this FIRST for any company query.

NameTypeReqDescription
tickerstringyesStock ticker (e.g. AAPL, MSFT, WAVX) or CIK number

No output schema declared.

No examples provided.

origin_digest ~58

Get the latest research digest for an enrolled user. Returns filing signals, recent facts, stock quotes, and AI agent interest levels for their watched companies. Use this to brief a user on their portfolio.

NameTypeReqDescription
emailstringyesUser email address

No output schema declared.

No examples provided.

origin_engage ~111

Enroll a user for company research briefings. The user provides their email and tickers to watch. They get weekly or daily digests with filing signals, earnings facts, and AI interest data. Use this when a user says they want to track companies or get regular updates.

NameTypeReqDescription
emailstringyesUser email address
frequencystringHow often to send briefings (default: weekly)
tickersarrayyesArray of stock tickers to watch (max 20)

No output schema declared.

No examples provided.

origin_filings ~44

SEC filing index with EDGAR links.

NameTypeReqDescription
formstringOptional: 10-K, 10-Q, 8-K
tickerstringyes

No output schema declared.

No examples provided.

origin_person ~24

Career path across US public companies.

NameTypeReqDescription
namestringyesPerson name

No output schema declared.

No examples provided.

origin_profile ~29

Full company profile: people, products, partnerships. ~800 tokens.

NameTypeReqDescription
tickerstringyes

No output schema declared.

No examples provided.

origin_search ~26

Cross-company search by keyword, technology, or person.

NameTypeReqDescription
querystringyes

No output schema declared.

No examples provided.

origin_timeline ~29

Quarter-by-quarter history from SEC filings. ~2000 tokens.

NameTypeReqDescription
tickerstringyes

No output schema declared.

No examples provided.

origin_transcripts ~135

Search earnings call transcripts. Query by topic (ai, trusted_computing, blockchain, data_center, etc.), company ticker, or free text. Returns extracted facts, speakers, and metrics from earnings calls.

NameTypeReqDescription
firstbooleanOptional: if true, returns first-mention date per company for the topic
qstringOptional: free text search across facts
tickerstringOptional: filter by company ticker
topicstringOptional: topic tag (ai, trusted_computing, blockchain, data_center, quantum, cybersecurity, robotics, autonomous, gaming, etc.)

No output schema declared.

No examples provided.