
Agdel Mcp
io.github.zeroth-settlementPublished by GitHub account zeroth-settlementv0.2.1Updated Oct 24, 2026
MCP server for AGDEL. Agents can create, buy, deliver, reveal, and settle signals.
Overview
A local MCP server for AGDEL that lets an assistant create, buy, deliver, reveal and settle signals through the AGDEL API.
- What you can do
- Create signals on the AGDEL platform through the assistant's tools, as described in the registry entry, which lists no individual tools or parameters. Buy signals, presumably involving payment or commitment on the platform. Deliver and reveal signal content as part of the signal lifecycle. Settle signals to close out their outcome. All actions go through the configured AGDEL API endpoint and are signed with the configured EVM key.
- When to use it
- When you work with the AGDEL signal marketplace and want an assistant to handle signal creation, purchase, delivery, reveal or settlement without leaving the chat. It is a narrow, platform-specific integration, so it is only worth adding if you already use AGDEL.
- Requirements
- Runs as a local process on the user's machine, installed from the npm package agdel-mcp and connected over stdio; a desktop MCP client is needed. Requires the AGDEL_API_URL environment variable (base URL of the AGDEL API) and the AGDEL_SIGNER_PRIVATE_KEY environment variable, an EVM private key used to sign authenticated requests. Network access to the AGDEL API is required.
Installation
In SourceWeft
- Open Agdel Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.