spacejobs-now
Registry code: 1af6d51baff61caa
SpaceJobs.Now lists the open space industry jobs (engineering, manufacturing, operations and the other kinds of work at the companies that build and launch rockets, satellites and spacecraft, and at their suppliers) in one place, from the job boards of the employers that publish one, read every hour, each role counted once, with the pay each role advertises. Use search_space_jobs to find open roles, get_space_jobs_pay for what each kind of work pays, and get_space_jobs_market for how many roles are open by kind of work and employer. Share the role links with the user: they open the role on…
- endpoint
- https://spacejobs.now/api/mcp
- 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 spacejobs-now live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is spacejobs-now free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does spacejobs-now have?
- 4 tools: get_space_jobs_pay, get_hiring_radar, search_space_jobs, get_space_jobs_market.
- Is spacejobs-now 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
through this hub
successful
what callers paid
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_hiring_radar open 1h ago
Hiring radar, SpaceJobs.Now's dataset for investors: every space industry role on the employers' own job boards since its first read, one row per role with advertised pay, field, countries and open and close dates, plus each employer by day and a change log. Returns what it covers today, its files, who uses it, the price and how to get a sample.
{ "type": "object", "additionalProperties": false }arguments 4 linessearch_space_jobs open 1h ago
Search the open space industry jobs (at the companies that build and launch rockets, satellites and spacecraft, and their suppliers) read from the job boards of 47 employers. Returns each role's title, employer, kind of work, advertised pay, where it is open and a link to apply on SpaceJobs.Now. All filters are optional.
{ "type": "object", "properties": { "kind": { "enum": [ "propulsion", "mechanical-structures", "avionics-electrical", "rf-communications", "gnc-flight-software", "ground-software", "systems-test", "manufacturing", "launch-mission-ops", "quality-safety", "science-imaging", "supply-chain-facilities", "business-programs" ], "type": "string", "description": "Kind of work. One of the listed slugs, e.g. 'propulsion', 'mechanical-structures', 'avionics-electrical'." }, "limit": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1, "description": "How many roles to return (1 to 25)." }, "query": { "type": "string", "description": "Keywords matched against role titles, e.g. 'propulsion', 'avionics', 'technician', 'mission operations'." }, "country": { "type": "string", "description": "ISO 3166-1 alpha-2 code (e.g. 'US', 'IN', 'BR'): only roles open to applicants in that country." }, "platform": { "type": "string", "description": "Employer slug, e.g. 'spacex', 'blue-origin', 'rocket-lab'. get_space_jobs_market lists them." }, "min_hourly_usd": { "type": "integer", "maximum": 1000, "minimum": 1, "description": "Only roles whose advertised hourly ceiling reaches this many US dollars." } }, "additionalProperties": false }arguments 50 linesget_space_jobs_market open 1h ago
How many space industry jobs are open right now, how many were listed in the last 7 days, and the open roles by kind of work and by employer (with each employer's slug for search_space_jobs). Optionally scoped to the roles open to applicants in one country.
{ "type": "object", "properties": { "country": { "type": "string", "description": "ISO 3166-1 alpha-2 code (e.g. 'US', 'KE'): count only roles open to applicants in that country." } }, "additionalProperties": false }arguments 10 linesget_space_jobs_pay unknown never probed
What space industry work pays per hour today, by kind of work: the median and the typical range (25th to 75th percentile) of the rates open roles advertise, with how many rates and employers each figure comes from. A rate is shown only when at least three employers advertise it.
{ "type": "object", "additionalProperties": false }arguments 4 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id1af6d51baff61caa.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1af6d51baff61caa/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1af6d51baff61caa?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.