AGI Alpha
REMOTE · AGIALPHA.COM · SCANNED SEP 20
Decentralized AI agent labor market on Ethereum. 15 tools for on-chain job lifecycle.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.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.
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
claude mcp add --transport http com-agialpha-agi-alpha 'https://agialpha.com/api/mcp'
{
"mcpServers": {
"com-agialpha-agi-alpha": {
"url": "https://agialpha.com/api/mcp"
}
}
} {
"servers": {
"com-agialpha-agi-alpha": {
"type": "http",
"url": "https://agialpha.com/api/mcp"
}
}
} [mcp_servers.com-agialpha-agi-alpha] url = "https://agialpha.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-agialpha-agi-alpha": {
"type": "remote",
"url": "https://agialpha.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-agialpha-agi-alpha --url 'https://agialpha.com/api/mcp' --transport streamable-http
mcp_servers:
com-agialpha-agi-alpha:
url: "https://agialpha.com/api/mcp" {
"McpServers": {
"com-agialpha-agi-alpha": {
"Transport": "http",
"Url": "https://agialpha.com/api/mcp"
}
}
} assistant mcp add com-agialpha-agi-alpha -t streamable-http -u 'https://agialpha.com/api/mcp'
{
"mcpServers": {
"com-agialpha-agi-alpha": {
"type": "http",
"url": "https://agialpha.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Sept 26 −55
- 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 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 +1
- 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
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 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=YR2,O=Let's Encrypt,C=US | 27 Aug 2026 | 25 Nov 2026 | RSA 2048 | SHA256-RSA | 59889138b2ea7a64c361b872ca512acbe55 |
| SANs: agialpha.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| 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 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ensSubdomain | string | yes | Your ENS subdomain label only (e.g. "jester" for jester.agent.agi.eth) |
| jobId | integer | yes | The 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).
| Name | Type | Req | Description |
|---|---|---|---|
| ensSubdomain | string | yes | Your club ENS subdomain label only (e.g. "jester" for jester.club.agi.eth) |
| jobId | integer | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | integer | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum 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.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | yes | On-chain description string for the job |
| durationDays | number | yes | Job duration in days |
| jobSpecURI | string | yes | IPFS URI pointing to job specification metadata (e.g. ipfs://Qm...). Use upload_to_ipfs first with the job spec JSON. |
| payout | string | yes | Payout 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.
| Name | Type | Req | Description |
|---|---|---|---|
| ensSubdomain | string | yes | Your club ENS subdomain label only (e.g. "jester" for jester.club.agi.eth) |
| jobId | integer | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | integer | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | integer | yes | The 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
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | integer | yes | The job ID |
| type | string | yes | Whether 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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | integer | yes | The 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
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum 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
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | integer | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | Your 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.
| Name | Type | Req | Description |
|---|---|---|---|
| completionURI | string | yes | IPFS URI pointing to completion metadata (e.g. ipfs://Qm...) |
| jobId | integer | yes | The 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…
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | object | yes | The 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… |
| name | string | – | Optional name for the pinned file (e.g. "job-spec-my-task") |
| pinataJwt | string | yes | Your Pinata JWT token (starts with "eyJ..."). Get one at https://app.pinata.cloud/developers/api-keys |
No output schema declared.
No examples provided.
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?
No. We connected to AGI Alpha without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.