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

btc-intel

https://9eouter-0f49c8.abyte.my.id

Registry code: 4fb6d6c674c17a08

api record

Live Stacks/Bitcoin market data plus npm/PyPI dependency version and health lookups. Pay-per-call x402.

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

endpoint
https://9eouter-0f49c8.abyte.my.id/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 btc-intel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is btc-intel free to use?
Yes — the hub reached it with no key and no payment.
What tools does btc-intel have?
6 tools: package_health, stacks_pox_cycle, bitcoin_fee_tiers, stacks_market, sbtc_supply, dependency_versions.
Is btc-intel 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
707ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 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.

  • package_health unknown 1h ago

    Stale / deprecated / outdated verdict for a list of dependencies.

    mcp-tool

    {
  "type": "object",
  "required": [
    "packages"
  ],
  "properties": {
    "packages": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Package names to check"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • stacks_pox_cycle unknown never probed

    Live Stacks PoX cycle: stacked ustx, minimum threshold, current + next cycle phases, block height.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • bitcoin_fee_tiers unknown never probed

    Bitcoin fee tiers (fast/30m/1h/economy) plus Stacks mempool fee recommendations.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • stacks_market unknown never probed

    STX/USD, BTC/USD, STX-BTC ratio and sats-per-STX, refreshed from live sources.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • sbtc_supply unknown never probed

    sBTC total supply on Stacks in sats and BTC.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • dependency_versions unknown never probed

    Latest published version and release metadata for an npm or PyPI package.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Package name, e.g. \"hono\" or \"requests\""
    },
    "registry": {
      "enum": [
        "npm",
        "pypi"
      ],
      "type": "string",
      "description": "Which registry to query"
    }
  },
  "additionalProperties": false
}
    arguments 21 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 4fb6d6c674c17a08.

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

_ also on my.id 4 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.