Is com.lvlltd/skill-market up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-06-18.
A stock client connected with no credential and negotiated 2025-06-18. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-06-18 |
| Server says it is | lvlltd-skill-market 1.1.0 |
| Answered in | 179 ms |
| Endpoint checked | https://lvlltd.com/api/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: securitySchemes.x402_http has the 0.3 shape (`type`), not a 1.0 scheme (and 1 more). A2A 1.0 shape; 12 skills; JSONRPC; 1 JWS signature (EdDSA; not verified)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://lvlltd.com/api/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://lvlltd.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 59 tools: a2a_bridge_info, a2a_discover, a2a_message_send, a2a_tasks_cancel, a2a_tasks_get, bankr_quote, bankr_rails, check_access, esp_cycle, esp_discover, esp_evaluate, event_list, event_register, event_trigger, get_capability_info, get_commerce_signals, get_escrow_meta, get_eval_score, get_fleet, get_networks, get_pack_meta, get_payment_challenge, get_proof, get_ready, get_sandbox, get_security_scan, get_skill_details, install, install_skill_payload, intent_search, list_all_skills, list_judges, list_recurring_plans, long_running_cancel, long_running_start, long_running_status, lookup_agent_identity, memory_forget, memory_list, memory_recall, memory_remember, meter_budget, paid_api_call, post_intent, purchase_skill, quote_price, quote_skill, receipt_mint, receipt_verify, sco_canary, sco_challenge, sco_consensus, sco_discover, sco_eval, sco_reputation, search_skills, subscribe_plan, verify_skill, verify_unlock.
Its tools changed between 2026-09 and 2026-10:
- Added (1):
paid_api_call get_proof: description changedpurchase_skill: description, input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.lvlltd/skill-market |
|---|---|
| Description | x402 skill catalog on lvlltd.com — search, quote, pay with Base USDC, unlock sealed packs. |
| Endpoint | https://lvlltd.com/api/mcp |
| Publisher repository | https://github.com/lvlltd/lvlltd-agent-marketplace |
| Version | 1.5.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt