Alya — The Hub for Autonomous Agents

io.github.Rupert1987Published by GitHub account Rupert1987v1.0.2Updated Oct 24, 2026

Operator-as-agent MCP hub. 6 tools. First $5 free, then $0.001/call.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingFinanceMedia & Design

Overview

AI-generated overview

A remote or local MCP hub giving an assistant web search, image generation, prediction-market and paper-trading status, and a chat agent, billed per call.

What you can do
Search the live web in Turkish and English and get a synthesized answer with sources, and generate images from text prompts with FLUX.1-schnell. Check Alya's current Polymarket edge ranking and Alpaca paper-trading status. Talk to Alya, the operator agent, through a chat tool. Connect either through a local stdio bridge package or directly to the hosted HTTP endpoint.
When to use it
Useful when you want a single hosted endpoint that bundles web search, image generation and light market or trading-status lookups, and you are comfortable with a metered, pay-per-call service. Not needed if you already have separate tools for search and images.
Requirements
Either the hosted HTTP endpoint or the npm package run locally with Node.js via npx. A required API key supplied in the ALYA_API_KEY environment variable (or a bearer token for direct HTTP); a free key with $5 credit is issued on signup. Network access to the provider's domain.
Before you install
The service is metered: the first $5 of credit is free, then $0.001 per call, so usage spends money. The ALYA_API_KEY is a secret and should be kept out of shared configs and repositories. Queries and prompts are sent to a third-party operator, and the market and trading tools report another party's rankings and paper-trading status rather than your own accounts.

Installation

In SourceWeft

  1. Open Alya — The Hub for Autonomous Agents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Rupert1987%2Falya-hub/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "alya-the-hub-for-autonomous-agents": {
      "type": "http",
      "url": "https://mydaughteralya.com/mcp"
    }
  }
}

README

@mydaughteralya/mcp

Stdio MCP client for Alya — The Hub for Autonomous Agents.

Bridges any stdio-MCP client (Cursor, Claude Desktop, Cline, Continue, etc.) to Alya's public HTTP MCP endpoint.

Tools available

  • web_search — live web search (TR/EN), synthesized answer + sources
  • image_gen — FLUX.1-schnell text-to-image
  • polymarket_edge — Alya's current Polymarket edge ranking
  • alpaca_paper_status — Alpaca paper-trading status
  • alya_ask — talk to Alya, the operator agent

Pricing

  • First $5 in credit free on signup.
  • After that, $0.001 per call.

Get an API key

bash
curl -X POST https://mydaughteralya.com/api/agent/keys/issue \  -H "Content-Type: application/json" \  -d '{"label":"my-agent","contactEmail":"[email protected]"}'

Response includes apiKey: "alya_…" — keep it secret.

Cursor

~/.cursor/mcp.json:

json
{  "mcpServers": {    "alya": {      "command": "npx",      "args": ["-y", "@mydaughteralya/mcp"],      "env": { "ALYA_API_KEY": "alya_..." }    }  }}

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "alya": {      "command": "npx",      "args": ["-y", "@mydaughteralya/mcp"],      "env": { "ALYA_API_KEY": "alya_..." }    }  }}

Cline / Continue / others

Same shape — point at the alya-mcp bin and pass ALYA_API_KEY as env.

Direct HTTP

If you don't want the stdio bridge, call the HTTP endpoint directly:

bash
curl -X POST https://mydaughteralya.com/mcp \  -H "Authorization: Bearer alya_..." \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Discoverable

  • https://mydaughteralya.com/.well-known/agent.json (A2A)
  • https://mydaughteralya.com/.well-known/ai-plugin.json (OpenAI plugin)
  • https://mydaughteralya.com/.well-known/mcp.json (MCP)
  • https://mydaughteralya.com/openapi.json (OpenAPI 3.1)

Operated by Alya, the autonomous agent. ALYA SATILMAZ.

Examples

Drop-in configs for Cursor, Claude Desktop, Cline, plus Python/curl snippets:

Source: README.md at commit 0442b33

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.