AgentPort Discovery

io.github.maxioosPublished by GitHub account maxioosv0.10.0Updated Oct 24, 2026

Resolve goals to machine-capable businesses and execution paths with discovery tools.

The publisher's own server: Port

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that resolves a stated goal into machine-capable businesses and execution paths using discovery tools.

What you can do
AgentPort Discovery is a remote MCP server reachable over streamable HTTP at a hosted endpoint. According to its registry description, it provides discovery tools that resolve goals to machine-capable businesses and execution paths. No individual tools, parameters, or output formats are documented in the supplied material, so the exact operations available are not described here.
When to use it
Consider it when an assistant needs to map a goal to businesses or services that can be acted on programmatically, and to possible execution paths for reaching them. Because the tool list is undocumented, evaluate it against a concrete task before relying on it.
Requirements
A remote streamable HTTP connection to the hosted endpoint. No packages, environment variables, headers, or authentication are declared, and no local runtime is needed.
Before you install
The server is hosted by a third party, so any goal text or query sent to it leaves the user's machine and is processed remotely. No authentication is declared, so it is unclear how requests are attributed or rate-limited. The tool list and data handling practices are undocumented; avoid sending confidential business or personal information until these are confirmed.

Installation

In SourceWeft

  1. Open AgentPort Discovery 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/io.github.maxioos%2Fagentport-discovery/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": {
    "agentport-discovery": {
      "type": "http",
      "url": "https://discover.agentport.maxioos.com/mcp"
    }
  }
}

Tools

3

capability.resolve

Resolve an executable capability

Final discovery step for actionable goals: resolve a structured user goal to ranked machine-capable resources and provider-owned execution paths without executing the selected action. Use this after business.search/business.get whenever the user asks whether a provider can expose a machine-capable action or execution path. Any requiredCapabilities/preferredCapabilities/desiredActions/preferredActions values must be exact canonical AgentPort keys already published by a provider; never invent keys. If exact keys are unknown, use business.search and business.get first.

ParametersintentrequiredlocationconstraintspreferencesschemaVersiondesiredActionsdesiredOutcomepreferredActionsexecutionRequiredrequiredCapabilitiespreferredCapabilities

business.get

Get an AgentPort business

Inspection step: resolve one discovered business by its stable AgentPort registry slug and inspect its exact published capability/action keys. For actionable requests, this is not final resolution; call capability.resolve after the relevant canonical keys are known.

Parametersslugrequired

Version history

1
  1. v0.10.0LatestSep 16, 2026

Score

83% 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
  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.

Other Port integrations