_ registry / mcp streamable-http · checked 11h ago

Mapping API MCP Server

https://api.hsk.oray.com

Registry code: fb7a8c6d49ed3a14

api record
endpoint
https://api.hsk.oray.com/v1/mcp-server/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 it live, free and safe measured by this hub
Is Mapping API MCP Server live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is Mapping API MCP Server free to use?
Not measured yet.
What tools does Mapping API MCP Server have?
10 tools: create_mapping, mapping_status_switch, update_mapping, check_port_availability, delete_mapping, get_domain_list, get_forward_service, list_mappings, ….
Is Mapping API MCP Server 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 100%· all time 100%

latency
1,982ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ 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 10 tools
10 never probed 0 of 10 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.

  • create_mapping unknown never probed

    Create a new intranet penetration tunnel mapping

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain",
        "fwtype",
        "service_host",
        "service_port",
        "memo"
      ],
      "properties": {
        "memo": {
          "type": "string",
          "description": "Memo/Description for the mapping"
        },
        "port": {
          "type": "string",
          "description": "External port (0 for random allocation). Default is 0."
        },
        "type": {
          "type": "string",
          "description": "Mapping type (0=normal). Default is 0."
        },
        "domain": {
          "type": "string",
          "description": "Domain for the mapping"
        },
        "fwtype": {
          "type": "string",
          "description": "Protocol type: 1=TCP, 2=HTTP, 3=HTTPS, 4=UDP, 5=SOCKS5"
        },
        "service_host": {
          "type": "string",
          "description": "Internal service host IP (e.g., 127.0.0.1)"
        },
        "service_port": {
          "type": "string",
          "description": "Internal service port"
        }
      }
    }
    arguments 40 lines
  • mapping_status_switch unknown never probed

    Start or stop a mapping (switch on/off)

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain",
        "port",
        "fwtype",
        "switch"
      ],
      "properties": {
        "port": {
          "type": "string",
          "description": "External port of the mapping"
        },
        "domain": {
          "type": "string",
          "description": "Domain of the mapping"
        },
        "fwtype": {
          "type": "string",
          "description": "Protocol type"
        },
        "switch": {
          "type": "string",
          "description": "Switch status: 'on' to stop/forbid, 'off' to start/enable"
        }
      }
    }
    arguments 27 lines
  • update_mapping unknown never probed

    Update an existing mapping

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain",
        "port",
        "fwtype",
        "service_host",
        "new_service_port",
        "memo"
      ],
      "properties": {
        "memo": {
          "type": "string",
          "description": "New memo/description"
        },
        "port": {
          "type": "string",
          "description": "Current external port of the mapping"
        },
        "type": {
          "type": "string",
          "description": "Mapping type (0=normal). Default is 0."
        },
        "domain": {
          "type": "string",
          "description": "Domain of the mapping"
        },
        "fwtype": {
          "type": "string",
          "description": "Protocol type"
        },
        "service_host": {
          "type": "string",
          "description": "Internal service host IP"
        },
        "new_service_port": {
          "type": "string",
          "description": "New internal service port"
        }
      }
    }
    arguments 41 lines
  • check_port_availability unknown never probed

    Check if a specific port is available. Note: When creating mappings with port 0 (random allocation), port availability check is not needed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "port"
      ],
      "properties": {
        "port": {
          "type": "string",
          "description": "Port number to check (use 0 for random allocation in create_mapping tool)"
        }
      }
    }
    arguments 12 lines
  • delete_mapping unknown never probed

    Delete a mapping by domain and external port.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain",
        "port",
        "fwtype"
      ],
      "properties": {
        "port": {
          "type": "string",
          "description": "External port of the mapping"
        },
        "domain": {
          "type": "string",
          "description": "Domain of the mapping"
        },
        "fwtype": {
          "type": "string",
          "description": "Protocol type"
        }
      }
    }
    arguments 22 lines
  • get_domain_list unknown never probed

    Get the list of available domains for mapping

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_forward_service unknown never probed

    Get forward service info (quota, bandwidth, supported protocols)

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • list_mappings unknown never probed

    List all active Peanut Hull intranet penetration mappings

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_mapping_info unknown never probed

    Get mapping info by domain and port

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain",
        "port",
        "fwtype"
      ],
      "properties": {
        "port": {
          "type": "string",
          "description": "External port"
        },
        "domain": {
          "type": "string",
          "description": "Domain of the mapping"
        },
        "fwtype": {
          "type": "string",
          "description": "Protocol type"
        }
      }
    }
    arguments 22 lines
  • search_mappings_by_memo unknown never probed

    Search mappings by memo

    mcp-tool

    {
      "type": "object",
      "required": [
        "memo"
      ],
      "properties": {
        "memo": {
          "type": "string",
          "description": "Memo/Name to search"
        }
      }
    }
    arguments 12 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 fb7a8c6d49ed3a14.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fb7a8c6d49ed3a14/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/fb7a8c6d49ed3a14/badge.svg)](https://brick.blue/agent/fb7a8c6d49ed3a14?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
100%

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.