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

Siglume MCP Gateway

https://mcp.siglume.com

Registry code: 1da37bec71704f75

api record

This MCP server provides Siglume API Store and Game API Store surfaces. API Store tools expose installed capabilities for the agent bound to this token, while market_* tools cover store discovery, trials, purchase/activation, agent binding, save state, usage, and support cases. game_* tools cover official sample game invocation. Use siglume_mcp_status first when availability or account binding is unclear, and to see which publisher, seller-support, and MCP Router tools this session actually has; that set varies per connection. For developers who want to publish an API on the API Store, build…

endpoint
https://mcp.siglume.com
protocol
streamable-http ·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 Siglume MCP Gateway live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Siglume MCP Gateway free to use?
Yes — the hub reached it with no key and no payment.
What tools does Siglume MCP Gateway have?
2 tools: mcp_router_inspect_active_tools, mcp_router_search.
Is Siglume MCP Gateway 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 99.3%· all time 99.3%

latency
780ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 277 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· fetch failed
  • unknown → live
_ what it is for
topic
developer tools apis & integration
used for
  • search registered mcp servers
  • inspect tools of an mcp server
takes → gives
text → data
tools
2 reads
_ 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 2 tools
1 open 1 never probed 1 of 2 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.

  • mcp_router_search reads open 15h ago

    Search only external MCP servers registered in Siglume MCP Router. For broad discovery across API Store and MCP Router, use siglume_search.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1
    },
    "query": {
      "type": "string"
    },
    "response_version": {
      "enum": [
        "1"
      ],
      "type": "string",
      "default": "1",
      "description": "Search response contract version. Default 1 keeps the current shape and order. Newer versions are opt-in."
    }
  }
}
    arguments 21 lines
  • mcp_router_inspect_active_tools reads unknown 15h ago

    Read canonical cached tools for an already-active MCP Router server. This never discovers, meters, or contacts the provider.

    mcp-tool

    {
  "type": "object",
  "required": [
    "server_id"
  ],
  "properties": {
    "server_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 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 1da37bec71704f75.

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

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.