mcpbeat Sign in

AgentPort Discovery MCP Server

by maxioos Your server? Claim it
answering

AgentPort Discovery is answering right now. Last checked 9 min ago. It exposes 3 tools.

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

Uptime history 66 days of history · worst day 0%
66 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
230 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 August 2026. No other catalogue keeps this.

30 Aug 2 tool descriptions were rewritten business.get, capability.resolve
30 Aug a tool changed the parameters it asks for capability.resolve

Nothing serious here today

Today is the operative word: we check AgentPort Discovery every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add agentport-discovery --transport http https://discover.agentport.maxioos.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://discover.agentport.maxioos.com/mcp
~/.codex/config.toml
[mcp_servers.agentport-discovery]
url = "https://discover.agentport.maxioos.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agentport-discovery": {
      "url": "https://discover.agentport.maxioos.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agentport-discovery": {
      "type": "http",
      "url": "https://discover.agentport.maxioos.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

business
business.get
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.
business.search
Find real businesses with published AgentPorts by natural-language need, location, and optional exact capability keys.
capability
capability.resolve
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.

Endpoints

URLTransportStateLatencyChecked
https://discover.agentport.maxioos.com/mcp streamable-http answering 216 ms 9 min ago

Alternatives to AgentPort Discovery

same job, measured the same way
Rhumb MCP
by supertrained

Agent gateway for Index discovery, AN Score evaluation, and Resolve governed execution

55 installs/wk local only
Crabeye MCP Bridge
by crabeye-ai

One MCP connection for all your tools — with discovery, namespacing, and execution policies.

87 installs/wk local only
Simmer
by adlai88

Trade prediction markets with AI agents — skill discovery, autoresearch, and execution.

435 installs/wk local only
AgentBadge
by spreadzp

AgentBadge MCP — agent-readiness scan, passport, discovery, marketplace and circle-payments tools

158 installs/wk local only
Directory
by tasklinkr

Discovery for the agent ecosystem: findable businesses, tools, knowledge, agent spaces, skills.

1 tools answering
Rithmo
by rithmo

AI agent governance with resolved business context, current decisions, provenance, and supersession.

answering
FindMyPart
by jgaethle10

Hard-to-source part discovery with replacement, salvage and fabrication paths.

5 tools answering
Frugal Blender MCP
by mohakmalviya

Let AI agents build Blender scenes with four compact tools: discover, execute, inspect, capture.

152 installs/wk local only

AgentPort Discovery — questions

Answers built from our own checks of this server.

What can AgentPort Discovery do?
It exposes 3 tools, read directly from the server on our last check. Among them: business.get, business.search, capability.resolve. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AgentPort Discovery working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 230 ms. The bar chart above shows every period we have measured.
How do I connect AgentPort Discovery?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AgentPort Discovery need an API key?
No. AgentPort Discovery completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AgentPort Discovery?
It answers our handshake in 230 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.