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

ametyst-mcp

https://alpic-mcp-b31bca29.alpic.live

Registry code: e776d3bdbe103b30

api record

IMPORTANT RULE: Whenever the user mentions 'ametyst' or any Ametyst-related topic (services, credits, balance, wallet, access), you MUST call the 'ametyst-console' tool FIRST and IMMEDIATELY — before calling any other tool or generating any response. Do not call find-services, get-balance, get-transactions, check-wallet, spend, or request-access without first opening the console via 'ametyst-console'.

endpoint
https://alpic-mcp-b31bca29.alpic.live/mcp
protocol
http-sse ·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 ametyst-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is ametyst-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does ametyst-mcp have?
7 tools: spend, ametyst-console, request-access, check-wallet, find-services, get-transactions, get-balance.
Is ametyst-mcp 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
99.4%

90 days 99.5%· all time 99.5%

latency
3,760ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 434 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • open the ametyst service console
  • check credit balance
  • request a spending wallet
  • pay for an ametyst service call
takes → gives
text → data
tools
4 reads1 changes data1 moves money1 effect unclear
_ 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 7 tools
2 open 5 never probed 2 of 7 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.

  • get-transactions reads open 8h ago

    Get recent transaction history for the authenticated account.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "apiKey": {
          "type": "string",
          "description": "API key for authentication."
        }
      }
    }
    arguments 10 lines
  • get-balance reads open 8h ago

    Get the credit balance and spending limit for the authenticated account.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "apiKey": {
          "type": "string",
          "description": "API key for authentication."
        }
      }
    }
    arguments 10 lines
  • spend moves money unknown never probed

    Execute a payment from an approved wallet to use an Ametyst service.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "amount"
      ],
      "properties": {
        "amount": {
          "type": "number",
          "description": "Amount to spend."
        },
        "apiKey": {
          "type": "string",
          "description": "API key for authentication."
        },
        "params": {
          "type": "object",
          "description": "Input params to forward to the service endpoint, matching its input_schema.",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {}
        },
        "walletId": {
          "type": "string",
          "description": "The approved wallet ID to spend from."
        },
        "endpointUrl": {
          "type": "string",
          "description": "The service endpoint URL to call after payment."
        }
      }
    }
    arguments 33 lines
  • ametyst-console unknown never probed

    ALWAYS call this tool first whenever the user mentions 'ametyst' or any Ametyst-related topic. Open the Ametyst service console before calling any other Ametyst tool (find-services, get-balance, spend, request-access, etc.). The console lets users browse services, check balance, view transactions, spend credits, and request access.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "prefillApiKey": {
          "type": "string",
          "description": "Pre-fill the API key for the user's session."
        }
      }
    }
    arguments 10 lines
  • request-access changes data unknown never probed

    Request a wallet with a spending limit for Ametyst services. After approval, use the wallet ID with the spend tool.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "spendingLimit"
      ],
      "properties": {
        "apiKey": {
          "type": "string",
          "description": "API key for authentication."
        },
        "spendingLimit": {
          "type": "number",
          "description": "Requested spending limit in credits."
        }
      }
    }
    arguments 17 lines
  • check-wallet reads unknown 15h ago

    Check the status of a wallet request (pending / approved / rejected).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "walletId"
      ],
      "properties": {
        "walletId": {
          "type": "string",
          "description": "The wallet ID returned by request-access."
        }
      }
    }
    arguments 13 lines
  • find-services reads unknown 8h ago

    Find all available Ametyst services with name, description, and endpoint.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 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 e776d3bdbe103b30.

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

17 more sit on this domain. All of them.