AgentPort Discovery
Server Details
Resolve goals to machine-capable businesses and execution paths with discovery tools.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: business.search finds candidates, business.get inspects a specific business's published capability keys, and capability.resolve maps a structured goal to execution paths. There is no meaningful overlap between them.
All tool names follow the same [domain].[verb] pattern: business.get, business.search, capability.resolve. The naming is consistent, readable, and predictable.
Three tools is well-scoped for a focused discovery server: search, inspect, and resolve. Each tool earns its place in the workflow without redundancy.
The tool surface covers the full discovery lifecycle: finding businesses, examining exact capability keys, and resolving actionable goals to execution paths. The cross-references between tools prevent dead ends and guide agents to the correct sequence.
Available Tools
3 toolsbusiness.getGet an AgentPort businessARead-onlyIdempotentInspect
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.
Inputs: slug (required).
business.searchSearch AgentPort businessesARead-onlyIdempotentInspect
Find real businesses with published AgentPorts by natural-language need, location, and optional exact capability keys.
Inputs: city, limit, query, region, +5 more.
capability.resolveResolve an executable capabilityARead-onlyIdempotentInspect
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.
Inputs: intent (required), location, constraints, preferences, +7 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Discover MCP endpoints for real-world entities by resolving business domains.
Discover, compare, route, and execute machine-accessible capabilities for AI agents.
Discover and execute authorized API capabilities through QuoAPI policy, routing and billing.
Discovery for the agent ecosystem: findable businesses, tools, knowledge, agent spaces, skills.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding tools to discover local Skills, plugin metadata, and runtime tools from configured sources, then classify a task's request and produce advisory cards (skip, consult, adapt, or execute) that the host may act on. Supports staged lookups under a single route ID and collaboration planning without executing recommended business tools or expanding user authorization.MIT
- AlicenseNot gradedqualityCmaintenanceProvides deterministic search, load, and execution operations for progressively disclosing agent capabilities (skills, MCP, CLI, HTTP/API, RAG). Enables scope-bound reference access with budgets and audit.MIT
- AlicenseBqualityBmaintenanceEnables local deterministic discovery, validation, and selection of validated skills through MCP tools, producing consistent plans without executing any skill.546 PyPI1Apache 2.0
- AlicenseAqualityDmaintenanceEnables models to discover, inspect, and call tools from thousands of MCP servers on the fly through a single gateway, without pre-configuring each server.565 npm3MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.