global.rootz.origin/filings
REMOTE · ORIGIN.ROOTZ.GLOBAL · SCANNED SEP 25
SEC-signed profiles for 8,000+ US public companies from EDGAR filings. Token-efficient.
Available components
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the global.rootz.origin/filings MCP server?
global.rootz.origin/filings is a hosted endpoint at https://origin.rootz.global/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 · origin.rootz.global
claude mcp add --transport http global-rootz-origin-filings 'https://origin.rootz.global/mcp'
{
"mcpServers": {
"global-rootz-origin-filings": {
"url": "https://origin.rootz.global/mcp"
}
}
} {
"servers": {
"global-rootz-origin-filings": {
"type": "http",
"url": "https://origin.rootz.global/mcp"
}
}
} [mcp_servers.global-rootz-origin-filings] url = "https://origin.rootz.global/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"global-rootz-origin-filings": {
"type": "remote",
"url": "https://origin.rootz.global/mcp",
"enabled": true
}
}
} openclaw mcp add global-rootz-origin-filings --url 'https://origin.rootz.global/mcp' --transport streamable-http
mcp_servers:
global-rootz-origin-filings:
url: "https://origin.rootz.global/mcp" {
"McpServers": {
"global-rootz-origin-filings": {
"Transport": "http",
"Url": "https://origin.rootz.global/mcp"
}
}
} assistant mcp add global-rootz-origin-filings -t streamable-http -u 'https://origin.rootz.global/mcp'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 23 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 22 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 20 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 19 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Sept 26 +10
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 3 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
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 25 Sept 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=YE2,O=Let's Encrypt,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6e05b98c007f2d2a3f50fd4ae724a173f91 |
| SANs: origin.rootz.global | ||||||
| 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 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=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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 →
origin_company ~59
Look up a US public company by ticker. SEC-verified, ~200 tokens. Use this FIRST for any company query.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Stock 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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | User 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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | User email address | |
| frequency | string | – | How often to send briefings (default: weekly) |
| tickers | array | yes | Array of stock tickers to watch (max 20) |
No output schema declared.
No examples provided.
origin_filings ~44
SEC filing index with EDGAR links.
| Name | Type | Req | Description |
|---|---|---|---|
| form | string | – | Optional: 10-K, 10-Q, 8-K |
| ticker | string | yes | – |
No output schema declared.
No examples provided.
origin_person ~24
Career path across US public companies.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Person name |
No output schema declared.
No examples provided.
origin_profile ~29
Full company profile: people, products, partnerships. ~800 tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
No output schema declared.
No examples provided.
origin_search ~26
Cross-company search by keyword, technology, or person.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
origin_timeline ~29
Quarter-by-quarter history from SEC filings. ~2000 tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| first | boolean | – | Optional: if true, returns first-mention date per company for the topic |
| q | string | – | Optional: free text search across facts |
| ticker | string | – | Optional: filter by company ticker |
| topic | string | – | Optional: topic tag (ai, trusted_computing, blockchain, data_center, quantum, cybersecurity, robotics, autonomous, gaming, etc.) |
No output schema declared.
No examples provided.
What is the global.rootz.origin/filings MCP server?
global.rootz.origin/filings is an MCP server listed in the public MCP registry as global.rootz.origin/filings. SEC-signed profiles for 8,000+ US public companies from EDGAR filings. Token-efficient. This page covers its hosted endpoint (https://origin.rootz.global/mcp).
Is the global.rootz.origin/filings MCP server safe to use?
global.rootz.origin/filings scores 76 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 global.rootz.origin/filings MCP server expose?
global.rootz.origin/filings exposes 9 tools: origin_company, origin_profile, origin_timeline, origin_person, origin_search, and 4 more. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.
Does the global.rootz.origin/filings MCP server require authentication?
No. We connected to global.rootz.origin/filings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the global.rootz.origin/filings MCP server still maintained?
global.rootz.origin/filings is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.