# AgentPort Discovery (remote · discover.agentport.maxioos.com)

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

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `discover.agentport.maxioos.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/maxioos-agentport-discovery/discover.md), [page](https://verifymcp.io/servers/maxioos-agentport-discovery/discover)

## Channel facts

- Endpoint: `https://discover.agentport.maxioos.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.10.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 619 tokens (~206/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the AgentPort Discovery MCP server?

AgentPort Discovery is a hosted endpoint at https://discover.agentport.maxioos.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http maxioos-agentport-discovery 'https://discover.agentport.maxioos.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "maxioos-agentport-discovery": {
      "url": "https://discover.agentport.maxioos.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "maxioos-agentport-discovery": {
      "type": "http",
      "url": "https://discover.agentport.maxioos.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.maxioos-agentport-discovery]
url = "https://discover.agentport.maxioos.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "maxioos-agentport-discovery": {
      "type": "remote",
      "url": "https://discover.agentport.maxioos.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add maxioos-agentport-discovery --url 'https://discover.agentport.maxioos.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  maxioos-agentport-discovery:
    url: "https://discover.agentport.maxioos.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "maxioos-agentport-discovery": {
      "Transport": "http",
      "Url": "https://discover.agentport.maxioos.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add maxioos-agentport-discovery -t streamable-http -u 'https://discover.agentport.maxioos.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "maxioos-agentport-discovery": {
      "type": "http",
      "url": "https://discover.agentport.maxioos.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `capability.resolve` (~290 tokens)

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.

Input parameters:

- `constraints` (object)
- `desiredActions` (array): Exact canonical AgentPort action keys already published by a provider (for example appointment.get_availability or appointment.create). Never invent or infer keys; discover them with business.search/…
- `desiredOutcome` (string)
- `executionRequired` (boolean)
- `intent` (string, required)
- `location` (object)
- `preferences` (object)
- `preferredActions` (array): Exact canonical AgentPort action keys already published by a provider. Never invent or infer keys.
- `preferredCapabilities` (array): Exact canonical AgentPort capability keys already published by a provider. Never invent or infer keys.
- `requiredCapabilities` (array): Exact canonical AgentPort capability keys already published by a provider. Never invent or infer keys; discover them with business.search/business.get first when unknown.
- `schemaVersion` (string)

### `business.search` (~127 tokens)

Search AgentPort businesses

Find real businesses with published AgentPorts by natural-language need, location, and optional exact capability keys.

Input parameters:

- `capabilities` (array): Optional exact AgentPort capability keys that every result must expose.
- `city` (string)
- `countryCode` (string)
- `latitude` (number)
- `limit` (integer)
- `longitude` (number)
- `query` (string): Natural-language business need, for example "collision repair that can book an appointment".
- `radiusKm` (number)
- `region` (string): State, province, or region code/name.

### `business.get` (~59 tokens)

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.

Input parameters:

- `slug` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/maxioos-agentport-discovery/discover#diagnostics

## Score history

- 2026-09-25: 75
- 2026-09-24: 75
- 2026-09-23: 75
- 2026-09-22: 74
- 2026-09-21: 74
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 68
- 2026-09-07: 67
- 2026-09-06: 67
- 2026-09-05: 66
- 2026-09-04: 66
- 2026-09-03: 65
- 2026-09-02: 65
- 2026-09-01: 64
- 2026-08-31: 64
- 2026-08-30: 63
- 2026-08-29: 63
- 2026-08-28: 64

## Common questions

### What is the AgentPort Discovery MCP server?

AgentPort Discovery is an MCP server listed in the public MCP registry as io.github.maxioos/agentport-discovery. Resolve goals to machine-capable businesses and execution paths with discovery tools. This page covers its hosted endpoint (https://discover.agentport.maxioos.com/mcp).

### Is the AgentPort Discovery MCP server safe to use?

AgentPort Discovery scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the AgentPort Discovery MCP server expose?

AgentPort Discovery exposes 3 tools: capability.resolve, business.search, business.get. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.

### Does the AgentPort Discovery MCP server require authentication?

No. We connected to AgentPort Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AgentPort Discovery MCP server still maintained?

AgentPort Discovery is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://discover.agentport.maxioos.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/maxioos-agentport-discovery/discover.xml
- Changelog JSON feed: https://verifymcp.io/servers/maxioos-agentport-discovery/discover.json
- HTML version of this page: https://verifymcp.io/servers/maxioos-agentport-discovery/discover