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

gigaverse

https://gigaverse.ai

Registry code: a7163e248d092783

api record

Portable Roth IRA signups for gig workers: eligibility checks, signup initiation, partners, sandbox.

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

endpoint
https://gigaverse.ai/api/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 gigaverse live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is gigaverse free to use?
Yes — the hub reached it with no key and no payment.
What tools does gigaverse have?
5 tools: check_roth_eligibility, start_signup, get_signup_status, register_partner, get_practicle_info.
Is gigaverse 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
97.9%

90 days 97.9%· all time 98.5%

latency
307ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 243 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • check roth ira eligibility
  • start a retirement account signup
  • check signup status
  • register as an integration partner
takes → gives
data → data
tools
3 reads2 changes data
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ 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.

  • get_practicle_info reads open 13h ago

    Get information about the Gigaverse PRActicle™ — a portable Roth IRA for gig workers, freelancers, and the self-employed (custody through a FINRA/SIPC-member broker-dealer). Returns product description, pricing, launch status, and links. Educational only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • check_roth_eligibility reads unknown 13h ago

    Educational Roth IRA MAGI phase-out check using 2026 IRS limits. NOT tax or investment advice — always show the returned disclaimer to the user. Takes filing_status and MAGI (USD).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "filing_status",
        "magi"
      ],
      "properties": {
        "magi": {
          "type": "number",
          "maximum": 100000000,
          "minimum": 0,
          "description": "Modified adjusted gross income in USD"
        },
        "filing_status": {
          "enum": [
            "single",
            "head_of_household",
            "married_joint",
            "married_separate"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • start_signup changes data unknown never probed

    Initiate a Gigaverse retirement-account signup for your user. This does NOT open an account: it returns a signup_url that the HUMAN account owner must open and complete personally (identity, suitability, and brokerage agreements cannot be completed by an agent). Idempotent per email. Provide the user's email (required), name, gig platforms, and your partner_id if you have one.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "email"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 80,
          "description": "The user's name"
        },
        "email": {
          "type": "string",
          "description": "The user's email address"
        },
        "sandbox": {
          "type": "boolean",
          "description": "true = test mode: nothing is stored, no email is sent, and the returned signup auto-progresses through the full lifecycle for testing"
        },
        "platforms": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 10,
          "description": "Gig platforms, e.g. [\"uber\",\"doordash\"]"
        },
        "partner_id": {
          "type": "string",
          "maxLength": 60,
          "description": "Partner attribution slug (from /api/agent/partners)"
        }
      },
      "additionalProperties": false
    }
    arguments 36 lines
  • get_signup_status reads unknown never probed

    Check the status of a previously initiated signup by signup_id. Statuses: initiated (awaiting the human's confirmation), waitlist_joined (human confirmed), account_opened (future). Returns no personal information.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "signup_id"
      ],
      "properties": {
        "signup_id": {
          "type": "string",
          "pattern": "^gv_(sgn|test)_[a-z0-9]+$"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • register_partner changes data unknown never probed

    Register a company (developer, platform, or retirement broker) as a Gigaverse integration partner. Returns a partner_id attribution slug immediately (status pending_review) — pass it on start_signup so signups are attributed to the partner. No API secrets are issued pre-RIA; advisory services and partner revenue share launch upon RIA registration approval.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "company",
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "Business contact email"
        },
        "company": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Company or organization name"
        },
        "sandbox": {
          "type": "boolean",
          "description": "true = test mode: returns a test- partner_id, stores nothing"
        },
        "website": {
          "type": "string",
          "maxLength": 200,
          "description": "Company website URL"
        }
      },
      "additionalProperties": false
    }
    arguments 30 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 a7163e248d092783.

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