omaha-hi-lo
Registry code: efa691da59082223
Prepare a table only when requested. Return the join_url unchanged, including its fragment. Humans play on the website. Share private invitations only with intended players. MCP does not play hands or access private cards.
- endpoint
- https://omahahilopoker.com/mcp
- 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 omaha-hi-lo live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is omaha-hi-lo free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does omaha-hi-lo have?
- 4 tools: get_play_link, create_poker_table, get_table_status, get_game_info.
- Is omaha-hi-lo 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 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
get_game_info open 1h ago
Explain Omaha Hi-Lo rules, free guest play, supported features and website links.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {}, "additionalProperties": false }arguments 6 linesget_play_link unknown never probed
Prepare a NEW playable table and return its join link. Supports bots or friends. Reuse a previously returned link instead of calling again when possible.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "private": { "type": "boolean", "default": true }, "bot_count": { "type": "integer", "maximum": 9, "minimum": 1 }, "game_type": { "type": "string", "const": "omaha_hi_lo", "default": "omaha_hi_lo" }, "opponents": { "enum": [ "bots", "friends" ], "type": "string", "default": "bots" }, "player_name": { "type": "string", "maxLength": 30, "minLength": 1 } }, "additionalProperties": false }arguments 34 linescreate_poker_table unknown never probed
Create a real free Omaha Hi-Lo table for bot practice or friends. Return its join link; the human plays on the website. First human to join becomes host. Never place bets or play for the user.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "private": { "type": "boolean", "default": true }, "bot_count": { "type": "integer", "maximum": 9, "minimum": 1 }, "game_type": { "type": "string", "const": "omaha_hi_lo", "default": "omaha_hi_lo" }, "opponents": { "enum": [ "bots", "friends" ], "type": "string", "default": "bots" }, "player_name": { "type": "string", "maxLength": 30, "minLength": 1 } }, "additionalProperties": false }arguments 34 linesget_table_status unknown 1h ago
Read only existence, waiting/in-progress state and available seats. Never returns names, credentials, invitations or cards.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "table_id" ], "properties": { "table_id": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" } }, "additionalProperties": false }arguments 15 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 MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idefa691da59082223.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/efa691da59082223/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/efa691da59082223?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
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.