Skip to content

filings MCP server

global.rootz.origin/filingsorigin.rootz.globalstreamable-httpv0.1.0Scanned

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

9 tools: 6 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 6 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the filings MCP server can do

The filings MCP server is published by origin.rootz.global, a domain the MCP Registry verified. It has 9 tools. It can create or change data (6 tools: origin_company, origin_profile, origin_timeline, origin_person and 2 more), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 6Claude Code: ask
  • origin_companyLook up a US public company by ticker.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Look up a US public company by ticker. SEC-verified, ~200 tokens. Use this FIRST for any company query.
  • origin_engageEnroll a user for company research briefings.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • origin_filingsSEC filing index with EDGAR links.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    SEC filing index with EDGAR links.
  • origin_personCareer path across US public companies.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Career path across US public companies.
  • origin_profileFull company profile: people, products, partnerships.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full company profile: people, products, partnerships. ~800 tokens.
  • origin_timelineQuarter-by-quarter history from SEC filings.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Quarter-by-quarter history from SEC filings. ~2000 tokens.
Only reads 3Show 3 read-only tools
  • origin_digestGet the latest research digest for an enrolled user.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    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.
  • origin_transcriptsSearch earnings call transcripts.No findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://origin.rootz.global/mcp: tools/list returned 9 tools to an anonymous client, including origin_company (write), origin_profile (write), origin_timeline (write), origin_person (write), origin_filings (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-03-26
  2. Nov 13, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-03-26 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 2 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-03-26
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-03-26 to none

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http filings https://origin.rootz.global/mcp
claude mcp add --transport http filings https://origin.rootz.global/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__filings__origin_search",
      "mcp__filings__origin_transcripts",
      "mcp__filings__origin_digest"
    ],
    "ask": [
      "mcp__filings__origin_company",
      "mcp__filings__origin_profile",
      "mcp__filings__origin_timeline",
      "mcp__filings__origin_person",
      "mcp__filings__origin_filings",
      "mcp__filings__origin_engage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as filings. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/global.rootz.origin/filings/verify?hash=0d4b4647018b291f04508c60c36d2a95c1683779ee7783e90c44b591e449195c" | jq -e '.changed == false'

Pinned hash 0d4b4647018b, from Nov 11, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/global.rootz.origin/filings/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for global.rootz.origin/filings
[![Anlyon Radar](https://radar.anlyon.com/badge/global.rootz.origin/filings.svg)](https://radar.anlyon.com/servers/global.rootz.origin/filings)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:13 UTC.

filings MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the filings MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the filings MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the filings MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the filings MCP server have?

9 tools: 6 write, 3 read. origin_company, origin_profile, origin_timeline, origin_person, origin_filings, origin_engage, origin_search, origin_transcripts and 1 more.

Does the filings MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the filings MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the filings MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.