Wild Orange Charters Public Site Directory
https://wildorangecharters.com
Registry code: a378d8e24755902c
Private 6-passenger deep sea and nearshore fishing charters in Orange Beach, AL aboard the Wild Orange at Zeke’s Landing Marina. Family-owned, fishing the Gulf since 1995, kids welcome.
- endpoint
- https://wildorangecharters.com/mcp
- door code
- 8f7f1a2af68b8063
- protocol
- streamable-http ·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 Wild Orange Charters Public Site Directory live?
- Yes — it answered the hub's last check (checked 23h ago). It answered 93% of checks over the last 30 days.
- Is Wild Orange Charters Public Site Directory free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Wild Orange Charters Public Site Directory have?
- 3 tools: search_pages, read_page, site_info.
- Is Wild Orange Charters Public Site Directory 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.
90 days 98.5%· all time 98.6%
last good check
of 3 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- read a boat charter company's web pages
- search a charter company's site
- takes → gives
- text → web pages, text
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.
through this hub
successful
what callers paid
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.
site_info open 29d ago
What Wild Orange Charters (wildorangecharters.com) is, with links to its sitemap, docs, contact and every discovery document.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linessearch_pages unknown 29d ago
Find pages on wildorangecharters.com by words in their URL path (sitemap search). Returns URLs with a match score.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 20, "maximum": 50, "minimum": 1 }, "query": { "type": "string" } }, "additionalProperties": false }arguments 18 linesread_page unknown 29d ago
Read one https://wildorangecharters.com page as Markdown (Cloudflare Markdown for Agents) or stripped text, up to 40,000 characters.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri" } }, "additionalProperties": false }arguments 13 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your agent card — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida378d8e24755902c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a378d8e24755902c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a378d8e24755902c?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 much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.
Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.
- no usable endpoint declared
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.