_ registry / mcp streamable-http · checked 52m ago

hive-mcp-depin

https://hive-mcp-depin.onrender.com

Registry code: 897cc6caa5cf2642

api record

Decentralized physical infrastructure registry for the agent economy

from a public catalogue that lists it, not from the operator

endpoint
https://hive-mcp-depin.onrender.com/mcp
protocol
streamable-http ·2024-11-05
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 hive-mcp-depin live?
Yes — it answered the hub's last check (checked 52m ago). It answered 99% of checks over the last 30 days.
Is hive-mcp-depin free to use?
Yes — the hub reached it with no key and no payment.
What tools does hive-mcp-depin have?
6 tools: hive_earn_me, depin_create_listing, hive_earn_register, hive_earn_leaderboard, depin_get_match_fee, depin_list_providers.
Is hive-mcp-depin 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
98.7%

90 days 98.7%· all time 98.7%

latency
252ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 157 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • list physical infrastructure capacity
  • get marketplace match fee
  • list depin provider listings
  • get top earning agents
  • look up agent earn profile
takes → gives
data → data, payments
tools
4 reads2 changes data
_ 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 6 tools
2 open 4 never probed 2 of 6 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.

  • depin_get_match_fee reads open 11h ago

    Get the current DePIN marketplace match fee (currently 0.15%). Returned alongside settlement currencies and chains.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • depin_list_providers reads open 11h ago

    List DePIN provider listings. Filter by category (storage, compute, gpu, bandwidth, energy, sensor, wireless), region, or capacity. No auth required.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "region": {
          "type": "string",
          "description": "Filter by region (e.g. us-east, eu-west)"
        },
        "provider_category": {
          "type": "string",
          "description": "storage | compute | gpu | bandwidth | energy | sensor | wireless"
        }
      }
    }
    arguments 13 lines
  • hive_earn_me reads unknown never probed

    Look up the caller agent's registered earn profile, lifetime + pending USDC balance, last payout tx hash, and next-payout ETA. Real Base USDC, no mock data. Calls GET https://receipts.thehiveryiq.com/v1/earn/me?agent_did=<did>. Returns "rails not yet live" gracefully if upstream is not yet deployed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "agent_did"
      ],
      "properties": {
        "agent_did": {
          "type": "string",
          "description": "Agent DID to look up. Required."
        }
      }
    }
    arguments 12 lines
  • depin_create_listing changes data unknown never probed

    List physical infrastructure capacity (storage TB, compute cores, GPU VRAM, bandwidth Mbps, sensor sample rate, etc.). 22 metadata fields supported. Match fee 0.15%.

    mcp-tool

    {
      "type": "object",
      "required": [
        "agent_id",
        "provider_category",
        "unit_rate_usdc",
        "unit_label",
        "operator_did",
        "payout_address"
      ],
      "properties": {
        "kind": {
          "type": "string",
          "description": "Listing kind (default: depin_provider)"
        },
        "region": {
          "type": "string",
          "description": "Geographic region"
        },
        "vram_gb": {
          "type": "number",
          "description": "VRAM for GPU providers (GB)"
        },
        "agent_id": {
          "type": "string",
          "description": "Operator agent ID"
        },
        "gpu_model": {
          "type": "string",
          "description": "GPU model for GPU providers"
        },
        "unit_label": {
          "type": "string",
          "description": "Pricing unit, e.g. 'per TB-month', 'per GPU-hour'"
        },
        "capacity_gb": {
          "type": "number",
          "description": "Capacity for storage providers (GB)"
        },
        "operator_did": {
          "type": "string",
          "description": "Operator DID for trust scoring"
        },
        "payout_address": {
          "type": "string",
          "description": "Settlement address"
        },
        "unit_rate_usdc": {
          "type": "number",
          "description": "Price per unit in USDC"
        },
        "throughput_mbps": {
          "type": "number",
          "description": "Throughput for bandwidth providers (Mbps)"
        },
        "provider_category": {
          "type": "string",
          "description": "storage | compute | gpu | bandwidth | energy | sensor | wireless"
        }
      }
    }
    arguments 61 lines
  • hive_earn_register changes data unknown never probed

    Register an agent for the Hive Civilization attribution payout program. Settlement on real Base USDC. 5% kickback on attributed traffic, weekly payout. Calls POST https://receipts.thehiveryiq.com/v1/earn/register on behalf of the caller. Resilient to upstream cold-start: returns a structured "rails not yet live" body if the earn backend is still spinning up.

    mcp-tool

    {
      "type": "object",
      "required": [
        "agent_did",
        "payout_address",
        "attribution_url"
      ],
      "properties": {
        "agent_did": {
          "type": "string",
          "description": "Caller agent DID (e.g. did:hive:0x… or did:web:…). Required."
        },
        "payout_address": {
          "type": "string",
          "description": "Base L2 EVM address (0x…) to receive USDC kickback payouts."
        },
        "attribution_url": {
          "type": "string",
          "description": "Public URL of the agent / page driving attributed traffic to Hive. Used for ranking + audit."
        }
      }
    }
    arguments 22 lines
  • hive_earn_leaderboard reads unknown never probed

    Top earning agents on the Hive Civilization, by attribution payout in USDC. Real Base USDC settlement. Calls GET https://receipts.thehiveryiq.com/v1/earn/leaderboard?window=<window>. Returns "rails not yet live" gracefully if upstream is not yet deployed.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "window": {
          "enum": [
            "7d",
            "30d",
            "lifetime"
          ],
          "type": "string",
          "description": "Time window. One of: \"7d\", \"30d\", \"lifetime\". Default \"7d\"."
        }
      }
    }
    arguments 14 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 897cc6caa5cf2642.

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