Openings
REMOTE · OPENINGS.AVAGAMA.CO
Search jobs on verified employer job boards. Every link is the employer's own posting.
Available components
Last scanned (12 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 868 tokens (~217/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Nov 26 +19
- Authorization: unverified → partial ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- 13 Nov 26 −19
- Authorization: partial → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 −1
- Stability: pass → 0.93 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://openings.avagama.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=avagama.co | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6bcb12ca0229612b0e1b3ee5f7a6d44d |
| SANs: avagama.co, *.avagama.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of openings.avagama.co. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| avagama.co. | DS published | 2371 | 13 | Verified |
| openings.avagama.co. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://openings.avagama.co/mcp | Verified | 200 | |
| http (plaintext) | http://openings.avagama.co/mcp | HTTPS enforced | 308 | https://openings.avagama.co/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_job Get job details ~49
Get the full description and application URL for a job returned by recommend_jobs or search_jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Stable job id returned by search_jobs or recommend_jobs (jobId is accepted too) |
| Name | Type | Req | Description |
|---|---|---|---|
| job | object | yes | The full job, including its description and the employer's application URL |
No examples provided.
get_job_coverage Check job coverage ~90
Report how many live roles the index holds for each country and how recently they were posted. Use it to set expectations before asking a candidate for anything, or to judge whether preparation is worth running; use search_jobs instead to see the roles themselves. Reads the index already on hand and never crawls.
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | yes | Two-letter codes to report coverage for, such as IN or US |
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | – | Per-country live and recent role counts |
| snapshotUpdatedAt | string | – | When the index this answer came from was last refreshed |
No examples provided.
prepare_job_search Prepare job search ~187
Download and refresh the local job index so searches have data to read. The first call fetches the shared index of every verified source (thousands of employers); later calls crawl only missing or stale sources, at most 25 per call, returning a continuation token until nextAction reports ready. Call it when a search says setup is needed, not before every search, and not at all on the hosted server, where the index is already prepared and this returns ready at once. Uses the network and writes job data under the local Openings data directory; it never reads, writes or transmits a resume.
| Name | Type | Req | Description |
|---|---|---|---|
| continuation | string | – | Opaque token from the previous call's result. Pass it back to prepare the next batch of at most 25 sources; omit it to start |
| countries | array | yes | Two-letter codes whose sources should be prepared, such as IN or US |
| Name | Type | Req | Description |
|---|---|---|---|
| continuation | string | – | Token for the next batch; present only when nextAction is call_again |
| coverage | object | yes | – |
| crawl | object | – | What this batch crawled: selected, succeeded, and the sources that failed |
| networkAttempted | boolean | – | Whether this call actually reached out to employer boards |
| nextAction | string | yes | call_again means pass continuation back for the next batch; retry_later means the network refused and waiting is the fix |
| note | string | – | – |
| sources | object | – | How many sources are in the catalog, indexed, fresh, stale, missing and pending |
| status | string | yes | ready means searches can run now; partial means sources are still missing |
No examples provided.
search_jobs Search jobs ~278
Search jobs immediately from role, country, location and optional stated experience. No resume required. Newest first; automatically widens 7, 14, 30 days then all dates until 5 matches. For another page reuse the same filters and returned window.daysUsed as maxAgeDays, with pagination.nextOffset. Resume-based ranking is optional via recommend_jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter country code for job eligibility, such as IN or DE |
| experienceYears | number | – | Years of experience to compare with the posting's stated min/max range; not a qualification or fit verdict. |
| includeUnknownExperience | boolean | – | With experienceYears, also keep roles without a stated range, clearly unknown rather than matched. |
| limit | integer | – | How many jobs to return in this page |
| location | string | – | Case-insensitive location substring |
| maxAgeDays | integer | – | Omit to widen 7/14/30/all until 5 matches. Explicit positive values exclude undated roles; 0 includes all dates. |
| offset | integer | – | Where the page starts. Use pagination.nextOffset from the previous result rather than counting by hand |
| query | string | – | Words to match in job title or company |
| remote | boolean | – | True for remote-only; false for non-remote-only |
| Name | Type | Req | Description |
|---|---|---|---|
| guidance | string | – | How to present these results honestly; meant for the assistant, not the candidate |
| jobs | array | yes | Matches, newest first |
| pagination | object | yes | offset, limit, total and nextOffset. nextOffset is null on the last page |
| window | object | yes | The age window the results came from, and whether it had to widen. Say which window was used |
No examples provided.
How do I install the Openings MCP server?
Openings is a hosted endpoint at https://openings.avagama.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · openings.avagama.co
claude mcp add --transport http co-avagama-openings 'https://openings.avagama.co/mcp'
What is the Openings MCP server?
Openings is an MCP server listed in the public MCP registry as co.avagama/openings. Search jobs on verified employer job boards. Every link is the employer's own posting. This page covers its hosted endpoint (https://openings.avagama.co/mcp).
Is the Openings MCP server safe to use?
Openings scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Openings MCP server expose?
Openings exposes 4 tools: prepare_job_search, get_job_coverage, search_jobs, get_job. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.
Does the Openings MCP server require authentication?
No. We connected to Openings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Openings MCP server still maintained?
Openings is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Openings MCP server?
VerifyMCP ran 13 checks on Openings, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.