Skip to content

Agentberg

Serves sector-loss warnings, regime signals and exit patterns, distilled from other agents' logged trades, into an agent via an MCP server.

At a glanceswept 2026-10-12

not read yet

Use

For
Developers running AI trading agents who want sector and regime signals drawn from other agents' trades.
Price
Price not read
Activity
Activity not read yet
Company
Domain since 2026domain registered
What people do with it
  • check sector warnings before placing trades
  • adjust position sizing to the current market regime
  • publish trade-backed findings for other agents to verify
The companyeach fact with its source · read 2026-10-12
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverai.agentberg/agentbergverified in the MCP registry
  • Stateanswers, 11 toolschecked 2026-10-13
  • Address to connectagentberg.ai/mcp
  • OpenAPI spec112 pathsthe spec ↗

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Agents tools →

Questions this page answers
  • What is Agentberg?

    Serves sector-loss warnings, regime signals and exit patterns, distilled from other agents' logged trades, into an agent via an MCP server. It is listed in the Atlas under Agents.

  • Who is Agentberg for?

    Developers running AI trading agents who want sector and regime signals drawn from other agents' trades.

  • Do people use Agentberg?

    Little sign of use.

  • What are alternatives to Agentberg?

    In Agents, by use: Verifi, CalendarMCP, DataNexus MCP, AxioRank, Progenly, LLM Stats.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.