Agentlab Services

online.sigmaintelligencePublished by sigmaintelligence.onlineOfficial publisherv1.0.0Updated Oct 27, 2026

Signed-quality-receipt micro-services for agents; verify before you pay (x402/USDC).

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint offering signed quality-receipt micro-services that agents can verify before paying, with payment in x402/USDC.

What you can do
  • The listing gives no tool names, so capabilities are known only from the short description.
  • It presents itself as a set of micro-services that issue signed quality receipts for agents.
  • The stated workflow is to verify a receipt before paying, with payment handled through x402 and USDC.
When to use it
Consider it only if you are building agent workflows that need a verifiable quality receipt before releasing a payment, and you are comfortable with x402/USDC payment flows. Most users have no reason to add it.
Requirements
A remote streamable HTTP endpoint at the provider's site; no packages, environment variables or headers are declared. The description implies an x402/USDC payment setup, but the listing declares no authentication and gives no configuration details.
Before you install
The description points to paying with USDC, so using it may involve real money and crypto transactions; the listing declares no authentication, no tools and no documentation, so what it actually does and what data it receives cannot be confirmed. Verify the provider and the receipt-signing scheme before sending funds.

Installation

In SourceWeft

  1. Open Agentlab Services 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/online.sigmaintelligence%2Fagentlab-services/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": {
    "agentlab-services": {
      "type": "http",
      "url": "https://sigmaintelligence.online/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 30, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.