_ registry / mcp http-sse · checked 1h ago

agentport-discovery

https://discover.agentport.maxioos.com

Registry code: a26febf7893e94b5

api record

Use business.search to discover candidate businesses when canonical capability/action keys are unknown, then business.get to inspect exact provider-published keys. Never invent capability or action identifiers. For actionable requests that ask whether a provider exposes a machine-capable action or execution path, capability.resolve is the final discovery step. Do not stop at business.get: after exact provider-published keys are known, call capability.resolve to evaluate eligibility and return the provider-owned execution path. Call capability.resolve only with canonical keys returned by…

endpoint
https://discover.agentport.maxioos.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is agentport-discovery live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is agentport-discovery free to use?
Yes — the hub reached it with no key and no payment.
What tools does agentport-discovery have?
3 tools: business.get, capability.resolve, business.search.
Is agentport-discovery safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
242ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 363 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • find businesses that expose agent actions
  • inspect a business's published capabilities
  • resolve a user goal to a provider execution path
takes → gives
text, data → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • business.search reads open 15h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 120
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 500,
          "description": "Natural-language business need, for example \"collision repair that can book an appointment\"."
        },
        "region": {
          "type": "string",
          "maxLength": 120,
          "description": "State, province, or region code/name."
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90
        },
        "radiusKm": {
          "type": "number",
          "maximum": 1000,
          "exclusiveMinimum": 0
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180
        },
        "countryCode": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "maxLength": 2,
          "minLength": 2
        },
        "capabilities": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 96,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Optional exact AgentPort capability keys that every result must expose."
        }
      },
      "additionalProperties": false
    }
    arguments 57 lines
  • business.get reads unknown 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "pattern": "^[a-z0-9][a-z0-9-]+$",
          "maxLength": 96,
          "minLength": 2
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • capability.resolve reads unknown 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "intent"
      ],
      "properties": {
        "intent": {
          "type": "string",
          "maxLength": 512,
          "minLength": 1
        },
        "location": {
          "type": "object",
          "properties": {
            "city": {
              "type": "string",
              "maxLength": 160
            },
            "near": {
              "type": "string",
              "maxLength": 160
            },
            "region": {
              "type": "string",
              "maxLength": 160,
              "description": "Region must match provider-published geography when used as a hard location requirement (for example WA rather than an invented synonym)."
            },
            "latitude": {
              "type": "number",
              "maximum": 90,
              "minimum": -90
            },
            "radiusKm": {
              "type": "number",
              "maximum": 1000,
              "exclusiveMinimum": 0
            },
            "longitude": {
              "type": "number",
              "maximum": 180,
              "minimum": -180
            },
            "postalCode": {
              "type": "string",
              "maxLength": 160
            },
            "countryCode": {
              "type": "string",
              "pattern": "^[A-Z]{2}$"
            }
          },
          "additionalProperties": false
        },
        "constraints": {
          "type": "object"
        },
        "preferences": {
          "type": "object"
        },
        "schemaVersion": {
          "enum": [
            "1.0"
          ],
          "type": "string"
        },
        "desiredActions": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 128
          },
          "maxItems": 16,
          "description": "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/business.get first when unknown."
        },
        "desiredOutcome": {
          "type": "string",
          "maxLength": 128,
          "minLength": 1
        },
        "preferredActions": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 128
          },
          "maxItems": 16,
          "description": "Exact canonical AgentPort action keys already published by a provider. Never invent or infer keys."
        },
        "executionRequired": {
          "type": "boolean"
        },
        "requiredCapabilities": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 128
          },
          "maxItems": 16,
          "description": "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."
        },
        "preferredCapabilities": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 128
          },
          "maxItems": 16,
          "description": "Exact canonical AgentPort capability keys already published by a provider. Never invent or infer keys."
        }
      },
      "additionalProperties": false
    }
    arguments 112 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a26febf7893e94b5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a26febf7893e94b5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a26febf7893e94b5/badge.svg)](https://brick.blue/agent/a26febf7893e94b5?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.