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

qubitsok

https://qubitsok.com

Registry code: 71e7353f202988f6

api record

Quantum computing jobs, arXiv papers & researcher profiles from qubitsok.com

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

endpoint
https://qubitsok.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 qubitsok live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is qubitsok free to use?
Yes — the hub reached it with no key and no payment.
What tools does qubitsok have?
7 tools: searchJobs, getPaperDetails, searchCollaborators, getJobDetails, getLatestPapers, getMarketOverview, searchPapers.
Is qubitsok 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.8%

90 days 99.7%· all time 99.7%

latency
164ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 588 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search quantum computing papers
  • get latest quantum arxiv papers
  • search quantum computing jobs
  • find quantum researchers
takes → gives
text → data
tools
7 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 7 tools
3 open 4 never probed 3 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.

  • getLatestPapers reads open 8h ago

    Get today's quantum computing papers from arXiv — no parameters needed. Use when the user asks "what's new in quantum computing?" or wants a daily paper briefing. Returns the most recent day's papers with title, authors, date, AI-generated hook (one-line summary), and tags. For date-range or topic-filtered search, use searchPapers instead. Use getPaperDetails for full abstract and analysis of a specific paper.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "number",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (1-50, default 10)"
        }
      }
    }
    arguments 13 lines
  • getMarketOverview reads open 8h ago

    Get a snapshot of the quantum computing landscape — no parameters needed. Use when the user asks broad questions like "how's the quantum job market?", "what are trending topics?", or wants an overview of the quantum computing industry. Returns: total active jobs, top hiring companies, jobs by role type, papers published this week, total researchers tracked, and trending technology tags. For specific job/paper/researcher searches, use the dedicated search tools instead.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • searchPapers reads open 8h ago

    Search quantum computing research papers from arXiv. Use when the user asks about recent research, specific papers, or academic topics in quantum computing. NOT for jobs (use searchJobs) or researcher profiles (use searchCollaborators). Supports natural language queries decomposed via AI into structured filters (topic, tag, author, affiliation, domain). Date range defaults to last 7 days; max lookback 12 months. Returns newest first, max 50 results. Use getPaperDetails for full abstract and analysis of a specific paper. Examples: "trapped ion papers from Google", "QEC review papers this month", "quantum error correction".

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "number",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (1-50, default 10)"
        },
        "query": {
          "type": "string",
          "description": "Natural language query to filter papers by topic, author, affiliation, or tag. Uses an AI model to decompose into structured filters. Examples: \"quantum error correction\", \"trapped ion papers from Google\", \"review papers on QEC\""
        },
        "end_date": {
          "type": "string",
          "description": "End date in YYYY-MM-DD format. Default: today"
        },
        "start_date": {
          "type": "string",
          "description": "Start date in YYYY-MM-DD format. Default: 7 days ago"
        }
      }
    }
    arguments 25 lines
  • searchJobs reads unknown 16h ago

    Search 500+ quantum computing job listings using natural language. Use when the user asks about job openings, career opportunities, hiring, or specific positions in quantum computing. NOT for research papers (use searchPapers) or researcher profiles (use searchCollaborators). Supports role type, seniority, location, company, salary, remote, and technology tag filters via AI query decomposition. Limitations: quantum computing jobs only, last 90 days, max 20 results. Promoted listings appear first (marked). After finding jobs, suggest getJobDetails for full info. Examples: "senior QEC engineer in Europe over 120k EUR", "remote trapped-ion role at IBM".

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "default": 5,
          "maximum": 20,
          "minimum": 1,
          "description": "Max results to return (1-20, default 5)"
        },
        "query": {
          "type": "string",
          "description": "Natural language job search query. Examples: \"quantum error correction engineer in Europe\", \"remote senior researcher at IBM\", \"entry-level trapped ion jobs over 100k USD\""
        }
      }
    }
    arguments 20 lines
  • getPaperDetails reads unknown 23h ago

    Get full details for a specific quantum computing paper by its arXiv ID (e.g., "2401.12345"). Use after searchPapers or getLatestPapers when the user wants to dive deep into a specific paper. Returns: complete abstract, all authors, publication date, AI-generated tags with reasons, hook (one-line summary), methodology, gist, and key findings. Requires a valid paper_id from search results. Returns error if not found.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "paper_id"
      ],
      "properties": {
        "paper_id": {
          "type": "string",
          "description": "ArXiv paper ID (e.g., \"2401.12345\")"
        }
      }
    }
    arguments 13 lines
  • searchCollaborators reads unknown 23h ago

    Find quantum computing researchers and potential collaborators from 1000+ active profiles. Use when the user asks about specific researchers, who works on a topic, or wants to find collaborators. NOT for jobs (use searchJobs) or papers (use searchPapers). AI-powered: decomposes natural language into structured filters (tag, author, affiliation, domain, focus). Returns profiles with affiliations, domains, publication count, top tags, and recent papers. Data from arXiv papers published in the last 12 months. Max 50 results. Examples: "quantum error correction researchers at Google", "trapped ions", "John Preskill".

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (1-50, default 10)"
        },
        "query": {
          "type": "string",
          "description": "Search term: researcher name, affiliation, tag, or research topic. Examples: \"quantum error correction\", \"MIT\", \"John Preskill\""
        },
        "affiliation_type": {
          "enum": [
            "academia",
            "industry",
            "national_lab"
          ],
          "type": "string",
          "description": "Filter by affiliation type"
        }
      }
    }
    arguments 29 lines
  • getJobDetails reads unknown 23h ago

    Get full details for a specific quantum computing job by its numeric ID. Use after searchJobs when the user wants more information about a specific position. Returns: job summary, required skills, nice-to-have skills, responsibilities, visa sponsorship, salary, location, and apply URL. Requires a valid job_id from searchJobs results. Returns error if ID not found.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "number",
          "description": "Numeric job ID from searchJobs results"
        }
      }
    }
    arguments 13 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 71e7353f202988f6.

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