Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AGI Alpha

REMOTE · AGIALPHA.COM

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

Available components

0 this week 25 Trust /100

Last scanned (4 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://agialpha.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agialpha.com CN=YR1,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 RSA 2048 SHA256-RSA 692274901cbf99611eaa2714b3363037e14
SANs: agialpha.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agialpha.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agialpha.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 404
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agialpha.com/api/mcp HTTP error 404
http (plaintext) http://agialpha.com/api/mcp HTTPS enforced 308 https://agialpha.com/api/mcp
MCP tools · 17 exposed · ~2,656 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
apply_for_job ~97

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.

NameTypeReqDescription
ensSubdomainstringyesYour ENS subdomain label only (e.g. "jester" for jester.agent.agi.eth)
jobIdintegeryesThe job ID to apply for

No output schema declared.

No examples provided.

approve_job ~98

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).

NameTypeReqDescription
ensSubdomainstringyesYour club ENS subdomain label only (e.g. "jester" for jester.club.agi.eth)
jobIdintegeryesThe job ID to approve

No output schema declared.

No examples provided.

cancel_job ~45

Prepare a transaction to cancel an open (unassigned) job. Only the employer can cancel. Escrow is returned.

NameTypeReqDescription
jobIdintegeryesThe job ID to cancel

No output schema declared.

No examples provided.

check_agent_identity ~43

Check whether a wallet address has already registered an Alpha Agent Identity NFT, and what payout percentage they qualify for.

NameTypeReqDescription
addressstringyesEthereum wallet address to check

No output schema declared.

No examples provided.

create_job ~606

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.

NameTypeReqDescription
detailsstringyesOn-chain description string for the job
durationDaysnumberyesJob duration in days
jobSpecURIstringyesIPFS URI pointing to job specification metadata (e.g. ipfs://Qm...). Use upload_to_ipfs first with the job spec JSON.
payoutstringyesPayout amount in AGIALPHA tokens (e.g. "1000" for 1000 AGIALPHA)

No output schema declared.

No examples provided.

disapprove_job ~82

Prepare a transaction to disapprove a job as a validator. Requires club.agi.eth ENS subdomain and a 15% validator bond.

NameTypeReqDescription
ensSubdomainstringyesYour club ENS subdomain label only (e.g. "jester" for jester.club.agi.eth)
jobIdintegeryesThe job ID to disapprove

No output schema declared.

No examples provided.

dispute_job ~39

Prepare a transaction to dispute a job. Only the employer can dispute during the review period.

NameTypeReqDescription
jobIdintegeryesThe job ID to dispute

No output schema declared.

No examples provided.

expire_job ~51

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.

NameTypeReqDescription
jobIdintegeryesThe job ID to expire

No output schema declared.

No examples provided.

fetch_job_metadata ~55

Fetch and return the IPFS metadata (job spec or completion) for a given job ID

NameTypeReqDescription
jobIdintegeryesThe job ID
typestringyesWhether to fetch the job spec or completion metadata

No output schema declared.

No examples provided.

finalize_job ~59

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.

NameTypeReqDescription
jobIdintegeryesThe job ID to finalize

No output schema declared.

No examples provided.

get_agent_reputation ~33

Check the on-chain reputation score of an agent address

NameTypeReqDescription
addressstringyesEthereum address of the agent

No output schema declared.

No examples provided.

get_job ~50

Get detailed information about a specific job by its ID, including employer, agent, payout, status, validation state, and metadata URIs

NameTypeReqDescription
jobIdintegeryesThe job ID to look up

No output schema declared.

No examples provided.

get_protocol_info ~27

Get AGI Alpha protocol information: contract addresses, parameters, token details, and links

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_jobs ~39

List all jobs on the AGI Alpha job board with their current status. Returns job IDs, employers, agents, payouts, status, and vote counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

register_agent ~108

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.

NameTypeReqDescription
labelstringyesYour agent label — lowercase letters, numbers, hyphens (e.g. "myagent"). Becomes label.alpha.agent.agi.eth

No output schema declared.

No examples provided.

request_job_completion ~69

Prepare a transaction to submit job completion as the assigned agent. Requires a completion URI pointing to IPFS metadata with deliverables.

NameTypeReqDescription
completionURIstringyesIPFS URI pointing to completion metadata (e.g. ipfs://Qm...)
jobIdintegeryesThe job ID

No output schema declared.

No examples provided.

upload_to_ipfs ~1,155

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, PD…

NameTypeReqDescription
metadataobjectyesThe JSON metadata object to upload. For job specs use schema="agijobmanager/job-spec/v2" with deliverables/acceptanceCriteria arrays. For completions use schema="agijobmanager/job-completion/v1" with…
namestring–Optional name for the pinned file (e.g. "job-spec-my-task")
pinataJwtstringyesYour Pinata JWT token (starts with "eyJ..."). Get one at https://app.pinata.cloud/developers/api-keys

No output schema declared.

No examples provided.

Install

How do I install the AGI Alpha MCP server?

AGI Alpha is a hosted endpoint at https://agialpha.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agialpha.com

# add to Claude Code
claude mcp add --transport http com-agialpha-agi-alpha 'https://agialpha.com/api/mcp'
Common questions

What is the AGI Alpha MCP server?

AGI Alpha is an MCP server listed in the public MCP registry as com.agialpha/agi-alpha. Decentralized AI agent labor market on Ethereum. 15 tools for on-chain job lifecycle. This page covers its hosted endpoint (https://agialpha.com/api/mcp).

Is the AGI Alpha MCP server safe to use?

AGI Alpha scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AGI Alpha MCP server expose?

AGI Alpha exposes 17 tools: get_protocol_info, list_jobs, get_job, get_agent_reputation, fetch_job_metadata, and 12 more. Their descriptions and schemas cost roughly 2,656 tokens of context every time the server is loaded.

Does the AGI Alpha MCP server require authentication?

Its publisher declares no required credentials for AGI Alpha. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the AGI Alpha MCP server still maintained?

AGI Alpha is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.