_ registry / mcp streamable-http · checked 1h ago

origin-sec-registry

https://origin.rootz.global

Registry code: 668272dc37714e7b

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://origin.rootz.global/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is origin-sec-registry live?
Yes — it answered the hub's last check (checked 1h ago). It answered 91% of checks over the last 30 days.
Is origin-sec-registry free to use?
Yes — the hub reached it with no key and no payment.
What tools does origin-sec-registry have?
9 tools: origin_timeline, origin_digest, origin_profile, origin_person, origin_filings, origin_transcripts, origin_engage, origin_company, ….
Is origin-sec-registry safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
91.4%

90 days 91%· all time 91%

latency
319ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 456 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
finance & markets company & filings
used for
  • look up a us public company by ticker
  • list sec filings for a company
  • search earnings call transcripts
  • trace an executive's career
takes → gives
text → data
tools
8 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
1 open 8 never probed 1 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • origin_search reads open 17h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • origin_timeline reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • origin_digest reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "User email address"
    }
  }
}
    arguments 12 lines
  • origin_profile reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • origin_person reads unknown never probed

    Career path across US public companies.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Person name"
    }
  }
}
    arguments 12 lines
  • origin_filings reads unknown never probed

    SEC filing index with EDGAR links.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "form": {
      "type": "string",
      "description": "Optional: 10-K, 10-Q, 8-K"
    },
    "ticker": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • origin_transcripts reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "q": {
      "type": "string",
      "description": "Optional: free text search across facts"
    },
    "first": {
      "type": "boolean",
      "description": "Optional: if true, returns first-mention date per company for the topic"
    },
    "topic": {
      "type": "string",
      "description": "Optional: topic tag (ai, trusted_computing, blockchain, data_center, quantum, cybersecurity, robotics, autonomous, gaming, etc.)"
    },
    "ticker": {
      "type": "string",
      "description": "Optional: filter by company ticker"
    }
  }
}
    arguments 22 lines
  • origin_engage changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email",
    "tickers"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "User email address"
    },
    "tickers": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Array of stock tickers to watch (max 20)"
    },
    "frequency": {
      "enum": [
        "daily",
        "weekly",
        "monthly"
      ],
      "type": "string",
      "description": "How often to send briefings (default: weekly)"
    }
  }
}
    arguments 29 lines
  • origin_company reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string",
      "description": "Stock ticker (e.g. AAPL, MSFT, WAVX) or CIK number"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 668272dc37714e7b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/668272dc37714e7b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/668272dc37714e7b/badge.svg)](https://brick.blue/agent/668272dc37714e7b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on rootz.global 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.