_ registry / mcp http-sse · checked 22m ago

Solana API & WebSocket Docs

https://docs.vybenetwork.com

Registry code: 5bffc68bfdf9a949

api record

Vybe Solana API MCP: OpenAPI discovery, doc search, and live API execution via your API key.

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

endpoint
https://docs.vybenetwork.com/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 Solana API & WebSocket Docs live?
Yes — it answered the hub's last check (checked 22m ago). It answered 100% of checks over the last 30 days.
Is Solana API & WebSocket Docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does Solana API & WebSocket Docs have?
5 tools: search-endpoints, execute-request, pay-with-x402, get-endpoint, list-endpoints.
Is Solana API & WebSocket Docs 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,065ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 297 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • search solana api endpoints
  • get endpoint details
  • execute a solana api request
  • pay for api access with x402
takes → gives
text, data, payments → data
tools
3 reads1 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 5 tools
1 open 4 never probed 1 of 5 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.

  • list-endpoints reads open 22m ago

    Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • search-endpoints reads unknown 22m ago

    Performs a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "pattern"
  ],
  "properties": {
    "pattern": {
      "type": "string",
      "description": "Search pattern (case-insensitive)"
    }
  }
}
    arguments 13 lines
  • execute-request unknown never probed

    Executes an API request with a given HAR request object.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "harRequest"
  ],
  "properties": {
    "harRequest": {
      "type": "object",
      "required": [
        "method",
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "full url to call"
        },
        "method": {
          "type": "string",
          "description": "options, get, head, patch, post, put, delete"
        },
        "headers": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name",
              "value"
            ],
            "properties": {
              "name": {
                "type": "string"
              },
              "value": {
                "type": "string"
              }
            }
          }
        },
        "postData": {
          "anyOf": [
            {
              "type": "object",
              "required": [
                "mimeType",
                "text"
              ],
              "properties": {
                "text": {
                  "type": "string",
                  "description": "Raw request body as a string"
                },
                "mimeType": {
                  "type": "string",
                  "description": "e.g. application/json, text/plain"
                }
              }
            },
            {
              "type": "object",
              "required": [
                "mimeType",
                "params"
              ],
              "properties": {
                "params": {
                  "type": "array",
                  "items": {
                    "type": "object",
                    "required": [
                      "name"
                    ],
                    "properties": {
                      "name": {
                        "type": "string"
                      },
                      "value": {
                        "type": "string"
                      }
                    }
                  },
                  "description": "Form parameters. Use this instead of text for multipart/form-data and url-encoded requests."
                },
                "mimeType": {
                  "type": "string",
                  "description": "e.g. multipart/form-data, application/x-www-form-urlencoded. Use multipart/form-data for form submissions."
                }
              }
            }
          ]
        },
        "queryString": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name",
              "value"
            ],
            "properties": {
              "name": {
                "type": "string"
              },
              "value": {
                "type": "string"
              }
            }
          }
        }
      },
      "description": "HAR request object"
    }
  }
}
    arguments 116 lines
  • pay-with-x402 moves money unknown never probed

    Before calling any Vybe endpoint without an API key (e.g. AI agent, throwaway script, premium-only path), use this to access the same endpoint via x402 pay-per-call USDC on Solana.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get-endpoint reads unknown 22m ago

    Gets detailed information about a specific API endpoint, including security schemes and servers

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "path",
    "method"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "The API endpoint path (e.g. /api/v1/users)."
    },
    "method": {
      "type": "string",
      "description": "The HTTP method (e.g. GET, POST, PUT, DELETE)."
    }
  }
}
    arguments 18 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 5bffc68bfdf9a949.

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

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.