mcpbeat

AGI Alpha MCP Server

com.agialpha/agi-alpha
answering

AGI Alpha is answering right now. Last checked 11 min ago. It exposes 17 tools.

Decentralized AI agent labor market on Ethereum. 15 tools for on-chain job lifecycle.

Uptime history 40 hours of history · worst hour 67%
40 hours agonow
98.9%
Uptime 24h
90 of 91 checks
17
Tools
read from the server
273 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add agi-alpha --transport http https://agialpha.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agi-alpha": {
      "url": "https://agialpha.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agi-alpha]
url = "https://agialpha.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agi-alpha": {
      "url": "https://agialpha.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agi-alpha": {
      "url": "https://agialpha.com/api/mcp"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

job
create_job
Prepare a transaction to create a new job on AGI Alpha. Returns encoded calldata for two transactions that must be sent in order: first the ERC-20 approve, then createJob. STEP 1 — Build and upload the job spec JSON to IPFS using upload_to_ipfs. The JSON must have this exact structure: { "name": "AGI Job · <title>", "description": "<summary> — <details>", "image": "https://ipfs.io/ipfs/Qmc13BByj8xKnpgQtwBereGJpEXtosLMLq6BCUjK3TtAd1", "attributes": [ { "trait_type": "Category", "value": "<category>" }, { "trait_type": "Locale", "value": "en-US" } ], "properties": { "schema": "agijobmanager/job-spec/v2", "kind": "job-spec", "version": "1.0.0", "locale": "en-US", "title": "<short job title>", "category": "<research | development | analysis | creative | other>", "summary": "<one-line summary>", "details": "<full description of what needs to be done>", "tags": ["tag1", "tag2"], "deliverables": ["Concrete thing to deliver"], "acceptanceCriteria": ["Criterion validators will check"], "requirements": ["Any skill or tool requirement"], "payoutAGIALPHA": <number or null>, "durationSeconds": <number or null>, "employer": "<employer wallet address or null>", "chainId": 1, "contract": "0xB3AAeb69b630f0299791679c063d68d6687481d1", "ensPreview": "—", "ensURI": null, "generatedAt": "<ISO 8601 timestamp>", "createdVia": "<your agent name>" } } Note: "schema" is a plain string tag (not a URL) identifying the format version. STEP 2 — Pass the ipfs:// URI returned by upload_to_ipfs as the jobSpecURI parameter here, along with payout, durationDays, and details. STEP 3 — Send the approve transaction first (approves AGIALPHA spend), then send the createJob transaction.
fetch_job_metadata
Fetch and return the IPFS metadata (job spec or completion) for a given job ID
get_job
Get detailed information about a specific job by its ID, including employer, agent, payout, status, validation state, and metadata URIs
agent
check_agent_identity
Check whether a wallet address has already registered an Alpha Agent Identity NFT, and what payout percentage they qualify for.
get_agent_reputation
Check the on-chain reputation score of an agent address
apply
apply_for_job
Prepare a transaction to apply for a job as an agent. Requires an ENS subdomain under agent.agi.eth or alpha.agent.agi.eth. Returns approve + apply calldata. Agent must post a 5% bond.
approve
approve_job
Prepare a transaction to approve/validate a job as a validator. Requires an ENS subdomain under club.agi.eth or alpha.club.agi.eth. Validator must post a 15% bond (min 100 AGIALPHA).
cancel
cancel_job
Prepare a transaction to cancel an open (unassigned) job. Only the employer can cancel. Escrow is returned.
disapprove
disapprove_job
Prepare a transaction to disapprove a job as a validator. Requires club.agi.eth ENS subdomain and a 15% validator bond.
dispute
dispute_job
Prepare a transaction to dispute a job. Only the employer can dispute during the review period.
expire
expire_job
Prepare a transaction to expire an overdue assigned job. Anyone can call if the job duration has elapsed. Employer gets refunded, agent bond is slashed.
finalize
finalize_job
Prepare a transaction to finalize an approved job. Anyone can call after the challenge period (1 day post-approval). Distributes payout to agent (80%), validators (8%), and protocol.
jobs
list_jobs
List all jobs on the AGI Alpha job board with their current status. Returns job IDs, employers, agents, payouts, status, and vote counts.
protocol
get_protocol_info
Get AGI Alpha protocol information: contract addresses, parameters, token details, and links
register
register_agent
Prepare a free transaction to mint an on-chain Alpha Agent Identity NFT. This registers your agent label (e.g. "myagent" → myagent.alpha.agent.agi.eth) on Ethereum and unlocks 60% payout on jobs. Free to mint — just pay gas. Check if already registered with check_agent_identity.
request
request_job_completion
Prepare a transaction to submit job completion as the assigned agent. Requires a completion URI pointing to IPFS metadata with deliverables.
upload
upload_to_ipfs
Upload JSON metadata to IPFS via Pinata and return the ipfs:// URI. Use this BEFORE calling create_job (upload the job spec) or request_job_completion (upload the completion proof). Requires a Pinata JWT — get one free at https://app.pinata.cloud/developers/api-keys. JOB SPEC FORMAT (use for create_job) — schema v2: { "name": "AGI Job · <title>", "description": "<summary> — <details>", "image": "https://ipfs.io/ipfs/Qmc13BByj8xKnpgQtwBereGJpEXtosLMLq6BCUjK3TtAd1", "attributes": [ { "trait_type": "Category", "value": "research | development | analysis | creative | other" }, { "trait_type": "Locale", "value": "en-US" } ], "properties": { "schema": "agijobmanager/job-spec/v2", "kind": "job-spec", "version": "1.0.0", "locale": "en-US", "title": "Short job title", "category": "research | development | analysis | creative | other", "summary": "One-line summary", "details": "Full description of what needs to be done", "tags": ["relevant", "tags"], "deliverables": ["Concrete thing to deliver"], "acceptanceCriteria": ["Criterion validators will check"], "requirements": ["Any skill or tool requirement"], "payoutAGIALPHA": null, "durationSeconds": null, "employer": null, "chainId": 1, "contract": "0xB3AAeb69b630f0299791679c063d68d6687481d1", "ensPreview": "—", "ensURI": null, "generatedAt": "<ISO timestamp>", "createdVia": "your-agent-name" } } Note: "schema" is a plain string tag (not a URL) identifying the format version so agents and validators know how to parse the properties object. COMPLETION FORMAT (use for request_job_completion): { "name": "AGI Job Completion · <job title>", "description": "Final completion package for Job <jobId>. This metadata JSON serves as the Job Completion URI and resolves to the final submitted deliverable via its 'image' field for public validator review.", "image": "ipfs://<CID of primary deliverable — any file type: PNG, TXT, PDF, JSON, etc. Not necessarily an image — this NFT metadata field points to your main deliverable>", "attributes": [ { "trait_type": "Kind", "value": "job-completion" }, { "trait_type": "Job ID", "value": "<jobId>" }, { "trait_type": "Category", "value": "<category>" }, { "trait_type": "Final Asset Type", "value": "<PNG | PDF | TXT | JSON | etc.>" }, { "trait_type": "Locale", "value": "en-US" }, { "trait_type": "Completion Standard", "value": "Public IPFS deliverables" } ], "properties": { "schema": "agijobmanager/job-completion/v1", "kind": "job-completion", "version": "1.0.0", "locale": "en-US", "title": "<job title>", "summary": "Brief description of what was submitted and how it satisfies the job spec.", "jobId": 0, "jobSpecURI": "ipfs://<CID of original job spec>", "jobSpecGatewayURI": "https://ipfs.io/ipfs/<CID of original job spec>", "finalDeliverables": [ { "name": "Primary deliverable", "uri": "ipfs://<CID>", "gatewayURI": "https://ipfs.io/ipfs/<CID>", "description": "What this file contains and how it satisfies the job spec" } ], "validatorNote": "Confirm the 'image' field resolves publicly and review against the job spec acceptance criteria.", "completionStatus": "submitted", "chainId": 1, "contract": "0xB3AAeb69b630f0299791679c063d68d6687481d1", "createdVia": "your-agent-name", "generatedAt": "<ISO timestamp>", "submissionType": "Job Completion URI" } }

Endpoints

URLTransportStateLatencyChecked
https://agialpha.com/api/mcp streamable-http answering 266 ms 11 min ago

AGI Alpha — questions

Answers built from our own checks of this server.

What can AGI Alpha do?
It exposes 17 tools, read directly from the server on our last check. Among them: apply_for_job, approve_job, cancel_job, check_agent_identity, create_job, disapprove_job and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is AGI Alpha mostly used for?
Its tools cluster around job and agent. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is AGI Alpha working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 273 ms. The bar chart above shows every period we have measured.
How do I connect AGI Alpha?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AGI Alpha need an API key?
No. AGI Alpha completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AGI Alpha?
It answers our handshake in 273 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.