_ registry / mcp http-sse · checked 46m ago

apify-mcp-server

https://mcp.toolstem.com

Registry code: 3e5810a0a16c692c

api record

Apify is the world's largest marketplace of tools for web scraping, data extraction, and web automation.

These tools are called **Actors**. They enable you to extract structured data from social media, e-commerce, search engines, maps, travel sites, and many other sources.

endpoint
https://mcp.toolstem.com/mcp/sec
protocol
http-sse ·2025-06-18
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 apify-mcp-server live?
Yes — it answered the hub's last check (checked 46m ago). It answered 100% of checks over the last 30 days.
Is apify-mcp-server free to use?
No — it charges per call, from 0.005 USDC, quoted in its own 402 answers.
What tools does apify-mcp-server have?
5 tools: get_company_filings_summary, get_material_events_digest, get_insider_signal, get_institutional_signal, compare_disclosure_signals.
Is apify-mcp-server 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
100%

90 days 100%· all time 100%

latency
830ms

last good check

priced tools
5

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
5 paid 5 of 5 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.

  • get_company_filings_summary 0.005 USDC paid 46m ago

    Retrieve a structured overview of a company's SEC filing activity. Returns the most recent 20 filings and pre-computed signals: filing velocity (ACCELERATING / NORMAL / SLOWING vs. trailing 365-day average), material event count in the last 90 days, 10-K disclosure volume trend (RISING / STABLE / FALLING), and the unique form types filed in the last 90 days. Use this as a first-pass signal before digging into insider or material-event detail.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker_or_cik"
      ],
      "properties": {
        "ticker_or_cik": {
          "type": "string",
          "minLength": 1,
          "description": "Ticker symbol (e.g. \"AAPL\") or numeric CIK (e.g. \"320193\" or \"0000320193\")."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_material_events_digest 0.5 USDC paid 46m ago

    Retrieve a severity-ranked digest of all 8-K and 8-K/A filings for a company within a configurable lookback window. Each event is tagged with item codes mapped to plain-English labels, categories, and severity (RED / YELLOW / GREEN). Returns redflag_count (events with any RED item) and category_counts for quick categorical analysis. Answers: "Has this company disclosed a cybersecurity incident, restatement, or going-concern risk recently?" Premium-tier tool. See the actor pricing page for current per-call cost.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker_or_cik"
      ],
      "properties": {
        "lookback_days": {
          "type": "integer",
          "default": 365,
          "maximum": 1825,
          "minimum": 1,
          "description": "Number of calendar days to include (max 5 years)."
        },
        "ticker_or_cik": {
          "type": "string",
          "minLength": 1,
          "description": "Ticker symbol (e.g. \"AAPL\") or numeric CIK (e.g. \"320193\" or \"0000320193\")."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • get_insider_signal paid never probed

    Probe insider filing activity (Form 3, 4, 4/A) for a company over a configurable lookback window. Answers: "Are insiders filing recently?" Returns recent Form 4 filing references and counts. NOTE: Direction-aware buy/sell signals (insider_signal, buy_count, sell_count) are null/0 in v0.1 — Form 4 XML parsing ships in v0.2.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker_or_cik"
      ],
      "properties": {
        "lookback_days": {
          "type": "integer",
          "default": 90,
          "maximum": 730,
          "minimum": 1,
          "description": "Number of calendar days to look back."
        },
        "ticker_or_cik": {
          "type": "string",
          "minLength": 1,
          "description": "Ticker symbol (e.g. \"AAPL\") or numeric CIK (e.g. \"320193\" or \"0000320193\")."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • get_institutional_signal paid never probed

    Probe institutional and activist investor signals for a company. Returns a live activist_risk_flag (true if any SC 13D or 13D/A was filed in the last 365 days — an activist investor has disclosed a large stake). Also lists the 13D filings and their SEC URLs. NOTE: Institutional accumulation/distribution signal (institutional_signal) and recent_13f_count are null/0 in v0.1 — quarterly 13F XBRL parsing ships in v0.2.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker_or_cik"
      ],
      "properties": {
        "quarters_back": {
          "type": "integer",
          "default": 4,
          "maximum": 20,
          "minimum": 1,
          "description": "Number of calendar quarters to look back (default 4 ≈ 1 year)."
        },
        "ticker_or_cik": {
          "type": "string",
          "minLength": 1,
          "description": "Ticker symbol (e.g. \"AAPL\") or numeric CIK (e.g. \"320193\" or \"0000320193\")."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • compare_disclosure_signals paid never probed

    Side-by-side comparison of 2-5 companies across key SEC disclosure signals: filing velocity, material event count (90d), red-flag count (365d), activist risk flag, and most recent filing date. Returns derived "winners" for each dimension — quietest disclosure, most active filer, most red flags, and companies with active activist investors. All lookups run in parallel. Use for competitive intelligence or risk triage across a watchlist.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tickers_or_ciks"
      ],
      "properties": {
        "tickers_or_ciks": {
          "type": "array",
          "items": {
            "type": "string",
            "minLength": 1
          },
          "maxItems": 5,
          "minItems": 2,
          "description": "2-5 ticker symbols or CIKs to compare (e.g. [\"AAPL\", \"MSFT\", \"GOOGL\"])."
        }
      },
      "additionalProperties": false
    }
    arguments 19 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 3e5810a0a16c692c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3e5810a0a16c692c/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/3e5810a0a16c692c/badge.svg)](https://brick.blue/agent/3e5810a0a16c692c?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
90%

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.