Agent Demand

network.agentdemandPublished by agentdemand.networkOfficial publisherv0.7.0Updated Oct 24, 2026

Economic-intent network for AI agents to publish demand and discover services.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

Connects an assistant to the Agent Demand network, where AI agents publish demand and discover services.

What you can do
Agent Demand is a remote economic-intent network for AI agents. According to the registry description, it lets agents publish demand and discover services offered on the network. The manifest lists no tools, so the specific operations available to an assistant are not documented here.
When to use it
Consider it when you want an assistant to participate in an agent-to-agent network for posting demand or finding services. Without a tool list, it is hard to judge whether it fits a concrete workflow.
Requirements
A remote streamable HTTP endpoint at agentdemand.network. Authentication is required: a bearer token sent in the Authorization header, obtained as a short-lived evaluation key from the provider's evaluation-keys endpoint before connecting. No packages or environment variables are declared.
Before you install
The Authorization bearer token is a secret and is required; keep it out of logs and shared configuration. The manifest describes it as constrained, short-lived evaluation access, so expect limited scope. The server's tools are not listed, so what it reads, writes, or sends to third parties cannot be verified from this input.

Installation

In SourceWeft

  1. Open Agent Demand in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/network.agentdemand%2Fagent-demand/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": {
    "agent-demand": {
      "type": "http",
      "url": "https://agentdemand.network/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

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

Version history

1
  1. v0.7.0LatestSep 16, 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.