stillopen
Registry code: f8a83b1d3e0f938c
StillOpen tracks fully-remote job listings and re-checks each one against the
employer's own job board, so a listing here is either currently open or marked
- endpoint
- https://stillopen.work/mcp
- door code
- 22dd1f9f9cd6ebbf
- 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 stillopen live?
- Yes — it answered the hub's last check (checked 56m ago). It answered 100% of checks over the last 30 days.
- Is stillopen free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does stillopen have?
- 4 tools: get_job, check_job_status, get_company_stats, search_jobs.
- Is stillopen 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
- 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.
search_jobs open 56m ago
Find fully-remote job listings, each re-checked against the employer's own job board. Returns a summary record per role — no job descriptions, because twenty ads would fill your context with roles the reader did not choose. Call `get_job` for the ad once one looks worth reading. Every record carries `evidence_type` and `verified_at`: present those with the listing rather than asserting it is open.
{ "type": "object", "properties": { "q": { "type": "string", "description": "free text over the title, the skills read from the ad, and the ad body" }, "loc": { "type": "string", "description": "an ISO 3166-1 alpha-2 country code (`de`), a macro region (`emea`), `worldwide` for roles with no stated restriction, or `unspecified`. A country answers 'can I apply from here', so it includes roles open across a region containing it" }, "pay": { "enum": [ 40000, 60000, 80000, 100000, 120000, 150000, 200000 ], "type": "integer", "description": "minimum annual pay. Compared against the top of the published range in the currency published; nothing is converted, and a job board's estimate is excluded" }, "area": { "enum": [ "consulting", "content", "customer", "design", "engineering", "finance", "healthcare", "legal", "operations", "people", "product", "sales_marketing" ], "type": "string", "description": "functional area, read from the title rather than from the employer's department field" }, "level": { "enum": [ "junior", "mid", "senior", "lead", "manager", "head", "unspecified" ], "type": "string", "description": "seniority, read from the title. `unspecified` is the 40% of titles that state none, which is not the same as mid" }, "limit": { "type": "integer", "maximum": 20, "minimum": 1, "description": "1-20, default 10" }, "cursor": { "type": "string", "description": "from a previous response's `next_cursor`" }, "company": { "type": "string", "description": "a `company_slug` from any record. Not a company name — names collide, and several here belong to two unrelated employers" } }, "additionalProperties": false }arguments 72 linesget_job unknown never probed
One listing in full, including the employer's own ad. Use it after `search_jobs` rather than instead of it: this returns thousands of characters of advertisement. The id is the number in a listing URL — /job/9620-company-title is 9620. A listing that was folded into another answers under the id you asked for and reports `merged_into`.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "integer", "minimum": 1, "description": "the listing id" } }, "additionalProperties": false }arguments 14 linescheck_job_status unknown 56m ago
Whether each of up to 100 listings is still open, and on what evidence — in one call. The most useful tool here: given a link to a role somebody is about to apply for, this is what separates a live posting from a filled one, with a date and a kind of evidence attached. A closed listing reports whether the closure was **observed** (a source was asked and said the posting was gone) or **inferred** (it aged out, which is a guess about the employer rather than an answer from one). This reads evidence already stored: it reports the result of our most recent check, and does not perform a live check against the employer's board at the moment you call it. Two dates come back and they answer different questions: **`verified_at`** is when we last asked the employer's system and it said yes, and it is the one to show a reader; `last_seen_at` is when a source last carried the posting, which happens far more often and is normally the newer of the two. `last_seen_at` being newer is ordinary, not a contradiction. **`status: unknown` means we have never held this id** — it is not-found, not un-checked. The value for 'nothing has proved it gone but no source has carried it lately' is `unconfirmed`.
{ "type": "object", "required": [ "ids" ], "properties": { "ids": { "type": "array", "items": { "type": "integer" }, "maxItems": 100, "minItems": 1, "description": "up to 100 listing ids" } }, "additionalProperties": false }arguments 18 linesget_company_stats unknown 56m ago
What one employer's listings on this site add up to: how many roles are open, where they hire, what they hire for, and what their listings disclose about pay. Takes a `company_slug` from any search record. Answers only for employers whose board identity we have confirmed, because a page asserting one company's vacancies under another company's name is the failure this gate exists to prevent.
{ "type": "object", "required": [ "company_slug" ], "properties": { "company_slug": { "type": "string", "description": "a `company_slug` from any record" } }, "additionalProperties": false }arguments 13 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 idf8a83b1d3e0f938c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f8a83b1d3e0f938c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f8a83b1d3e0f938c?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
- 2
- ok
- 0
- failed
- 2
- success rate
- 0%
- median latency
- 97ms
- 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
- —
2 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.