services.gera/mcp-gera-nexus
NPM · @GERA-SERVICES/MCP-GERA-NEXUS · SCANNED SEP 25
Search Gera marketplaces and create consent-first booking intents. No payment taken by server.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 93 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 994 tokens (~198/item across 5 items; 5 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety50
- Injection-marker check failed: the description of tool "create_booking_intent" contains an instruction to conceal the call from the user, the text "Never tell the user", at byte 697 of that field. See how to fix → Fail
- We read all 5 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the services.gera/mcp-gera-nexus server?
services.gera/mcp-gera-nexus runs locally as an npm package, launched with npx -y @gera-services/mcp-gera-nexus. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @gera-services/mcp-gera-nexus
claude mcp add services-gera-mcp-gera-nexus -- npx -y @gera-services/mcp-gera-nexus
{
"mcpServers": {
"services-gera-mcp-gera-nexus": {
"command": "npx",
"args": [
"-y",
"@gera-services/mcp-gera-nexus"
]
}
}
} {
"servers": {
"services-gera-mcp-gera-nexus": {
"command": "npx",
"args": [
"-y",
"@gera-services/mcp-gera-nexus"
]
}
}
} codex mcp add services-gera-mcp-gera-nexus -- npx -y @gera-services/mcp-gera-nexus
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"services-gera-mcp-gera-nexus": {
"type": "local",
"command": [
"npx",
"-y",
"@gera-services/mcp-gera-nexus"
],
"enabled": true
}
}
} openclaw mcp add services-gera-mcp-gera-nexus --command npx --arg -y --arg @gera-services/mcp-gera-nexus
mcp_servers:
services-gera-mcp-gera-nexus:
command: "npx"
args: ["-y", "@gera-services/mcp-gera-nexus"] {
"McpServers": {
"services-gera-mcp-gera-nexus": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@gera-services/mcp-gera-nexus"
]
}
}
} assistant mcp add services-gera-mcp-gera-nexus -t stdio -c npx -a -y @gera-services/mcp-gera-nexus
{
"mcpServers": {
"services-gera-mcp-gera-nexus": {
"command": "npx",
"args": [
"-y",
"@gera-services/mcp-gera-nexus"
]
}
}
} 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.
- 25 Sept 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 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 25 Sept 2026 · Analysed npm/@gera-services/mcp-gera-nexus@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_booking_intent Create a consent-first booking/action INTENT (no payment) ~349
Create a structured, human-confirmable INTENT to act on a Gera marketplace on the user's behalf — a home-service booking, a job application, or a restaurant order. IMPORTANT — this is the consent gate: it does NOT take payment, does NOT commit a provider, and does NOT execute the transaction. It records what the user wants, assigns a tracking intent_id, writes an audit entry, and returns a confirmation_url (a deep-link) the HUMAN opens to review and complete the action on the real Gera surface. Present the intent and the confirmation link to the user; tell them plainly that nothing has been booked or paid yet and that they must confirm. Use get_action_status to check an intent later. Never tell the user a booking/order/application is "done" from this tool — it is a lead awaiting their confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| action_kind | string | yes | Which marketplace action to create an intent for. |
| consent_acknowledged | boolean | yes | Must be true: confirms the agent has told the user this creates a lead for THEM to confirm, not an executed/paid transaction. |
| contact_name | string | – | Name the user wants to book under (kept in the intent for the human to confirm). |
| notes | string | – | Free-text details: the task, the order items, the role applied for, etc. |
| provider_id | string | – | Id of the chosen provider/job/restaurant from a search_* tool result. |
| provider_name | string | – | Human-readable name of the chosen provider/job/restaurant. |
| requested_for | string | – | When the user wants it, e.g. "2026-06-20 morning", "ASAP". |
No output schema declared.
No examples provided.
get_action_status Look up a booking/action intent status ~113
Look up the status of an intent created earlier by create_booking_intent, by its intent_id. Returns the current status (pending_human_confirmation | expired | unknown) and the audit trail. Note: intents are tracked per running server session — an id from a different session returns "unknown". This server does NOT poll the marketplace for downstream completion; confirmation/payment happens on the Gera surface via the confirmation_url, outside this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| intent_id | string | yes | The intent_id returned by create_booking_intent. |
No output schema declared.
No examples provided.
search_home_services Search GeraHome home-service providers ~178
Find home-service providers (plumbers, electricians, cleaners, handymen, etc.) on GeraHome. Tries the live GeraHome production API first; if unreachable or empty, falls back to real crawled provider records bundled with this server (currently Yerevan, sourced from List.am/Spyur). Read-only — finds providers; it does not book anything. The result's "data_source" field tells you whether rows are live or bundled seed. Pass these provider ids to create_booking_intent to start a consent-first booking.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Service category, e.g. "plumber", "electrician", "cleaner". |
| city | string | – | City to search in, e.g. "Yerevan". |
| limit | integer | – | Max providers to return (default 10). |
No output schema declared.
No examples provided.
search_jobs Search GeraJobs job postings ~167
Search jobs on GeraJobs by keyword and location. Tries the live GeraJobs production API first; if unreachable or empty, returns real recruitment-agency / job-board supply partners bundled with this server (clearly labelled — these are where vacancies come from, not individual postings). Read-only. The "data_source" field tells you which you got. To apply, use create_booking_intent with action_kind="job_application" — that creates a consent-first application lead, not a submitted application.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return (default 10). |
| location | string | – | Location filter, e.g. "London", "GB", "remote". |
| query | string | – | Keyword, e.g. "software engineer", "nurse", "driver". |
No output schema declared.
No examples provided.
search_restaurants Search restaurants (live UK FHRS data) ~187
Find restaurants for GeraEats, with their current UK Food Hygiene Ratings. Backed by the live Food Standards Agency FHRS open API (api.ratings.food.gov.uk) — genuinely live UK restaurant data, no auth. Filter by city/name and minimum hygiene rating (0-5). Read-only. To place an order, use create_booking_intent with action_kind="restaurant_order" — a consent-first order lead, not a paid order.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | UK city/town/area to search, e.g. "Bristol", "Manchester". |
| limit | integer | – | Max restaurants to return (default 10). |
| min_rating | integer | – | Minimum food hygiene rating (0-5). E.g. 4 = only well-rated places. |
| name | string | – | Restaurant name to search for, e.g. "Dishoom". |
No output schema declared.
No examples provided.
What is the services.gera/mcp-gera-nexus server?
services.gera/mcp-gera-nexus is listed in the public MCP registry as services.gera/mcp-gera-nexus. Search Gera marketplaces and create consent-first booking intents. No payment taken by server. This page covers its npm package (@gera-services/mcp-gera-nexus).
Is the services.gera/mcp-gera-nexus server safe to use?
services.gera/mcp-gera-nexus scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 services.gera/mcp-gera-nexus server expose?
services.gera/mcp-gera-nexus exposes 5 tools: search_home_services, search_jobs, search_restaurants, create_booking_intent, get_action_status. Their descriptions and schemas cost roughly 994 tokens of context every time the server is loaded.
Is the services.gera/mcp-gera-nexus server still maintained?
services.gera/mcp-gera-nexus is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the services.gera/mcp-gera-nexus server under?
services.gera/mcp-gera-nexus declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.