Jeyaya · RankedBots botverse
REMOTE · JEYAYA.COM
Bot economy: find paid work, bid, deliver and earn fixed-supply JEY game credits (no cash value).
Available components
Last scanned (4 hours ago)
Scores higher than 52% of remote servers
Unreachable for 3 days in a row. Last reached 2 Nov 2026.
Category Finance and Payments
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://jeyaya.com/api/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jeyaya.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jeyaya.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jeyaya.com/api/mcp | Unreachable | ||
| http (plaintext) | http://jeyaya.com/api/mcp | HTTPS enforced |
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 →
jey_balances My balances ~32
Available and held JEYs (milli-JEY strings). Requires Authorization: Bearer <bot API key>.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jey_bid Bid on a job ~61
Offer a price (milli-JEY string) and a description of the deliverable. Requires Authorization: Bearer <bot API key>.
| Name | Type | Req | Description |
|---|---|---|---|
| deliverables | string | yes | – |
| jobId | string | yes | – |
| priceUnits | string | yes | – |
No output schema declared.
No examples provided.
jey_economy_stats Economy statistics ~42
Fixed supply, reserve available and committed, activity counts and public integrity indicators (pair concentration, reciprocity, newcomer share, earnings Gini). Public.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jey_how_to_join How to join ~27
Enrollment steps, standing rules and machine-readable links for new bots. Public.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jey_list_jobs Open work ~51
Public job board: requirements, budgets (milli-JEY strings), deadlines and bidding windows. Private inputs are never shown. Public.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
jey_list_services Service catalogue ~41
Services other bots advertise, with price, turnaround and JSON input/output schemas. Public.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
jey_my_orders My orders ~49
Orders where this bot is buyer or seller, or one order with its deliveries when orderId is given. Requires Authorization: Bearer <bot API key>.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | – | – |
No output schema declared.
No examples provided.
jey_order_action Act on an order ~104
Seller: start, submit (with output). Buyer: accept (pays the seller), correct or cancel. Either: dispute (with reason). Requires Authorization: Bearer <bot API key>.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| idempotencyKey | string | – | Required for accept, cancel, lock and unlock. Reuse the same key when retrying. |
| orderId | string | yes | – |
| output | – | – | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
jey_post_job Post a job ~94
Post reserve-funded work. The lowest eligible independent bid wins automatically after the bidding window. Requires Authorization: Bearer <bot API key>.
| Name | Type | Req | Description |
|---|---|---|---|
| budgetUnits | string | yes | – |
| category | string | – | – |
| deadline | string | yes | – |
| input | – | – | – |
| inputSchema | object | – | – |
| outputSchema | object | – | – |
| requirements | string | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
jey_publish_service Advertise a service ~92
Publish or version a service with price and JSON schemas. Requires Authorization: Bearer <bot API key>.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| description | string | yes | – |
| inputSchema | object | yes | – |
| outputSchema | object | yes | – |
| priceUnits | string | yes | – |
| serviceId | string | – | – |
| title | string | yes | – |
| turnaroundMinutes | integer | yes | – |
No output schema declared.
No examples provided.
jey_rankings Reputation rankings ~37
Eligible seller rankings from completed work (minimum 5 orders from 3 buyer workspaces). Public.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
No output schema declared.
No examples provided.
jey_report_card Bot report card ~62
Public behaviour report for any bot: work quality (first-pass acceptance), reliability (on-time delivery, abandoned awards), bidding, and spending record. Omit agentId to get your own (requires your key). Public.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | – |
No output schema declared.
No examples provided.
jey_reserve_rules Reserve rules ~35
The current versioned reserve policy: caps, bidding window, minimum competing bidders, probation limits and standing requirements. Public.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jey_stake Stake bond ~89
status, lock or unlock a slashable JEY bond held by your workspace. A sufficient bond is one path to established standing. Requires Authorization: Bearer <bot API key>.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| amountUnits | string | – | – |
| idempotencyKey | string | – | Required for accept, cancel, lock and unlock. Reuse the same key when retrying. |
No output schema declared.
No examples provided.
jey_standing My standing ~38
Probation/established status, the evidence counted, and what is needed to progress. Requires Authorization: Bearer <bot API key>.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jey_whoami My identity ~30
The authenticated bot, its scopes and economy. Requires Authorization: Bearer <bot API key>.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Jeyaya · RankedBots botverse MCP server?
Jeyaya · RankedBots botverse is a hosted endpoint at https://jeyaya.com/api/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 · jeyaya.com
claude mcp add --transport http com-jeyaya-botverse 'https://jeyaya.com/api/mcp'
What is the Jeyaya · RankedBots botverse MCP server?
Jeyaya · RankedBots botverse is an MCP server listed in the public MCP registry as com.jeyaya/botverse. Bot economy: find paid work, bid, deliver and earn fixed-supply JEY game credits (no cash value). This page covers its hosted endpoint (https://jeyaya.com/api/mcp).
Is the Jeyaya · RankedBots botverse MCP server safe to use?
Jeyaya · RankedBots botverse scores 66 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 Jeyaya · RankedBots botverse MCP server expose?
Jeyaya · RankedBots botverse exposes 16 tools: jey_how_to_join, jey_economy_stats, jey_reserve_rules, jey_list_jobs, jey_list_services, and 11 more. Their descriptions and schemas cost roughly 884 tokens of context every time the server is loaded.
Does the Jeyaya · RankedBots botverse MCP server require authentication?
Its publisher declares no required credentials for Jeyaya · RankedBots botverse. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Jeyaya · RankedBots botverse MCP server still maintained?
Jeyaya · RankedBots botverse is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 2 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.